Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - akumiszcza

#1
Modules Development / Re: DotTune AFMA (dot_tune.mo)
January 22, 2016, 09:01:47 AM
Hi. As for the 6D/1.1.6 problems.
I'm using the current nightly (magiclantern-Nightly.2016Jan14.6D116.zip) and I can say that DotTune AFMA sometimes works, sometimes not :)
For my first trial (with 50 f/1.4) I got the whole range. After different try (different focusing card among other things) I got no AF... After several trials I think I get best results with:
- manual ISO (100)
- M mode
- lowest f value of course
- exposure slightly to the right (for better contrast, +1 or so)
- IS turned off
- AF-ON key changed to default value
- new focusing card taken from original youtube video (http://www.testcams.com/DotTune/CrossHatch_Target.png)
- distance from the card = 50 x focal length (more less)

I don't know which of these are important, though. Even after doing everything, for some lenses/focal length I had to do it manually, as in original youtube video (https://www.youtube.com/watch?v=7zE50jCUPhM). One tip: you don't have to enter Canon menu, setting it in DotTune AFMA module works the same (just remember to pick if it's prime/wide/tele). So it's fast anyway.
#2

Quote from: maxotics on October 21, 2013, 07:19:38 PM
I've owned a G5, G6, G10, G11, G13, 5D, 50D, T1i, etc. For Sony Nex 5-N, 7.  In Panasonic GF3, G5.

Are you some kind of camera beta-tester? Especially Canon G13 is intriguing.
#3
Quote from: Audionut on October 14, 2013, 04:44:40 PM
So disable it!

Yeah. That's the best remedy. Thanks...


BTW. Would it be possible to have a message during a shot review taken after SET mode in ETTR? 50D does not have ettr confirmation beeps and I don't know if ettr worked during LV after pressing SET, making the mode less useful than other. It would be great to have a message saying if ettr failed or not, especially since set mode is the fastest 
#4
Quote from: Audionut on October 14, 2013, 06:42:20 AM
On top of the process time for the actual dual ISO shots.  So if I have 100 dual ISO shots, I've doubled that part of the processing time for no other reason then there is no other way to distinguish which shots need to be processed. 

If the prefix works for you, no reason then. But I get about 1 in 10 shots wrongly prefixed, both ways.

Quote from: Audionut on October 14, 2013, 06:42:20 AM
Then there's the file management.  Prefixed shots get dumped into a separate folder and the processed DNG's copied into the shot folder.  This way I can keep the original CR2's separate for later processing (updated cr2hdr or whatever), without having to process all 2000 photos again, and, I don't have interlaced CR2's polluting the image viewer.

That's what dualiso.vbs script does – it renames all files according to exif date and time, moves real Dual-ISO cr2s to separate folder than dngs and even makes a "_dualiso" suffix to Dual-ISO .cr2 and .dng to make them easier to distinguish. Anyway, I've already almost processed a Dual-ISO photo with some batch processing because I didn't notice it was Dual-ISO on quick preview (and it had no prefix). The result would have been strange...
#5
Tragic Lantern / Re: 50D and 40D Raw video
October 12, 2013, 02:54:28 PM
Quote from: Andy600 on October 11, 2013, 06:30:05 PM
(...)
***************************************************************************************************************************************
50D users - NEW TRAGIC LANTERN 50D BUILD UPLOADED https://bitbucket.org/andy600/tl50d/downloads/Tragic_Lantern_50D109-Andy600.2013Oct11.zip
***************************************************************************************************************************************
(...)
Great looking new display bar with new 'Histobar' - select in raw histogram settings. (Tip: in the Display menu>Advanced set to auto 4:3)


Does RAW HistoBar work in image review? I have it only in LV, though the info says:
"Will use RAW histogram in LiveView and after taking a pic."

Maybe some other setting is needed too?
#6
Quote from: Audionut on October 11, 2013, 10:21:24 AM
The file prefix is very handy.  Sure it doesn't work in burst mode but that's what warnings are for.
Processing 2000+ wedding photos, it's much easier to pick out the dual ISO shots with the prefix then to wait hours batch processing the lot of them.

It's only a problem where you have alternate shooting enabled.  I'd settle for reduced capture rate where file prefix is not default and alternate capture is enabled.

I've made a short benchmark for 20 non-dual-iso cr2 files using cr2hdr alone and scripts I have there: http://www.magiclantern.fm/forum/index.php?topic=8738.msg81768#msg81768
cr2hdr alone (drag&drop) = 1:46.52
No renaming of files, just many processes of cr2hdr:
timer cmd /c dualisonorename.vbs = 48.391 (maxprocs=4) 40.902 (maxprocs=8 ) 41.252 (maxprocs=16)
Many processes of cr2hdr + renaming using exiftools:
timer cmd /c dualiso.vbs = 59.851 (maxprocs=4) 62.404 (maxprocs=8 )

So for 2000 photos it would take 1 hour 8 minutes on my old computer (Core2 Q6600). Less than that, because the program takes some time to start and stop (less processes at once then). Of course, for Dual-ISO files the time will increase, but so as with your method.

And I think I have some photos with wrongly assinged prefix that were not made by burst but by Always On AETTR. Probably ML finished calculations of new exposure at the exact moment I took the photo?
#7
Quote from: a1ex on October 11, 2013, 08:50:16 AM
I simply run cr2hdr on all files (usually, more than half of them are dual ISO, and the ones that are not are skipped quickly). Then, my raw processing script picks the DNG if there's one, or the CR2 otherwise.

I do the same way — see the scripts here: http://www.magiclantern.fm/forum/index.php?topic=8738.msg81768#msg81768
I've just noticed the moire in small previews and thought it might be useful for some people.

Quote from: a1ex on October 11, 2013, 08:50:16 AM
The file prefix is not quite synced in burst mode, so I'm not sure whether to keep it or not. I don't think I can make it reliable in the near future.

I would opt for removing it — it's unreliable and might leave some photos processed wrongly (it's not visible at first glance sometimes if photos are dual-iso and somebody might batch process them without using cr2hdr first, which can give unpredictable results).
#8
Thank you, a1ex – works great! As far as it's possible for these bad and unexposed photos ;)

BTW, I've found a quick way of checking if a given .cr2 is Dual-ISO, or not (I get quite many Dual-ISO photos without the prefix and some non-Dual-ISO with the prefix – I guess it's some kind of racing condition while having Auto Snap or Always On and shooting in quick series?). By turning small image previews in additional panel of Bridge (smaller than thumbnails for me at least) I see the stripes quite clearly – Moire effect. It's much faster than opening 100% previews at least. It should work with other software I guess, but you need to find the proper preview size.
#9
New version – http://bit.ly/dualisopack6
CHANGES:
1. dualisonorename.vbs to skip renaming files and just process them — useful for reprocessing Dual-ISO with newer cr2hdr.exe
2. New version of cr2hdr.exe included
#10
Both photos were made with AETTR+Dual-ISO, but on AutoSnap mode and both, I think, were not the final, settled, photos.
#11

