Messages

Tried a second chance with that single problematic file gave a perfect result.
I correct myself: you COMPLETELY did it.
Sincerely many congrats for your amazing work.

You almost did it, Danne. Great job anyway!
I tested 7 most problematic dual-ISO mlvs, and new Switch does work for 6, and fails only for 1.
That one gives a weird result: the converted dngs are a sequence that alternates bunches of good-dngs and bunches of bad-dngs. The bunches contain different numbers of dngs, for example the first bunches contain respectively 8-good-dngs, 2-bad-dngs, 8-good-dngs, 10-bad-dngs, 2-good-dngs, etc.
Good-dngs have extension in uppercase (.DNG) whilst bad-dngs have extension in lowercase (.dng).
The curious thing is that importing the dngs-folder into Davinci, the software can't recognize a unique sequence, instead it imports all the bunches separately (each one with 8, 2, 8, 10, 2, etc. dng-frames)
I uploaded the first 30 dngs of the folder HERE, and also a shortened version of the problematic mlv HERE (the original file was 15GB, so I used MLVApp, RAW Correction disabled, codec MLV Fast Pass).

It's probably the version on ML Downloads/Utilities

Apparently yes: same creation date. Perhaps silly question: does libraw.dll matter somehow?

No specified branch but should be included in the binary info I think.

Can you tell me how can I extract this info for you? (In OSX I opened the .exe with Keka, and now I have some docs in a folder. I opened them with an Hex editor and the only one not-in-alien-language is a doc named "19" in which there is written «GNU C 4.9.0 20130523 (experimental) -m32 -mtune=generic -march=pentiumpro -g -O2 -std=gnu99». Is it anything useful? I guess not...)

I'm not really a Windows user and I'm not a coder, anyway the working cr2hdr.exe has been created 4 Dec 2017, and HERE i found Commit 06fae84 dated 4 Dec 2017... Is it anything useful?

It works...
I've no words kayman1021.
With your apps' version my dual-ISOs get solved. I don't even need raw2mlv because I uploaded the DNGs directly into Davinci... and it finally works.

Now, just to be fussy, passing throuh cr2hdr is a "pain-in-the-a@@" workflow: very-very-very time-consuming.

@Danne: is there any future chance to see this sort of "legacy" dual-ISO-conversion option in Switch?

@kayman1021:
As I wrote before, I tried your method without obtaining your clean result. I really don't know why, since I replicated step by step your guide.
The only explanation to this is that probably you are using a peculiar version (an old one?) of cr2hdr.exe
I tried everything, even a super-long workflow with Lightroom and LRTimelapse...
At the moment the best&fastest result I obtained is based on a petty trick:
1. In MLVApp I upload the uncompressed MLV, and I set Off Focus dots, Off Bad pixels, Off Vertical stripes, whilst Chroma smooth 2x2 and Dual ISO forced on Preview;
2. I export uncompressed DNGs;
3. In Davinci the first node is for RAW panel settings, then the second is a layer-node in Color mode: the "under" layer completely desaturated (B/N) and with a strong deflicker, while the "above" layer is a coloured still exported from a "grab" still. Adding just a bit of blur, the dirty trick works, but only because the shot is pretty motionless.
Conclusions: this is NOT the way to go...

MLVApp for compressing the original, raw correction off
MLVApp for extracting the frames as DNG, raw correction off
cr2hrd.exe for processing dual iso to single iso
raw2mlv for stiching the dng frames into a single mlv

Incredibly, I CAN'T obtain the same result... Still flickering, still lines... And I tested all in Windows, following step by step!
So, please kayman1021 may you very kindly make a couple of things for me?
1. Please, tell me the version of MLVApp you are using;
2. Please, link an archive with cr2hdr.exe and raw2mlv.exe you are using.
Thanks in advance.

Incredible! Thank you really a lot, kayman1021.
Unfortunately I can't replay your "Experiment 2"... So please, may you explain to me Experiment 2 like if you are talking to a baby?
1. You uploaded the original MLV file into MLVApp and unchecked Enable RAW Correction? (Or the Correction remains enabled?)
2. In Export Settings you set codec MLV, Compress, uncheck Export audio, then clic Close (or Export audio is enabled?)
3. At this point, you pressed Export selected clip.
4. Now you uploaded the new compressed MLV into the same MLVApp and again unchecked RAW Correction enabled, right?
5. In Export Settings you set codec DNG Uncompressed with Davinci Resolve naming scheme, and Export audio unchecked, right?
6. At this point, you pressed Export selected clips, and so you obtained the DNGs folder.
7. Now you pointed Switch to the DNGs folder, and chose "(d) cr2hdr dualiso processing(CR2)", then "(f) Force dualiso processing"?
Please, explain your detailed workflow.
Thanks a lot.

