Messages

I uploaded cr2hdr for windows and mac(could not compile on ubuntu) and like to test the --wb=exif setting.
https://bitbucket.org/Dannephoto/magic-lantern/downloads/cr2hdr_mac_win.zip

Where can I still find this newer version of cr2hdr?

OK, just so the few fellow 70D users who experience the issue can find the fix here as well:

Thanks to Danne's 6+ years old post I found the workaround for my LR DualISO problem.

If not using this plugin:

1) Convert your DualISO CR2 files with the latest cr2hdr.exe WITHOUT using the --compress command
2) Run exiftool -uniqueCameraModel="Canon EOS 6D" -ext dng . (so that you change the relevant EXIF tag for the resulting DNG files as per Danne's instructions)
3) Import your files into LR the regular way
4) Optionally apply lossless DNG compression in LR via the Update DNG Preview & Metadata command

This way you get properly imported DualISO DNGs (who will still register as shot on 70D, BTW). Compressing them before importing into LR somehow breaks this 'fix' even if you do change the tag.

If using this plugin:

1) Export your DualISO CR2 files as usual
2) Run exiftool -uniqueCameraModel="Canon EOS 6D" -ext dng . (so that you change the relevant EXIF tag for the resulting DNG files as per Danne's instructions)
3) Refresh your LR files with the now externally changed metadata and regenerate the previews
4) Optionally apply lossless DNG compression via the Update DNG Preview & Metadata command

I seem to have fallen prey to this very issue with my 70D Dual ISO DNGs 'mistreated' when imported into Lightroom Classic v10.3. Is spoofing a different UniqueCameraModel still the only workaround?

I'm afraid it's rather too technical for me. What I wanted was being able to use DualISO with Lightroom. Should I try contacting cr2hdr author(s) who might know what this supposed metadata issue is?

What happens replacing exiftool with the latest version (12.32)?

