Messages

I don't believe any dev has that cam, and thus no work is taking place on it.

I do, but it is waiting in a pile of untouched Digic 8 cams until we confirm we fixed our favourite Digic 8 bug.

It must be years (if not a decade) since last cam got bricked during development. Today it is better understood what to do and what to avoid. And the tools have changed, too.

In fact, at least from my camera collection I almost exclusively have cameras I bought broken and fixed it. And to be honest, from what I see (after constantly watching EU broken cam market for opportunities for what, 2 years now?) they are usually hardware problems.

Even that one time I had 1300D with what was seemingly software issue, it turned out to be a bad flash chip that was returning garbage when running on expected voltage. It was successfully dumped externally while overvolted and replaced with new one

From ML code perspective: We know quite well what not to touch and what can cause real issues, so we don't ship that parts until very well tested. That doesn't mean something can't slip in the limited testing we can do, but we also have a pretty good track record on fixing cameras broken by one particular unofficial build that was not very well tested... Just remember to keep your ROM backups for each cam running Magic Lantern and you should be safe

From what I know, old (like A7s Mk I that I had) generations were running Android, thus OpenMemories hacks were possible. No idea about newer generations.

You will gain no benefit with a UHS-II card, the cam only supports UHS-I.

Adding to the injury: Fastest UHS-II cards may not deliver outstanding results in UHS-I mode.

This is great news! Is there a way to get updates via RSS about new ML releases? I used to use https://builds.magiclantern.fm/jenkins/, but I see that's gone.

It was a great way to get releases about the cameras I use and nothing more.

Hey,
Jenkins is very long gone and for a good reason - public Jenkins instance is a security threat more than anything else.

At the moment, downloads website is a static content generated from script and not fully automated.
Pelican (author of EOSCard) also requested some kind of file with metadata that their software can pull, so we will look into it in future.

As a summary: This is Hello world running on Canon EOS R8

But I have some bad news: As for now we don't know any good method to enable Magic Lantern (autoexec.bin / enable bootflag) to run on this model - we need a new way in as our old methods are now blocked (Basic script doesn't work anymore ).

Since R8 is a DIGIC X camera, all the issues described in R5 thread still apply. If you don't want a technical mumbo-jumbo but rather a general description what's going on, check out Digic 8 and Digic X parts of this post in "Current state of Magic Lantern project" thread

This will be even more fun as we found on Discord that since R5/R6 Canon is actively updating some areas like GUI code that were mostly the same since at least Digic 4. Our core will need even more adaptations than R5 took to get the PoC working.

But having Bilal work on this is promising, as due to the lack of understanding how Digic X memory management works, I was not going to touch it myself in any foreseeable future.

It's there any documentation about more technical findings on registers and functions, besides the code itself?

The documentation is very lacking.
There's this, but it is very hard to read even for us: https://magiclantern.fandom.com/wiki/Register_Map
It is often we got "eureka moment" after first reverse engineering a thing and then finally understanding the docs or code 

We are taking some efforts to put documentation on the new Wiki, but this right now exists just for the D6-8 cameras, eg.:
https://wiki.magiclantern.fm/digic6:registers
https://wiki.magiclantern.fm/digic8:registers

Any help of converting in-code and Fandom wiki docs into easily digestible info on new wiki will be really appreciated. A lot of knowledge was unfortunately lost.

And on a technical note: We have issues with the Canon code we use for intervalometer functionality on older models. On R it lead into camera misbehaving. Thus wouldn't hold my breath for it to be available whenever the first public builds arrive.

That would be great, let me know where I can get started and I'll start working on it.

The easiest way is to join our Discord channel, we do most of the development work there.

I get that it would be too hard to get all the improvements on the main branch in a way that are not messing with the "one code base for all" strategy, I'm just thinking at loud

No, the goal is to merge all features back. In ideal world people wouldn't use forks as all features would be ported back. Of course due to lack of official activity in the project every dev was doing own fork which made it more difficult to handle. But you know, ML itself had like a hundred branches in the official repo itself...

