Magic Lantern 2025: Midsummer Edition

[kitor]

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

[SebastianC]

I would like ask, is these four camera all support recording FHD 1920(or around) Raw video?or just basic functions? Thank you !

[BackintheDSLR]

I would like ask, is these four camera all support recording FHD 1920(or around) Raw video?or just basic functions? Thank you !

No raw video yet, details are linked in OP:

Newly supported cameras:
- 200D (Kiss X9, Rebel SL2)
- 6D2 (6D Mark II)
- 750D (Rebel T6i, Kiss X8i)
- 7D2 (7D Mark II)
(cam specific discussion can happen in these threads)

More detail is given in the separate threads, but generally the new cams have utility features such as:
- intervalometer
- custom crop marks
- shutter count
- 30 min LV powersave disable (good for HDMI out webcam mode)

[BackintheDSLR]

Hi
Long time user first time poster.
Just want to express my thanks and appreciation for keeping this project alive

see also

https://discuss.pixls.us/t/magic-lantern-is-back-ready-to-kick-ass-and-chew-bubblegum/50805

Two announcements threads atm. at https://www.dpreview.com/search/forums?query=Magic%20Lantern&only-threads=yes - no real buzz yet

[Slade]

Great to hear, C is not hard to learn, it's a small language.  You could have a port some time next year if you start now   We can give you good advice.

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

[kitor]

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.

[chawla.shray]

Can we expect a build coming for Canon EOS M6 Mark II?

[names_are_hard]

There is nothing planned for M6 II as no devs have this cam.  It's a nice cam and I'd like to support it.

[iaburn]

There is nothing planned for M6 II as no devs have this cam.  It's a nice cam and I'd like to support it.

Once you said that the M5 was not a Magic Lantern target because it is PowerShot-like.
Is it any different for the M6 II?

[Walter Schulz]

Is it any different for the M6 II?

There is aew FAQ entry for that.

[iaburn]

There is aew FAQ entry for that.

I'll check it, thanks 👍

[nikfreak]

Well done and congratulations. I am very proud for you.

[Walter Schulz]

70D and 100D now in main repo ... ;-)

[notthesame]

Congratulations to this achievement! May the force continue to be strong with you and your noble cause!
It feels good, to have a more sustainable model for camera hardware. Thanks for making severely crippled hardware usable for way longer than it's creators intended.

[Skinny]

Hi guys, just one small question - where should we discuss these new builds for older cameras (d4)?

[Walter Schulz]

https://www.magiclantern.fm/forum/index.php?board=34.0 -> Search for cam thread.

[mothy]

Is there a link where we can go read about what bugfixes are included in this release for the EOSM?

[names_are_hard]

Not really.  You could go through the last 5 years of commits and try and work out which might be relevant, but I don't think either of us wants to do that

It is quite easy to try different builds, so the quick way will be trying both and seeing which you prefer.  If you want a working real time preview while recording, you don't want the new builds yet.

[Walter Schulz]

Is there a link where we can go read about what bugfixes are included in this release for the EOSM?

That's one of the features I want to have in the future:
- Get build info from cam
- Using this info you get linked to a site (via smartphone, ...) and get info
-- which updates you missed
-- what was fixed

So you can decide if it is worth updating to newest release.

But we are not there yet. And maybe it will not happen!

[names_are_hard]

- Get build info from cam
- Using this info you get linked to a site (via smartphone, ...) and get info

Easy enough, probably a QR code that links to commit in repo or build zip.

-- which updates you missed

Also fairly easy.

-- what was fixed

Harder, because it's difficult to automate.  Linking to something like the tech summaries I make is practical but a bit of work.  Being sure we list every change that might be relevant for X cam is quite a lot harder.  If we did all work via tickets and ensured all closed tickets linked to a relevant commit, we'd capture most but not all of it.  But that's more work.  So it depends what you want.

[Walter Schulz]

About last one: I think it would be sensible to include at least
- if a build fixes an issue (bug/ticket) reported via github: Issue number and short description + link to issue report
- if a feature/module was added: Very short description, link to further information (help text, tutorial, ...)
- relevant changes to menu. Like changing order for tabs, menu items changed location, etc. Not about fixing a missing comma or spelling error.
- The rest is open to discussion.

[names_are_hard]

- if a build fixes an issue (bug/ticket) reported via github: Issue number and short description + link to issue report

I assume this is easy but haven't checked.  Needs some way to check for commits ref'd in GH issues.  They have this, I don't know if they expose it as an API.

- if a feature/module was added: Very short description, link to further information (help text, tutorial, ...)
- relevant changes to menu. Like changing order for tabs, menu items changed location, etc. Not about fixing a missing comma or spelling error.

These are manual (unless / until we get fancy with qemu) but should happen rarely enough that it's not a problem.

[goldenchild9to5]

Longtime 5D Mark III Magic Lantern user, soo.. excited you guy's are back. 

[jw2k_fr]

Great to hear, C is not hard to learn, it's a small language.  You could have a port some time next year if you start now   We can give you good advice.

Thank you to EVERYONE who has helped to keep ML going.  I am truly surprised to be reading this post as it's pretty unusual for these kinds of projects to rekindle.

I'm another one keen to see an M6II build.

I'm unlikely to be able to help much with coding, although I do have some programming experience (a little, and it's been over 10 years) but I am a decent beta tester and have hardware available.

Given that a few of us have specifically requested support for M6 II, what would be the best way to facilitate that in the context of (what I understand to be) a single, multi-model build?

Also, is there going to be a way to support the development process - a kickstarter to pay devs or buy hardware, or buymeacoffee, etc?

[reddeercity]

Please help me make it better.  If you find reproducible problems, I will work to fix bugs.  The official repo should build easily, if you want to add extra logging, etc.

Ok I will ,
 
I'm not a fan of the current status of the builds , in the pursuit of making thing better on D5
cams the D4/5D2,50D suffer performance and functions'/features e.g. Dual ISO Video (not dual ISO photos)
that's been a working feature since Aug.2020 & of cousre Crop_rec 4k 3x1, 3x3 48fps (1880x776) 3k crop_rec(my work here)
There's nothing in the main build with these feature , I do see 10bit in MLV_lite , i had that in mlv v1.0 since 2018  I'm using "raw_slurp" etc. ....

So I'll need to go over all the features & functions in both Photo & Video mode and compare with my builds
Just a note i still love the Raw record we had in the old code , it made the 5D2 shine like a King, i still use it from time to time , (over the year i've been thing about building a Strip down version of ML just to record Raw video without any other features, but haven't found the the time.

I want the official repo to work as well as possible on all cams.

Yes I agree , I do my best to bring D4 cam in the that

Just because quick discussion is much easier in a chat app, I do recommend you join Discord: https://discord.gg/vJCWmmRJhb
It works in a browser, you should just need to click that link.  It would be great to have more devs involved!

I'm a Old Dog , But I can learn new trick from time to time 
Ok I'll give a try one of these days soon , I'll need to figure out how the protocol work in that kind of environment