Issue: latest memory backend prefers SRM for very large buffers, but these can't be kept allocated during a still image capture. Raw_diag: fix BUSY screen with 2-shot analyses in still photo mode Magiclantern-lua_īug in testing code, triggered by camera running out of memory.ĬMOS/ADTG/Digic register investigation on ISO Therefore, it's important to give it a good try on all functions, not just Lua, so we can include it in the nightly builds.Īlso includes lens.focus_pos and dynamic-my-menu. focus, menu, Q button handling, fonts etc. It’s weather-sealed, after all.Includes many other backend changes, e.g. These are the earliest of early days, remember. Canon is not liable if my camera breaks, so I’ll get to use it as a doorstop, or even a sailboat for a guinea pig. Joking aside, I am just excited to experiment. I am not worried about bricking my camera, because it’s already a brick with a 1.8x crop and rolling shutter to make the leaning tower of Pisa look straight. The probe was able to display a green screen (see video below) – which demonstrates the possibility to change camera registers and execute code on the main processor. This is big news because it means Magic Lantern code was able to execute on the EOS R as normal. The next firmware update “RLEDID14.FIR” was successfully loaded by the boot loader and firmware update program in the EOS R from the Canon firmware update menu. The error message is the same as on previous models and that’s encouraging however, I’m unable to figure it out by brute forcing.Ī1ex hadn’t realised I hadn’t yet tried both firmware updates 🙂 Whatever worked on all models from 50D to M50, it no longer works here.

They changed something in the file format, possibly also the encryption.

Magic lantern canon sl2