Dual ISO - massive dynamic range improvement (dual_iso.mo)

Started by a1ex, July 16, 2013, 06:33:50 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Walter Schulz


dfort

Quote from: CesarOliveiraPhotography on November 14, 2015, 12:17:03 AM
Hello dfort, thank you for answering me. I downloaded your files but I can't open it. cr2hdr open in terminal. What I need to do? 
Where can I find a tutorial?

What Walter said -- though to get the most out of it requires some skills on the terminal.

On the Mac put cr2hdr in /usr/local/bin so it will be in your path. If you don't know what I'm talking about then you can still use it if you put cr2hdr in the same directory as the files you want to process the difference is that instead of starting it by typing "cr2hdr" (without quotes) you will need to type "./cr2hdr". Open the terminal and type "cd" then drag the folder that contains the dng files you want to process, hit return. Now that you are in that directory type "./cr2hdr" and the name of the file you want to process. You can also type "./cr2hdr *" to process everything in the folder. cr2hdr will only process the .dng and .cr2 dual_iso shots.

By the way, a1ex just committed some changes to cr2hdr so I posted new builds in my download area:

https://bitbucket.org/daniel_fort/magic-lantern/downloads

tron

Thanks dfort. Is it still  the unified 20 bit version ?   :)

toze3


Danne

Experienced a bug with the latest cr2hdr binary.

Older RAW file. Doesn,t seem to parse the color matrix 1 looking through exiftool. Filmed with a 5d mark 3 back in the days :).
Here are the files

https://drive.google.com/file/d/0B4tCJMlOYfirSmhNY1l3bGIzdGc/view?usp=sharing

https://drive.google.com/file/d/0B4tCJMlOYfircUd1NlY4MG0zVmc/view?usp=sharing

dfort

Quote from: Danne on November 17, 2015, 06:29:28 PM
Experienced a bug with the latest cr2hdr binary.

Older RAW file. Doesn,t seem to parse the color matrix 1 looking through exiftool. Filmed with a 5d mark 3 back in the days :).

I can't open M30-1635_1_2015-11-17_0001_C0000_000011.DNG with any of the tools that I've got.
M30-1635_1_2015-11-17_0001_C0000_000006.dng is a dual_iso shot that the latest cr2hdr seems to convert properly. What's the problem?

The version @toze3 pointed to seems to be for Windows only and I'm on OS-X so I wasn't able to test it out though I think I'm up to date on the latest version.

Quote from: tron on November 15, 2015, 01:56:17 PM
Thanks dfort. Is it still  the unified 20 bit version ?   :)

Yes, the 20-bit version has been merged into the main branch so from now on cr2hdr is 20-bit.

Walter Schulz

What happened to tag ColorMatrix1? Undefined in M30-1635_1_2015-11-17_0001_C0000_000011.DNG (viewed by ExiftoolGUI). Different DNG definition in both files: Readable one has 1.1.0, unreadable 1.3.0.
Do you have used different tools to get those DNGs?

toze3

Just guessing, but maybe dcraw and exiftool updated...

Danne

Sorry.
I used later build from dfort bitbucket and it won,t convert properly.
https://bitbucket.org/daniel_fort/magic-lantern/downloads

QuoteLast update: 8b9190b on 2015-11-14 16:44:35 UTC by a1ex:
cr2hdr: identify camera model from string (should fix issue #2403 ...

Should I update exiftool?

*Replaced also with included exiftool from dfort but still not working.

Walter Schulz

Try using the files included in dfort's zip file. Exiftool, dcraw, cr2hdr

EDIT: dfort is just running some code changes to cr2hdr.

Danne

I did. No cegar ;).
Do you get the second file to convert with his included files? Your on windows right.

Walter Schulz

Your DNG is out of order and there is no use playing around with it. How do you create this dng? It's converted from dual-iso clip, isn't it?

Danne

That is the DNG example I get when converting with dforts stuff. It,s just to show the problem. The second file is converted from raw2dng before using cr2hdr and it is very playable.

Walter Schulz

Can you make your source file accessible?

EDIT: I'm running Windows and OS X.

Danne


Walter Schulz

Thanks! And confirmed: dforts build messes up ColorMatrix1. I downloaded latest lr2hdr.plugin zip from kitchetof's bitbucket repository and converted your file and opened it in PS.


dfort

Good to know. The one on my download page has these commits that have not been merged into the main branch yet. Thanks for being the crash test dummies on this!

https://bitbucket.org/hudson/magic-lantern/commits/3a7553747e4f10984c9c35df3ed1fbd94c8aaefd
https://bitbucket.org/hudson/magic-lantern/commits/a5de7ee1cf619c5df45fb01122b9462dc77b3e3e
https://bitbucket.org/hudson/magic-lantern/commits/dd7f91d38e9ed2d3618d8014949b16e3b073d339
https://bitbucket.org/hudson/magic-lantern/commits/8b9190b7b0c57297c35eaaae4da26df74b12cc07

I'm not sure what the proper protocol is. There's no pull request yet. Perhaps comment on the commits so they won't get merged into unified? In the meantime I'll mark the versions in my bitbucket download area.