I thought they were frames from the same film but from different programs ...

Yes indeed: the original MLV is the same, but converted to DNG via 2 different apps (Switch and MLVApp).

[YOU]

I would like to ask which build was this shot with? Also would you mind sharing some short MLV samples if you still have them.

Thank to YOU DeafEyeJedi and to all the guys here for your kind support.
My build is the old Nightly.2017Feb12.5D3123 (it's so old because I started a project in 2017 and it's still in progress...)
I haven't "short" original MLVs (all my MLVs, expecially dual-ISO MLVs, are 1 minute long and up). What I can do is re-linking THIS 6GB file, and adding 3 other "shortened" MLVs (I shortened 3 long MLVs with MLVApp hoping this is the correct workflow: I uploaded and cut-out each MLV at frame 100, then I un-checked the RAW Correction panel, then I exported DNGs uncompressed, then I used "Transcode and Import" function). HERE the link for these 3 short dual-ISO MLVs.
Thanks for your help, I deeply appreciate it.

@adrjork: Found a workflow in MLVapp that somehow gives ok results (not perfect, because after this fix you can see you deal with the problem discussed in this post)

Dear Levas, thanks for having shared your detailed workflow, I appreciated it, but the result I obtained is still unusable: it actually DOES improve things but doesn't fix them: flickering is better but still there (needs to be fixed with a deflicker), reddish and greenish frames are a problem, but the worse thing is... lines, lines, lines. It gets a little better if I put off Bad Pixels, and also using a temporal denoiser does something more, but the result remains pretty unusable.

Apparently nor the reddeercity method can help me...

I'm using 2 different MLVFS systems, the first one is the old Fuse/Dokan Quick Mount with mlvfs.dll in the root drive so a simple right click on the .mlv file in windows explore.

Today I downloaded mlvfs.dll (dated 2014) and PFMAP, and I tried a test on Windows 10. The result is again a variant and synonym of "unusable". Main problem is again: lines, lines, lines (and a little flickering, and all the other stuff...)

That's it man... Game over, man

Found the one I use on my older mac , build date from 11/30/2014 the only difference in this one is there no support for lossless compression (I think but I'm not sure). I didn't check any file with it as i'm not close to my MacPro 5.1 right now , but work with any files from my 5d2. MLVFS.dmg

Thank you so much reddeercity. Also, may I ask to you to kindly post a downloable link of your «old Fuse/Dokan Quick Mount with mlvfs.dll in the root drive». I'd appreciate it a lot (I'd like to test a thing on my machine...)