Just consider this: We are working on this project since 2020. No new active devs since I joined. People thought project is long dead. Shall we wait another 2 years to blindly integrate the features? How do we test this without any audience? Will we attract any new devs this way? Will we still want to work on this in two years from now?

The project needs momentum. In open source project momentum comes from both developers and community. If names_are_hard gets bored we will be back roughly in the same place we were 5 years ago.

Instead we made this bold announcement: Magic Lantern is not dead, work is being made. We finally cracked newer generations and they get some features. There's a lot fixed in the background, it is easiest than ever to join as dev and get your first build. Names did the tremendous work to merge all main branches from the old official repo into a single branch - thus achieving the first step of re-uniting everything. We also have a plan on how to move forward.

People noticed and the community reaction is overwhelmingly positive. We hope that will in turn help to get to the goals faster: more people using it means more feedback. More audience means we maybe find that few unicorns with both skill set and ambitions needed to join the dev work

All depends on a few things:

- Camera availability in devs hands
- Devs interest in taking time digging into it
- All the problems found in a way

The main issue is right now most of the work is being done by names_are_hard, I do some inputs whenever I can. This is "less than two people" maintaining 20+ models with more to come. And remember we all do it in our spare time, for free.

I always wondered how this was possible in the past. And recently learned that in its heyday Magic Lantern had basically a single maintainer per camera model.

Magic Lantern is based on top of Canon firmware and hardware, thus it is impossible to port it as is to other cameras.

We already know how to get (hardware!) zebras on newer models, and what's best - that seems to allow both over and underexpo with different styles/thresholds visible at the same time.

This is not yet integrated, but definitely will be in future.

As for focus peaking, I don't think it was explored yet.

Re autofocus, can you give me more info?  I'm far from an expert on using all of these cams (I do own a 750D).  I'm not aware of what these changes in AF capability are re HDMI.

I understand this as a question of if we will have a proper clean HDMI output in the future. Now you can fake it by toggling off Canon overlays, but the focus one stays on screen if you have AF enabled.

Answer is: We know at least two ways how to do it, but it is not integrated into codebase yet

Looking like some updates, good for the d6 and up but I see no love for D4 ,
Where did all the Experimental builds go to on the download page ? crop_rec,10bit mlv_rec, etc. ..
All I see is basic vanilla builds , functional at best (sorry done mean to upset anyone)
it like that whole download page gone. Or is it that you don't what to update/support D4 Camera anymore ? just check the latest 5D2 download "magiclantern.2025-06-20.5D2.212" , not many thing work well,(wondering if any one did test before the build was posted?)

Hey,
truth is between me, Names and Walter there's not a lot of Digic 4/5 cameras we can run any tests on. And the entire old "qemu testing framework" is gone - those tests relied on a very specific ROM dumps we don't have access too. Unless I will find them somewhere in server files as I'm still digging through those.

If you see any bugs, please report them. There was a lot done in the ML source code internals, if there's a regression we will try to fix it. Of course that needs a bug report and someone to test if the fixed code works

With Walter we decided the only "old relevant" builds to keep for now were Lua fix and latest nightly. New builds merge multiple branches (nightly, crop_rec_4k, lua_fix, probably more - Names will remember).

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

But we don't understand how to control EDMAC on Digic 8 (it has different hardware than previous generations) so it was a sheer luck we found a working combination to do it at all. There was no attempts to do 1:1 zoom modes recording and with our current knowledge 12/10 bit and lossless can't be done. I mean in terms of "we don't know how to configure hardware to achieve this".

Digic 8 has more problems, it requires much rework in our codebase (Canon changed data structures for basic things like ISO or Aperture values in a way those are incompatible with our core data structures), and - as Names pointed out - for a good 3 years or more we are trying to catch major instability problem on those platforms.

I would like to explore possibility of such literally "unstable dev super-pre-alpha" Digic 8 builds in foreseeable future, but they will be fundamentally broken in many areas and targeted towards chasing the root cause of mentioned unstability. But that for sure won't happen before, or close to first "reboot" releases.

