Messages

From what i've tested, most features seem to work well.
The only problems I found:

Focus peaking only works on high resolution mode (which is not very good on low-light conditions);
Magic zoom isn't working at all;
Viewing a MLV and exiting the viewer crashes the camera sometimes.

Thanks for the port. Hope to see it progressing.

[.de]

I'm now ready to do the job for 100D. One caveat: 100D has at least two know firmware revisions. Read through the 70D thread to understand what this means. Now I would like to get my hands onto a 100D + pancake lens to maintain the 100D. If you wanna help (got a wishlist on .de) please PM me.

Sent you a PM.

Hey, i'm the guy who tried to port it some time ago, but because of a lack of knowledge on the ML world and some developers probably busy and stopped replying me i did give up.
But i'm so happy that someone experienced did take the lead and we got an Hello World. Thanks Count! Hope this port will end sucefully, and if someone need any help with testing or some not-complex developing, ask me.

In the main page of ML site http://www.magiclantern.fm/ the SL1/100D is said as supported also.
Maybe someone can remove it please?

This should probably be added as a big red blinking warning on the ML homepage: If you want ML, but a camera that supports it right now (at least to a working degree like 6d) and ... do. not. expect. any. further. ports. no. really. we. mean. it.

Or less posts like this: https://www.facebook.com/magiclantern.firmware/posts/470244706398806

Hi!

First of all, a big thank you to all of the ML developers, you guys are doing a great job.

I just want to express that ML did confirm that Magic Lantern will run on 100d at Facebook, and some developers did promise that they will continue developing ML, but now I know that the original developers had ditched the project. I'm not hating them, I understand they are using their own time to develop ML, but I'm just really disappointed.

I haven't bought the 100d yet, but considering there's not yet any ML for 100d, I am thinking of getting the eos m instead, though I'm not so sure...

Can anyone kindly give some ideas of which camera should I go for? Thanks in advance.

Do you really like the EOS M?
If not, you're better with a t3i.
Yes, the port is going slowly, but i don't guarantee anything.

Tbh you seem to lack the "skill" part of the job description. I would be surprised if you'd find some dev to coach you through the process in detail, they're much too busy coding features - and 2nd tbh is that the 70d seems like a more attractive next target than the sl1.

How about buying yourself a good ol' Rebel that is actually supported by ML, and then start coding some nice modules to learn the ropes?

Nanomad alerady helped me and i'm on the process.
As much as i would like to have an stable ML on another camera, i just love the size of the camera and the video AF which works. it's miles better than the t4i one, and helps me a lot when i have other priorities rather than pulling focus.

i'm trying to port the ml to 100D... But i'm lost, one say i should find the bootloader, then other say i should analyse the boot process... And I end up in nowhere stuck looking at lines and lines of code.
Me and e^ipi will be glad if someone explain *with details* what should be done.

ff143424:    e28f00a4    add   r0, pc, #164   ; ff1434d0: (62616e45)  *"EnableBootDisk"
ff143434:    e28f00a8    add   r0, pc, #168   ; ff1434e4: (61736944)  *"DisableBootDisk"
this is the bootflag?

And the HDMI specs simply don't support 14bit RAW Bayer data.

Holy. Shit.
THIS IS INSANELY INCREDIBLE MAN

What you can record with an external recorder over HDMI in the lastest firmware is recording an uncompressed signal, which is different from RAW.
Uncompressed is processed on camera, but it doens't suffer from h.264 compressing artifacts;
RAW is the image as the sensor sees it; no preprocessing, and can only be recorded using CF card on the camera. The bitrate is VERY high and you can only record a few minutes with 32gb+ cards. And you need very fast cards too.
If you want a long recording time, use the built-in h.264 and tweak the profile settings (custom ones) to have the best picture, or use the uncompressed HDMI on the latest firmware to a external recording, but the files will be huge and the quality differences isn't too dramatic (google 5dmkiii uncompressed hdmi vs h264).
If you want an outstanding image, go for RAW, but you need fast, large (and expensive) cards.
1080p24 raw is 83,61 MB/s or 5GB per minute. so you need true 1000x cards that are expensive (lexars and sandisk extreme ones. komputerbay seems to work but they're of duvidous quality.)

I've thinking around a moment... About the EOS 1DC. (Yes i know the ML team will not work on then, but it's only used as a concept here)
Well, it's an 1DX with a different firmware. Same sensor, board, processors, etc, just the firmware and a different heatsink.
But... It has an S-35 1080p crop... it's 1080p, but it's incredible sharp compared to the full frame 1080p and make it look like it has passed an blur filter.
But if the 1DC was never designed to do that and it's added on firmware or as a feature on the Digic 5+ cameras?
You can't shoot a picture while in 4k mode because... it bypass the h.264 and use the bulit-in JPEG encoder for pictures...
The S-35 mode is h.264, but man, it's sharp everywhere i've seen
The encoding engine is different from the Digic 5(non +) and Digic 4 as i've seen on real world tests (far more efficient) and also techincal (uses IPB compression, which is bidirectional and needs far more processing than the IPP on older cameras which only references back frames).
So, chances are the Digic 5+ have some features hidden...
Just something i've thinking on, because maybe a high sharpness crop mode exists on all Digic 5+ cameras, just disabled and we don't know?
What you guys think of this?

http://www.slashcam.de/tools/ml-raw-calc.html
now your life is easier.

Much probably not.
The H.264 enconder is fixed function hardware and probably only supports the resolutions Canon developed the encoder for.

If you want to donate, do this for the entire project, the people who first make this possible.

We're alerady trying to port it, but this thing needs time and patience to do, we're alerady making it as fast as we can without messing around with this, so just wait, and if we can port it, we will.

Request the dumper to a1ex, so your can help me finding the bootflag. I've installed the development system on my machine and learning how the thing works.
Two heads work better than one. I will send you a PM so we can talk.

Hello!

I purchased an SL1 a few months ago and was hoping for an ML port... It appears that there is no active development on this front.

And I don't see myself selling/exchanging this for something else...

I have the requisite skills... perhaps this is an itch I need to scratch.

I just joined the forum... haven't groked for all the relevant info.

Would someone be kind enough to point me in the right direction?

Cheers!

Quote from CHDK wiki (which applies here too):

I have the camera and alerady messed up with ARM processor on nintendo consoles, using arm-gcc. I've alerady read about starting development, trough it's still no clear to me what i should start doing. If someone guides me how to start, i will help as i can.

Oh... The port was cancelled, what a shame... hope on the future some other developer get into it, sometimes i regret buying a 100D just because of the ML functions. They're so useful, especially on video.
P.S since the SL1 is an small T5i, is there any way that the t5i developer could help?

Aqui estou eu, BR HUE, SP.
Olá a todos do forum!

Any advance on this port? I'd love to have magic lantern on my 100D.
If i can help, i have some skills on programming.
Sometimes i regret on dont buying the t3i just becuase of ML