Quote from: Doyle4 on October 10, 2013, 02:19:41 PM
What camera did you use akumiszcza? i noticed i had an image like your bottom sample on my 600D, only the one though.

It's 50d. The problem on the bottom sample appeared in some previous photos in dark scenes, but only on small fragments.
#12
Two badly processed Dual-ISO photos:

1. CR2 DNG


2. CR2 DNG

#13
Not for slow cards I still use for photos, not video. And I don't have USB 3.0 in my computer, so I'd need some card additionally. Anyways, the main problems are processing time and my time spent unnecessarily at the computer just doing basic commands. These scripts try to deal with both issues.
#14
I'd like to share my quick and very dirty way to get dual iso files from CF card as fast as possible.
Normal steps are:
1. Get files from CF cards (it's a long process for me especially with USB 2.0 card reader and some slow 30MB/s cards).
2. Process them by cr2hdr (I use the script provided by engardeknave (http://www.magiclantern.fm/forum/index.php?topic=8520.0) without any prefix as I get quite many dual-iso files without prefix).
3. Rename them (I use exif date based system that moves filename.cr2 into something like a:\2013\10\07\20131007T121930filename.cr2).
4. Find dual-iso .cr2s in those created dirs and move them to dualiso subdir (I want to see only generated dngs while browsing, if something goes wrong I can alway go to dualiso subdir for original).

This takes a looong time.

Here is a zip file containing cr2hdr.exe, exiftool.exe, dcraw.exe (9.19, not requiring cygwin1.dll) together with dualiso.vbs (altered script by engardeknave), commands.cmd (this calls cr2hdr.exe and changes names), and runiffiles.cmd (a loop that calls dualiso.vbs if there's any file left to process).

Now, put all those in one directory, upload all .cr2 files in the same dir and run dualiso.vbs (you can change maxprocs -- maximum number of running processes -- to different number at the beginning of dualiso.vbs). After some time you'll get all your files processed and put into different directories

Second method is even more dirty but gives you ability to run the script while getting files from the cards. Just start downloading from your card into the directory with the unzipped files and run runiffiles.cmd. The crazy script just checks constantly if there are any .cr2 files and calls dualiso.vbs then. So you can put all photos from several different cards and in the meantime the computer will process and rename them for you. You can leave the computer while moving the files and at the end everything will be done.

NOTES
THESE SCRIPTS ARE PROVIDED AS IS AND I DON'T GIVE ANY WARRANTY IF THEY WORK AND DO NOT DELETE YOUR PHOTOS, SO PLEASE TEST IT ON SOME COPIES FIRST!!!!

For Windows 9x and earlier you should probably change cmd.exe to command.com in dualiso.vbs (at the beginning)

DOWNLOAD (zip file)
http://bit.ly/dualisopack6

Version 4 (and previous) had a critical bug during renaming - mixed months with minutes. Sorry...
#15
I'd like to share my quick and very dirty way to get dual iso files from CF card as fast as possible (...)
Topic moved here: http://www.magiclantern.fm/forum/index.php?topic=8738.msg81768#msg81768
Please post your comments there.
#16
Quote from: 1drey on October 08, 2013, 10:48:43 AM
Got this


Looks like you're in another folder...

Open the folder in explorer. Check if all your files are here. shift+rightclick and choose "open command prompt here" (it does not work on every windows version) and check again. Or run cmd.exe and cd <yourfolderpath> before running the command.
#17
Quote from: a1ex on October 08, 2013, 10:47:48 AM
Do you have a link to a non-cygwin dcraw.exe that also works for 6D, so I can put that one in the zip?

I don't have 6D to check. I use some 9.17 version 576064 byte on my 50D. Some new builds of 9.19 are here: https://sites.google.com/site/manuelllorens/ – but I didn't test those.
#18
Quote from: pest01 on October 08, 2013, 10:27:54 AM
Hi to everyone, i download the new Windows:cr2hdr.exe and it doesn't seem to be working on my windows i get a dcraw.exe - System error that says <<cant start cygwin1.dll is missing>> how do i fix it or do i stay with the previous one that worked? Are there any major changes in those two?

Just replace dcraw.exe with a version not requiring cygwin1.dll or install cygwin in your system.
#19
Quote from: 1drey on October 08, 2013, 10:33:50 AM
And for some mysterious reason I don't see resulting DNG in the source folder. It was the first place where I expected it to appear.
Seems that *******.dng file was not created at all - I was searching it through the file search on my PCwith no avail.

Put the .cr2 dual iso file in the same folder with cr2hdr.exe, dcraw.exe, exiftool.exe. Run cmd.exe there and execute "cr2hdr <yourfilename>". See if any errors appear.
#20
Quote from: a1ex on October 07, 2013, 02:00:47 PM
As I said earlier, the issue is in EXIF. So, just find the exiftool command that copies WB properly from the CR2 and I'll integrate it.

This is what I found, maybe something will be useful in the future:

I renamed the files mentioned before to norm.cr2, dual.cr2 and dual.dng.

Adobe Camera Raw shows the following temperature/tint values ("As shot"):
norm.cr2: 5200/+14
dual.cr2: 5850/+38
dual.dng: 4850/+46

As you can see dual.cr2 has it wrong, too, but better than dual.dng anyway.

I tried using exiftool commands, but none worked for me:
exiftool -tagsfromfile norm.cr2 -Canon:WhiteBalance -WB_RGGBLevelsAsShot -WB_RGGBLevelsAuto -WB_RGGBLevelsMeasured dual.dng
(mentioned somewhere by the author of exiftool)
exiftool -WhiteBalance#=5200 dual.dng

Then I used hex editor to alter dng on my own.
After setting crs:Temperature="5200" and crs:Tint="+14" ACR shows the proper values of dual.dng file. This could be a good way of changing dng directly, but I don't know how to read temperature and tint value from a file. I've tried exiftool, exiv2, dcraw and all of them had other formats. And, as I found out just before posting it, it only works if ACR already exported xmp values into dng (standard cr2hdr output does not have it). But if it's possible to add some xmp to dngs, then crs:Temperature and crs:Tint works.

Second thing I've noticed: dcraw -v -w norm.cr2 shows the following: multipliers 2.102539 1 1.365234 1.

Now the command dcraw -T -r 2.102539 1 1.365234 1 dual.dng creates dual.tiff with correct WB, so it might be possible to use this method somewhere in cr2hdr.c.
#21
General Help Q&A / Re: Dual ISO workflow issue
October 07, 2013, 04:34:40 PM
No. You take cr2hdr.zip package. Unzip it into a directory and then replace dcraw.exe with another version. You drop files onto cr2hdr.exe as usual. Cr2hdr uses dcraw during process.
#22
Quote from: a1ex on October 07, 2013, 11:21:22 AM
cr2hdr does not touch WB coefficients and it's not meant to do so.

How come then that two photos — one normal, one dual iso — taken seconds apart in the same conditions have completely different WB? I don't have a single DNG file with proper WB set. Maybe it's ACR issue? See the example files: https://mega.co.nz/#!gYcwSYLJ!cQuj1zx4Q2k1IphjgMZIOBHjOoJpwEC4HUHsTPDM2jI
#23
General Help Q&A / Re: Dual ISO workflow issue
October 07, 2013, 07:14:13 AM
See this post – http://www.magiclantern.fm/forum/index.php?topic=7139.msg80387#msg80387

I just used dcraw.exe that didn't need cygwin1.dll
#24
Quote from: ouuzi on October 05, 2013, 10:05:47 PM
I am noticing a slow down of ettr in the latest build.Is something changed ?I am using 5/10 build and I have set the trigger to Halfs DBC, I was using this till now.After double click it takes noticeably more time to end calculations(it goes to ettr(5) if this makes a difference),I have also noticed that I see something like a thin line of pixels scanning down the screen from top to bottom.
My setting are:
Defaults all except link to dual iso and SNR limits off both.

As for this scanning – I've noticed it in October 3 nightly (see this post http://www.magiclantern.fm/forum/index.php?topic=8322.msg80410#msg80410) and it was connected with RAW zebras I think. Sometimes almost all of the photo was overlaid by it, as you can see in the screenshot there. Anyway, the problem disappeared in later nightly for me.
#25
Quote from: a1ex on October 06, 2013, 11:48:31 PM
Is exiftool running?

I think so – cr2hdr gives no error while running, exiftool.exe is in the same dir and runs fine when called. It's in the path too.

Here's an example of what I'm talking about:
https://mega.co.nz/#!gYcwSYLJ!cQuj1zx4Q2k1IphjgMZIOBHjOoJpwEC4HUHsTPDM2jI
In the zip you get non-dual-iso CR2, dual-iso CR2 and generated DNG. I need to change WB of the DNG by about +500 K, -30 tint to have it similar to non-dual-iso CR2.