The metadata is once again all there (no profile missing errors in LR, but that, I repeat, wasn't the original issue), but the imported DNG is as overblown as per initial setup (and as OK in Photoshop as ever). That's Photoshop CS6 with Camera Raw 7.0, just in case.

So I gather this is some weird cr2hdr/LR interaction issue? Because I've already begun cutting all middle steps by just dropping my CR2 file on cr2hdr.exe from the latest cr2hdr-win package and then manually importing the DNG into LR and PS, which means this plugin has no hand in it whatsoever. But I doubt I can take this up with LR support, given that I'm trying to feed it a CR2 that had been extensively tampered with

Hi guys! Could someone please help me troubleshoot an issue?

The issue is: here is what my converted Dual ISO CR2 should've probably looked like (this is a jpeg of its ---debug-blend fullres.dng)
And here is what it looks like when coverted in LR via this plugin. (Here it is stopped down to -2EV to illustrate how clipped the highlights are.)

Iterestingly, when I replace the original exiftool 10.43 from cr2hdr.3.0-170316-02-MLV-DEV with exiftool 10.02 from cr2hdr-win 2017-12-04, this issue goes away and the imported file looks as it should (however, this other exiftool version is incompatible with the LR plugin, which leads to metadata problems within LR, so it's not a real solution). I forgot to mention that the issue remained even when I replaced cr2hdr.exe bundled with the original plugin with that newer standalone version.

But the real revelation is that the same DNG imported into Photoshop looks perfectly OK. So, presumably, this is some kind of issue with EXIF metadata that forces Lightroom to import the file with blown highlights?

Here is the original DualiSO CR2, and here is the folder with all the files one might need to investigate this issue (debug DNGs, cr2hdr log, plugin and standalone cr2hdr archives, etc.). My camera is 70D, Lightroom Classic v10.3.

At face value, this looks like the issue mentioned by another uses back in 2017, though I don't see whether they solved it at all.

No, it is not. Nikfreak ported 70D, managing 3 different firmware versions (all going by the same version number) at once and some day had to shift his priorities. As it frequently happened and will happen in the future.
Such remarks "gets so little attention" are not helpful at all and some devs made it quite clear such things make them less interested in working on ML code at all. More like killing the motivation left.

So sorry. Killing the motivation was the last thing on my mind, really.

To whom it might concern: Bilal (he of the 650D/700D fame) had expressed his interest in working on the 70D build, but lack the camera itself: https://www.magiclantern.fm/forum/index.php?topic=25784.msg236046#msg236046

I got the source code from ArcziPL yes, but I can't really do much for 70D without having the hardware, at some point I was going to borrow 70D for some time, but plans changed, I don't mind working on 70D if I got the body.

Since we're probably living on different continents altogether, I just hope you will one day cross paths with a friendly owner of an extra 70D. Will post a note to that effect in the relevant threads.

BTW, isn't it crazy that 70D, being the only ML-enabled camera with Dual AF, gets so little attention?!

To whom it might concern: Bilal (he of the 650D/700D fame) had expressed his interest in working on the 70D build, but lack the camera itself: https://www.magiclantern.fm/forum/index.php?topic=25784.msg236046#msg236046

@elenhil: thank you. I tried exactly what you described. Result: I get the exported stabilized video file. Did you close the cmd window by accident? Or, do you forbid MLVApp to create files in the application folder? : ffmpeg creates a vector file when anaysing the footage and then uses this file to stabilize.

Brilliant! Access rights to app folder (more specifically, not running MLV App with admin privileges) was, indeed, the culprit! Thanks a ton!

Start describing your system (OS+version, app version,...), all your settings (cam+App(receipt and export)), maybe upload the MLV file.

- Windows 10 Pro v20H2
- MLV App v1.13
- Canon 70D running ML v1.12 (https://bitbucket.org/ArcziPL/downloads/downloads/magiclantern-Nightly.2021Apr04.70D112_crop_rec_4k_mlv_lite_lossless_fps_override_focus_stack_sduhs.zip)
- Zero receipt settings except ticking 'Enable FFmpeg vis.stab
- File export settings: H.264 (no mistake this time), ffmpeg MPEG-4 (*.mp4) Medium Quality, Debayer: Receipt configuration, Smooth aliasing Off, Export audio On, no other boxes ticked
- Source file at D:\RawVideo\, export to D:\, no special symbols whatsoever
- MLV App and ffmpeg.exe at C:\Program Files\MLV.App.v1.13.Win64.static\, likewise (anyways, exporting with vis.stab off works OK).

Source MLV file: https://disk.yandex.ru/d/LwpCY0i3jhLp0A

@elenhil: More information needed. Can't reproduce here - all works as expected for me.

OK, what do I do? Is there a debug option for a complete readout of all the info you need?

I'm having this exact same problem with no files whatsoever appearing in my folders after exporting from MLV App to H264.

And before you ask, I have no folder in cyrillic or any other funny letters or symbols, and all the original installation files are present and correct in the MLV app folder, it just won't save the exported files at all. What's going on?

EDIT: I solved it after I figured out Avast antivirus was blocking the applications. I added exceptions to the MLV folder and all MLV .exe files. Woohoo!

My problem was 0-size files, not no files whatsoever (which I did use to get with cyrillic paths), so it's not the same problem. Plus, I disabled my AV and the problem didn't go away.

And, just so we're clear, regular encoding without enabling vid.stab works OK.

The instructions and the vid.stab-enable-checkbox tell, vid.stab only works for H.264. So when choosing anything else you should get a non stibilized video, but never a 0-size file.

Oops, a typo. I meant H.264, or course!

Any ideas why trying to enable vid.stab invariably produces a 0-sized file? I do try to exit is as a H.264 ffmpeg, as per instructions.

P.S. I mistyped '265' the first time.

Am I correct thinking that DualISO video on 70D is almost unusable because no build has working 1x3 binning (seemingly a prerequisite for DualISO video without extreme aliasing)?

upd: found the answer myself

Are more samples still wanted?

Bilal, sorry to ping you in the wrong thread, but did you get any luck obtaining ArcziPL's source code? I would really love to see your work combined for a better 70D experience.

More to the point, is the 70D community a thing, at all? 

Is there a working 70D build with 1x3 binning (anamorphic)?

I'm completely new to ML and am just cutting my teeth at this whole thing. My first snag is that I can't seem to download my trial videos (though I can see them in-camera thanks to mlv_play). Does this mean I can only download them via a proper card reader, not via Canon's default USB cable connection (or wifi)?