Messages

Seeing as this is a paid product, I wonder if anyone here actually used it for MLV processing

Got it, thank you.

This error "correction" is a main task in sensor data manipulation. It won't be seen in most cases (there are some well known exceptions which got fixed in a hurry) but ML's way to treat data is a bit different. You may say "not as sophisticated".

See https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6386896/

Sorry, your reply has left me somewhat mystified. Could you please expand on it? Do you mean to say that a FRSP (а very much "ML" way of acquiring data from the sensor) will always be prone to this phenomenon, while a "regular" photo, or even video (a "Vanilla" way of doing it) won't?

The "black sun" effect is a well known phenomenon with CMOS camera sensors -- it has nothing to do with Magic Lantern.

Here is one way to fix it in post.

Strange. I've been shooting stills with other Canon cameras for quite some time, and never encountered this phenomenon; the overexposed areas were always white.

Anyway, might there be some other means of fixing it without tracking and masking involved? Something at the DNG conversion stage, perhaps?

I've been trying to shoot a timelapse with FRSP, and some of the frames got the sun in them. Since I was using AETTR, the sun was, naturally, overexposed. But compared to regular photos or videos, it was black!

Is this a side effect of FRSP? Or of converting the resulting MLV container into separate DNGs? Can it be fixed in post-processing?

So, how's it doing?

Disregard that, sorry

Genius! Thank you very much, Walter!

Huh. Neither 60D nor 70D have the menu items under RAW video that you described. Oh, well. I do get the level displayed during recording anyway.

It's just that I can't find the level data. I had tried opening these MLVs with mlvfs, thinking these would be in log file inside. mlv_dump is new to me. I can't wrap my head around its structure. MLV_DUMP <myfile>.mlv -m -v seems to consist mostly of VIDF blocks. Is there a way to output just the ELVL blocks?

My settings:
Level enabled in ML overlay menu
MLV_REC allowed to use overlays
Preview option "Canon"

I'm afraid I don't recognize the last two options. Could you please elaborate?

Is there some additional setting I need to turn on (besides electronic level) to log this data? So far the log file inside my MLVs is empty.

Thanks a ton, Walter!

I wonder if it is possible to log and export real-time electronic level data to a sidecar file, to possibly use it in postprocessing for stabilization purposes?

The feature comparison matrix says mlv_lite isn't supported on 1100d. Is that still the case?

Kudos!

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?

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.

Is ML on 1300d still missing some essential features? Because otherwise this thread would've been stickied, right?

70D, 5.5k 1x3, dual pixel af on with stm efs lenses, steadicam/gimbal, cinematic moving scenes.

No 1x3 for 70D yet, though...

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

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)

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.

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

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?

Oh, cr@p. But thanks for the heads-up (not no mention the original port)!