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.


Messages - elenhil

Pages: [1] 2
1
Camera-specific Development / Re: Canon 1100D / T3
« on: January 07, 2022, 09:51:52 AM »
The feature comparison matrix says mlv_lite isn't supported on 1100d. Is that still the case?

2
Camera-specific Development / Re: Canon 1200D
« on: December 24, 2021, 07:02:36 PM »
Kudos!

3
Camera-specific Development / Re: Canon 1200D
« on: December 24, 2021, 02:46:17 PM »
1200D has limited write speed, mostly it is 21 MB/s as many DIGIC 4 cameras,
Bilal, this page claims 1200d can write at 44 MB/s. Can you comment?

4
Camera-specific Development / Re: Canon 70D
« on: November 29, 2021, 06:48:31 PM »
I cant change fps. My default is 25p but when I applied 5x zoom it gets broken. And as far I know normal shutter in deegres at 1/50 is 180.
Crop mode indeed changes FPS override settings (at least on my 70D). You need to set it after entering crop mode, that's all.

5
Camera-specific Development / Re: Canon EOS 1300D / Rebel T6
« on: November 09, 2021, 07:04:57 AM »
Is ML on 1300d still missing some essential features? Because otherwise this thread would've been stickied, right?

6
Raw Video / Re: AI algorithms for debinning
« on: November 06, 2021, 01:12:12 PM »
70D, 5.5k 1x3, dual pixel af on with stm efs lenses, steadicam/gimbal, cinematic moving scenes.
No 1x3 for 70D yet, though...

7
Modules Development / Re: Full-resolution silent pictures (silent.mo)
« on: November 05, 2021, 04:43:27 PM »
Can someone please help me troubleshoot my issue?

Something goes wrong with the LCD power off control when I try to combine FRSP with AETTR and/or Intervalometer. The LCD won't turn off after reviewing the pic. Naturally, I have Canon review on and LV Power Save timers on.

1) If a FRSP was taken with AETTR (with the Auto Snap trigger) and the exposure was OK (no correction from AETTR needed), the LCD turns off.
2) If a FRSP was taken with AETTR (with the Always On trigger) and the exposure was OK (no correction from AETTR needed), the LCD turns off.
3) If a FRSP was taken with AETTR (with the Always On trigger) and the exposure was wrong (AETTR had to make a correction for a *future* pic), the LCD turns off.
4) If a FRSP was taken with AETTR (with the Auto Snap trigger) and the exposure was wrong (AETTR had to make a correction *and* take the Auto Snapped extra pic), the LCD turns off after the first pic but doesn't turn off after the *extra* one (stays on indefinitely, save for actual FRSP capture, of course).
5) If a FRSP was taken with AETTR (with the Always On trigger) plus the Intervalometer, regardless of AETTR's reaction, the LCD stays on displaying the last reviewed pic (with the ETTR and Intervalometer readouts).

Obviously, turning off AETTR and/or Canon review makes the problem go away (but neuters ETTR). The same goes for choosing regular shuttered pics instead of FRSPs. It's just the combination of the three (clearly very desirable for timelapses etc) that fails.

Any ideas? Perhaps someone could review the code and find out what goes on in cases 4 and 5? I'm using ArcziPL's experimental build for 70D (Bilal also has his source code, in case you need it).

8
I'm trying to shoot a timelapse with FRSP and ETTR. I get it that AETTR needs to have Canon image review to be on for at least 2 seconds. Problem is, the reviewed picture (along with all the intervalometer info) stays on indefinitely, no matter the Power Saving in LV setting. So the only time my LCD turns off is during the actual FRSP capture. Then it's on for review again till the next intervalometer step (regardless of Canon's 2 sec review and ML's 5 sec LV powersave).

Any ideas why that might be?

P.S. 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)

9
Sorry, because this thread is quite old, but: i still can't use LR deflicker plugin, and i just get that message:

Unsupported PPM format -> Expected a binary RGB (P6)

LR CC 2015
CR2 files from a 7Dmk2

Any help, please?
edit: i'm using the plugin version of the previous post, from the release page.
I'm having the exact same problem, though in my case it's FRSP DNGs.

10
Unfortunately, that doesn't explain much to me. The thing is, I'm trying to make a FRSP timelapse with DualISO. And the way ETTR turns DualISO on and off seems inconsistent (like, three shots 20 seconds apart, the first and the last ones has DualISO while the middle one doesn't). Since I can't get any kind of log, I suspect that the ones without DualISO are probably the ones with 'ETTR failed' (because that's what I get in regular photos where ETTR fails - no DualISO setting).

11
What does the 'ETTR failed' message really mean? Does it mean that the algorithm simply cannon find an optimal setting for the scene, or that there is some genuine module error involved?

12
Camera-specific Development / Re: Canon 70D
« on: October 15, 2021, 08:10:29 PM »
Oh, cr@p. But thanks for the heads-up (not no mention the original port)!

13
General Help Q&A / Re: Green and magenta artefacts on DUAL ISO output
« on: October 13, 2021, 11:53:38 AM »
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?

14
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

15
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?

16
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?

17
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 :)

18
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.

19
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.

20
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

21
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?!

22
Camera-specific Development / Re: Canon 70D
« on: October 05, 2021, 04:01:26 PM »
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

23
@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!

24
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

25
@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?

Pages: [1] 2