I don't want to cause any trouble to the people handling the group, I just find strange that new post are not being approved for quite some time and I know no other way to reach the admins

Nah, that was not the intention of my post. I know there are a lot of similar groups, just found it interesting people from ML mod/dev community have admin capabilities there and we missed that somehow

In fact some time ago I wanted to join that particular group from ML fanpage account but unfortunately it is locked from being joined by pages.

We had some internal discussions on how to make a clear distinction between "official builds", nightly/development "official builds" and "community builds" for the upcoming reboot - since for now everybody just uses "Magic Lantern" name and logo which is not always the best approach.
I was exploring use of Magic Lantern name / branding over the internet groups, etc and IIRC that was in fact the biggest group I found back then.

You might be one of the very few people in the forum that are not aware of "the" facebook group
https://www.facebook.com/groups/mlvraw

The admins are also forum users, that's why I posted it here

Which, considering rn I'm de facto admin of all official ML social media is a bit worrying there's "the" group we don't even know about and even ML developers are admins. Names was also not aware.

I've heard of this group, but it somehow missed our attention that Bilal is admin there.
Thanks for explanation. I ping'd Bilal on Discord.

What Facebook group?
We don't have any official FB groups, only FB fanpage.

Let me add to the news:
We re-gained access to (what we thought was) long gone official Magic Lantern Youtube channel - yes, the one with ML v2.3 promo video from 12 years ago! (and also to ML Vimeo account)

It took almost 2 years of digging and trying to contact people who in many cases left this community many years ago. But we got lucky and after I was able to get in touch with @Bart we found out that by sheer luck we was still able to get access there and get me rights needed for the channel management.

No posts = no progress, this has never changed.

This is unfortunately lack of resources and helplessness fighting with bots. Reality is that 95% of registered accounts were spam bots anyway and this project lacks manpower to work with it. We literally deleted a few dozens accounts daily, and tbh there's not a single moderator available that is willing to spend so much time on useless work.

We are aware of most of those issues, but have no solution available to any of them. If you know any good anti-bot measure for SMF forums, that runs on SMF 2.1.x - we will be happy to test it out, removing most of existing measures in place.

Anyway, I corrected the twitter handle question to accept "@" answer, and rephrased another question into "For which camera manufacturers Magic Lantern is available?"

Re: general challenges - those questions are designed to require reading 2 lines of text and visiting home page to find answers for other questions.
This variant was somehow successful against spammers, which is contrary to other security questions we used earlier.

I also took the liberty of editing your post to hide the answers.

I guess that's a duplicate of https://www.magiclantern.fm/forum/index.php?topic=27198.0 ?

Won't happen. M100 runs PowerShot firmware flavour - thus it is CHDK target.

So I went to discord and asked about it and they told me that there never will be a 80D version of magic lantern

Who said that?

Could you please update us of your intentions about the 80D firmware ?

There are no intentions. Digic 6 is just hard to get working due to its unique design. It is just easier in later models running Digic 7 and 8.
Remember this is just a hobby project of a few people. We work on it when we feel like it, and work on what we want. I have a pile of 10+ Canon cameras and tbh I favour EOS R as it was my re-entry into Canon ecosystem - and also my entry into Magic Lantern / camera hacking world.

I think quite a few models got magic lantern a lot sooner than 80D

Then you are wrong - right now they exist just two "builds" of Magic Lantern for newer models: one for EOS M50 - which does nothing except card benchmark. And one for 200d which also doesn't have almost any features - it was released as a proof of concept that project is still alive.

I think you should get familiar with Current state of Magic Lantern project. This will answer many of your questions.

I bought a new motherboard from Aliexpress, installed it and nothing happened. I am going to keep buying parts untill i will changed everything.

Honestly, that was not the wise idea. Probably you paid more for that board that camera is worth itself.
I'd look for a faulty shutter unit and then... just swap parts until it works.