[EDIT: the old 2014 MLVFS gives the same results as current MLVFS... I'd like to try your old Windows quick mount version.]

So I would think if you compile the commit (bb0bad7) for mac you should have the same as me. here link to the commit bb0bad7

I'm not a coder, so I can only follow hoping someone compiles this for Mac.

Of course Danne (and I'll never do it again in future).
But just to know: do you confirm that when you copy&paste a dng-folder from the MLVFS'virtual-drive to another "real" folder-place is exactly like doing a conversion with Switch (or MLVApp)?

Question about Switch vs MLVFS:
If I understand correctly, MLVFS should do on-the-fly what Switch does saving a new dng-folder. If that's true, the following two things should be identical: making an mlv-to-dng conversion via Switch, or copying&pasting a "virtual" dng-folder from the MLVFS' virtual-drive to another "real" place.
Is that right?

I'm asking this because I noticed that MLVFS maintains the complex naming structure I used for my MLVs (with dots and dashes), and Davinci seems handle it without problems.

Really thanks reddeercity for your help.
But... It sounded too good to be true in a "usable" way: after your post I tried immediately MLVFS and the result is: dual-ISO "Full" on-the-fly crashes/stops Davinci, only dual-ISO "Preview" works on-the-fly (on my machine at least). I tried also setting dual-ISO "Full", then copying the DNG-folder to save it as "offline", and then importing into Davinci (it works, but the result is apparently not SO different from Preview).
Anyway, the result is almost unusable: some frames are good, but the flickering is horrible, and the worst thing is that during the "flicks" you can clearly see the horizontal lines suddenly appear (it's like an old damaged CRT TV... it looks like young Chris Cunningham set my camera...)
I tried to use Davinci's deflicker to limit the problem, and it does something, but not too much...
This is the result:

I think that perhaps I could export deflickered DNGs from Davinci, and then trying to do a final adjustment in LRTimelapse, but even if it improves brightness stability, there are still the lines that appears time to time (the "flicks"). Any other idea is very welcome

Hi, I'm migrating here my question from other topics (Switch and MLVApp) since I've found out that my problem are my somehow faulty dual-ISOs. After the conversion with Switch I can clearly notice the horizontal lines and an heavy flickering. I've tried also MLVApp and the result is even more weird: horizontal lines, flickering, but also bluish tint and vertical lines. The funny thing is that if I set a tonemapping in MLVApp, even if I'm converting to DNG, the tonemapping seems influencing the final DNG, so that in Davinci I can see the two DNGs (from Switch and from MLVApp) as completely different!
Images speak louder than words, so HERE the screen record of the two conversions.
HERE the first-frames of the two DNG-folders.
And finally HERE the original problematic dual-ISO MLV.
I'd like to know how to fix my dual-ISOs (and IF it's possible to do that).
Thanks really a lot.

With proper info all is clear as crystal.

Well... not "all" actually: now it's clear that the problem is the faulty dual-ISO MLV, but it's not clear (to me) how to fix it (or IF it's possible to fix it...) Anyway, this is not directly a Switch problem, so I'll try to migrate my question to the proper dual-ISO topic.
Thanks again

I downloaded your clip and tried my luck. [...]

First of all, thanks really a lot for your help and your time. In the future I'll surely follow your advice of testing builds first. (For the flickering I have in mind a couple of solutions: perhaps Davinci deflicker could work, or perhaps a little workflow's detour towards LRTimelapse...)

You're adressing Luther? But it's my build.

Actually, Luther very kindly advised me to change my old build for your newer build (that's what I'll surely do!)
Anyway, finally I've found out that my two problems (dual-ISO here in this topic, and the case of the different DNGs from the same MLV in Switch topic) are actually one single issue: simply my dual-ISOs. I've posted a screen record HERE, as you asked me.

Now the problem is clear (not really the solution): the case of the MLV converted into two DNGs (Switch-default vs MLVApp-cineon) which are seen differently by Davinci, does make sense because it happens only when the MLV is a somehow faulty dual-ISO.
HERE the screen record.
And HERE the two first-frames of the DNG-folders.
And finally HERE the original problematic dual-ISO MLV.
Thanks a lot.
https://youtu.be/5QffZCwMPjk

You're using a very old build.

Thanks Danne, I'll change the build. But what about my old dual-iso shots? Unusable?

Regarding timelapse sequencing I usually convert my CR2 files with Ilia3101 raw2mlv tool.

Fantastic, I didn't know that software. Thank you!

DNG or any kind of raw has no tonemapping of any kind, ever, at all. If you saw difference it was for other reasons, please explain more.

Thank you so much for your kind reply ilia3101. Yes, as I knew DNGs should not have tonemapping, but I saw a big visual difference importing 2 dng-folders into Davinci. These 2 dng-folders are two different conversions of the same MLV: one made with Switch (leaving all default) and the other one made with MLV-App with Cineon tonemapping and Alexa gamut applied. I imported into Davinci both the dng-folders, and in RAW Panel I set both with BMD Film in Color Space and Gamma. I expected to see the same visual result, instead I noticed a huge difference: the one converted with MLV-App (with Cineon tonemapping and Alexa gamut) has midtones strongly brigther and less saturated than the one converted with Switch (default). Why? Why does Davinci interpret these 2 dngs in different ways? And which is the right thing to do?
Thanks a lot.

Which camera and build are you using? Also, if possible, provide a MLV sample...

My cam is a 5D3, and build should be Nightly.2017Feb12.5D3123
HERE the link of the MLV-dualiso (it's a 6GB file I compressed in .7z with Keka). If you want, I can also upload some frames/dngs of the conversion. Anyway, converting into both dngs or mov give the same result: horizontal lines are reduced but still visible (mainly on the ancient stone columns in the image), and flickering is evident.
More or less, all my dual-iso shots have the same issue, and it seems not to be an MLV-App's specific issue because also Switch gives a very similar result (lines, flickering...)
Thanks a lot.

Check google or create a new post if you can't find your answer in here already.

MY bad, sorry, I can't find in Google anything about how Resolve handles dng(from-mlv) with different tonemapping...

But actually my question was mainly oriented on Switch: which is its default tonemapping? Is there one?
And more generically: converting to DNG (which I'd do with Switch), which is the "most advisable" (if there's one) profile/tone to make the conversion? Or, being DNG, it's insignificant? (Here I mentioned Davinci only because, if it's insignificant, why I saw a huge difference in the same MLV converted in DNG with two different tonemappings?)

Another Switch specific: I saw it can handle CR2 for dual-iso or HDR. I shooted a normal timelapse in CR2s with MagicLantern. Can Switch handle/convert timelapse too?

If it looks ok, it probably works.

This last thing referred to the second question?