Messages

For faster communication follow our discord invite.

- copy Portable Display Test autoexec.bin to card
https://www.magiclantern.fm/forum/index.php?topic=2296.0

- Remove battery
- Insert card
- Close card compartment door
- Insert battery
- Close battery compartment

Report results via discord. You should be greeted with a diagnostic screen.
Remove battery after test.

5D3 and 6D2 have been reviewed by various reliable sites. Please take a look for yourself.

https://www.photonstophotos.net/Charts/PDR.htm
https://www.imaging-resource.com/IMCOMP/COMPS01.HTM -> Select "All cameras" to view older cams, too
https://www.dpreview.com/reviews/image-comparison

This feature is not implemented for 5D3 and 6D. Sorry!

May I ask why you want to lower bitrate?

You don't need to run installation again.
If your PC is running Windows: Run EOScard utility to make CF bootable.

- Copy extracted build content to CF (Autoexec.bin, ML directory/folder. ML-SETUP.FIR is optional).
- Run EOScard utility as Admin.
- Make sure to have your CF drive selected.
- Mark boxes for EOS_DEVELOP and BOOTDISK
- Press Save button

Done.

Insert card into cam and startup.

Technically R has all the hardware to do 1080p60 on a fast card, and with code I have on branch it can record full sensor width 1080p60 uncompressed 14 bit RAW with I believe line binning (that was checked by Walter).

At least strong indication. 5D4 and R may use the same sensor type. At least 1080p30 mode seems not to use line skipping (not sure I tested 60 fps).

BTW: 7D2 doesn't use line skipping either. The only Canon APS-C DSLR AFAIK.
BTW2: I kicked pre-ML from my R. Just beyond useless.

Or get yourself a 550D and help finding out where button triggering BGMT_PRESS_FLASH_MOVIE is located, what it does and why we have 3 related events. /s

That's good news!

You should follow our discord invite, drop by development_101 and get advice for starting points.

Most short term info is shared there.

Quick question for those who've tested it: how stable is the build during longer recordings? Any overheating issues or dropped frames?

Overheating is an issue with this cam. There is a reason for M-Lite mod including active cooling.
A small fan may be helpful (a bit). Of course it makes handling not easier.

What code do you guys use for development?

Plain C, mostly.
C99, to be precise.

Keep in mind about viewing conditions "in the wild".
Viewing high contrast content requires optimal lighting. The kind of non-lighting you find in a movie theatre. No disturbing light or your dark areas will get lost.
My dated non-HDR, non-OLED monitor is only able to show its full potential if i pull down the blinds during daytime.
If you are sure all your efforts will not be lost I would think about 2 options:
- Damn the highlight showing in lamp and reflection and fix it in post.
- ETTR the hell out of it as you described.

Balancing base ISO and extension remains a balancing act. The further you stretch between both the higher the risk of getting visible artifacts. I have to admit not to be a big fan of Dual-ISO. I avoid it most of the time. That's easy because my kind of work doesn't force me to use it.
Maybe I'm the wrong person to be asked about Dual-ISO for movie making. ;-)

Moiré is unpredictable and we have no way to reproduce your environment.

In cams like 5D3 with "banana-shaped" DR curves I use ISO 200. According to Photons To Photos you lose just 0.2 PDR but gain 1 EV.
With this setting I would rather use 200/1600.

Also: Are you sure about ISO 80? Haven't experimented that much with tweaking this setting, though.

Thanks! Didn't catch that! ;-)

Thanks!
Cream on top if you are able to share two pics with Tv/Av/ISO used for video (ISO=base and expanded as used in Dual-ISO). Don't change focus, please!
I have a suspect and with those pics it would be easy to tell if I'm wrong or not.

Maybe start to tell the build version you are using and your Dual-ISO settings.

If able share a short unprocessed footage file.

Advice would require some basic info about the build and settings you used.
Same for postprocessing tools and workflow.

anybody have the tutorial to install this build:?
magiclantern-crop_mood.2024Jul03.EOSM2103.zip

Short:

https://builds.magiclantern.fm -> EOS M 2.0.2 -> Installation

Replace
1. Make sure you are running Canon firmware 2.0.2
By
1. Make sure you are running Canon firmware 1.0.3

Long:
Top of page -> Wiki -> Install Guide

Low-level format cards in cam and retry.

Thank you!

I think you are aware that Dual-ISO processing is hampered by design. In its current implementation it works with a single thread and this is not only a shame but slows down processing big time!

If (if!) someone finds a way to make it multithreaded and it - cream on top - is portable ... big win!

This is much to ask for and I don't: If you go with "plain" Dual-ISO processing it would be great anyway! ;-)

Nice!

May I ask you to change subject line?
Title is quite generic and that's not user friendly (IMO). Title should make transparent that you created an import plug-in for MLV footage for OpenFX.

I already moved your post to "Raw Video Postprocessing".

Thanks for your work and contribution!

Q: Dual-ISO support?

Nice!
Thanks!

I don't think this is the proper way to use keyframes.


About timer options: Have you looked into Lua scripting? You can stop intervalometer by command and you can use cam's clock taking the first picture by 06:00

Link to ML Lua API and some scripts: https://builds.magiclantern.fm/lua_api/modules/property.html

Info for readers:
Some discussion took place in our discord.
OP still undecided so feel free to add your 2 cents.

I think the card is broken (it's a komputerbay 128gb 1066x). Can't make any card reader see it.

If you go for a replacement: I purchased some Integral Ultima Pro 1066x lately and they perform very well so far. And here in Germany they offer a very good price/GB ratio.
128 GB goes for 63 Euro and 256 for 129. Two weaks ago price for 256 variety was 93 ...

Komputerbay 1066x CF cards come with a warning label: Do not use in UDMA-6 devices. Or else!
They will get damaged. 5D2 got an update to handle UDMA-7 cards nicely.

Yes, there is a chance cardreader is the culprit. But cannot exclude UDMA-7 card acting up, too. My knowledge how 5D2 and 5D3 handle UDMA protocols is non-existent.

And thanks for asking! Good to have you back!
BTW: Discord is a faster communication channel.
We hardly use forum for anything else than documentation, long term things in general anymore.