dfort

Ok--there's now a 2015-10-01 version and a 2015-11-14 testing version. I re-compiled the Nov. 14 version just in case that the raw video issue is coming from a mix up when I built the binaries.

https://bitbucket.org/daniel_fort/magic-lantern/downloads

Walter Schulz

Thanks! ColorMatrix1 issue not present in test version.

dfort

You mean the November 14 version? Really??!! That means that the problems you were seeing in the previous version had an error on my part and a1ex's commits are fine. Gee, imagine that.  :o

We should probably continue using the November 14 test version and if it proves stable ask for that branch to be merged into unified. There is still a segmentation fault that goes back several versions. The discussion is in this topic.

NickZee

Hello ML.

Dual ISO is new to me.  I've tinkered with it a while back, but never fully explored it.  Recently, I used it in a vacation rental video, and I hope to get feedback.

These jpgs are one frame from a RAW (not MLV) Dual ISO video.    I used the LR Plugin to interlace.

5DM3
1920x1080
30fps
ISO difference  : 3.97 EV (1567)


Original - Dual ISO difference  : 3.97 EV (1567)


Before Editing


After Editing - In Lightroom


Settings


Is it normal to have to raise the exposure +2 EV and the shadows to almost 80?  Seems very extreme to me. 

Also, can some one clarify why the interlaced image is so dark?  The pre interlaced version is much lighter.

If anyone has ideas or tips for me, I'd appreciate it!


Here are the details form the log file. 
Camera model    : Canon EOS 5D Mark III
Full size       : 1920 x 1080
Active area     : 1920 x 1080
Black borders   : N/A
ISO pattern     : BddB RGGB
White levels    : 10000 14882
Noise levels    : 8.00 8.00 8.00 8.00 (14-bit)
ISO difference  : 3.97 EV (1567)
Black delta     : 33.54
Dynamic range   : 9.96 (+) 10.65 => 14.62 EV (in theory)
AMaZE interpolation ...
Amaze took 0.18 s
Edge-directed interpolation...
Semi-overexposed: 3.87%
Deep shadows    : 89.44%
Horizontal stripe fix...
Full-res reconstruction...
ISO overlap     : 3.0 EV (approx)
Half-res blending...
Chroma smoothing...
Building alias map...
Filtering alias map...
Smoothing alias map...
Final blending...
Noise level     : 8.00 (20-bit), ideally 8.00
Dynamic range   : 15.96 EV (cooked)
AsShotNeutral   : 0.61 1 0.53, 4048K/g=1.13 (gray max)
Active options:
--amaze-edge    : use a temporary demosaic step (AMaZE) followed by edge-directed interpolation (default)
--cs3x3         : apply 3x3 chroma smoothing in noisy and aliased areas
--no-bad-pix    : disable bad pixel fixing (try it if you shoot stars)
--wb=graymax    : set AsShotNeutral by maximizing the number of gray pixels (default)
--same-levels   : Adjust output white levels to keep the same overall exposure
                  for all frames passed in a single command line
                  (useful to avoid flicker - for video or panoramas)
Architectural Photography
NickZimmerman.com
5D MK3 & 600D | 24-70mm USMII L 2.8 | Nikon 14-24mm 2.8 | Nikon Nikkor 24mm 2.8 AIS & 50mm 1.4 AIS ** Windows 8.1 Pro | 32GB Ram | i7-4770 @ 3.4GHz

garry23

@NickZee

I'm sure others will add further comments, however, from what you have posted it looks normal to me. Remember what dual ISO is. Think of it as a 'normal' exposure interlaced with an over exposed one. This is why the interlaced looks over exposed. The Dual ISO capture should only be seen as a 'data gathering' stage, ie don't try and assess it from a quality perspective.

It is thus usual to have to boost the exposure and/or shadows in post and play around with whites/blacks, and of course noise reduction.

I personally use the ETTR + Dual ISO as a killer combination for still photography, ie I don't touch video.

BTW I have written about my ML experiences on my blog, which you are welcome to scan at photography.grayheron.net. Please note I write this blog for personal enjoyment and accept it is not always the best view of ML or photography :-)

DeafEyeJedi

@NickZee:

You're getting about 16 stops of DR... Which is usually more than what you can ask for especially coming from a 5D3.

Looks fine to me as well.
5D3.113 | 5D3.123 | EOSM.203 | 7D.203 | 70D.112 | 100D.101 | EOSM2.* | 50D.109

NickZee

@garry23 @DeafEyeJedi

Very appreciative gents!

Thank you.
Architectural Photography
NickZimmerman.com
5D MK3 & 600D | 24-70mm USMII L 2.8 | Nikon 14-24mm 2.8 | Nikon Nikkor 24mm 2.8 AIS & 50mm 1.4 AIS ** Windows 8.1 Pro | 32GB Ram | i7-4770 @ 3.4GHz

DeafEyeJedi

You can also try crushing down the Blacks a bit more to give it more contrast and less noise...
5D3.113 | 5D3.123 | EOSM.203 | 7D.203 | 70D.112 | 100D.101 | EOSM2.* | 50D.109