T2i Magic Lantern for 550D in progress!

LiveView presets right now don't store the configuration of various items; they store just the ON/OFF state. I'm not yet sure how to implement it without complicating things too much, but it may be possible sometimes.

I'm not sure if anyone noticed, but latest build should fix some problems with high-impedance microphones, where input level is very low with ML, but OK with AGC. I didn't get any feedback from users with such microphones, and I'd like to know if the new setting (microphone power) has any effect or not.
 
What is the difference between AJ's CBR implementation and the old 550d one ?

Are there any practical (and tangible) quality differences between, say, video that was shot with 25-5 version and the current one ?
 
Hi a1ex,

Thanks for the June 7 Magic Lantern update for the T2i.

I did notice one issue. When paging through the picture styles in the Magic Lantern menu, the "Faithful" picture style is represented in text as "Fai", although the picture style itself changes correctly. This was on the second build you released today with the same date ("[FONT=Courier, Monospaced]A bit strange; simply recompiling seems to have fixed this...[/FONT][FONT=Courier, Monospaced]Maybe it's time to upgrade my compiler?[/FONT]").

I also had another question about the Magic Lantern shutter speeds. The conventional wisdom when shooting around older florescent fixtures is to shoot with a shutter speed of 1/60 to avoid flicker (at least in North America), on the theory that the shutter speed will match the AC power frequency. I suppose the same would be true for 1/50 in countries with 50Hz power.

A few builds back you changed the shutter speeds to work with a different multiplier, allowing the use of a 1/48 shutter speed. Personally I prefer the 1/48 shutter speed to 1/50, but I'm concerned that if I'm ever stuck shooting around old florescent lights I might have to bypass Magic Lantern for those shots. I don't suppose there's any way to have the best of both worlds, where we get 1/48 and 1/60 shutter speeds in the same build? From what I could tell, you used a single frequency multiplier from which all of the shutter speeds were derived.

Thanks again for your excellent work!
 
Sorry if this is already asked somewhere before. But which is the most "solid" ML version for the 550d at the moment?I tried the 0.2.0 Version on the 550d from december and the last from 31th of may. Both are too buggy to use it seriously.

Cheers
Thomas.
 
Last edited:
AD Tom said:
Sorry if this is already asked somewhere before. But which is the most "solid" ML version for the 550d at the moment?I tried the 0.2.0 Version on the 550d from december and the last from 31th of may. Both are too buggy to use it seriously.

Cheers
Thomas.
Click to expand...
I was using the build before the last one (with the new icons) for some days of shooting and it was stable.


The shutter speed thing: I was trying to film some projections from little lcd projectors and it was not possible to get rid of the flickering. At least there were some stripes which moved very slowly. Finally I tried it with a Sony Z5 camcorder and 1/50 shutter speed and it works just fine.
So it seem that the DSLRs really use 1/48 shutter.

Best regards,
Dorian
 
Shutter speeds are exactly the same in all ML builds (only the displayed values have 2 digits instad of 1). My theory says those are the exact values used by the firmware; you can find it in the PDF. If you disagree, feel free to prove the contrary.

AD Tom: did you notice any problems with Jun 7 build? It's still young, but a few unused features were removed, and this should make it more stable in theory.
 
a1ex said:
Shutter speeds are exactly the same in all ML builds (only the displayed values have 2 digits instad of 1). My theory says those are the exact values used by the firmware; you can find it in the PDF. If you disagree, feel free to prove the contrary.

AD Tom: did you notice any problems with Jun 7 build? It's still young, but a few unused features were removed, and this should make it more stable in theory.
Click to expand...

Thanks - do you mean this one http://bit.ly/jEy4D2

Cheers
Thomas.
 
Last edited:
Yes. There are actually 3 different builds recompiled from the same source; I believe the latest one to be the best, but I didn't really test it (I've upgraded the compiler).

Of course, before using any build for serious jobs, you should test it thoroughly and get familiar with it.
 
a1ex said:
Shutter speeds are exactly the same in all ML builds (only the displayed values have 2 digits instad of 1). My theory says those are the exact values used by the firmware; you can find it in the PDF. If you disagree, feel free to prove the contrary.
Click to expand...
Hi Alex, I did not want to disagree because what I experienced supports your calculations of the shutter speeds. So the standard firmware 1/50 is not a real 1/50.
 
What I believe is that there is some kind of software correction for flicker inside the firmware. Some interesting strings: "EP_SetFlickerMode >> 50Hz Mode" and "EP_SetFlickerMode >> 60Hz Mode". I don't understand yet how this is working, but I did notice different flicker behavior in movie and photo mode (with the same shutter speed).
 
What is the status of ML functionality when using the composite out to an SD monitor?

I haven't checked for a while. I wonder if Alex ever got his SmallHD monitor? I heard a rumour some progress had been made on HDMI out, but I haven't seen anything official bout that either.
 
alex, i must admit i liked it better when i could scroll through the pic styles and see them update on the screen. also, i don't think this version keeps the saturation and contrast settings from the user pic styles. pic style surely doesn't work as well in this version.
 
a1ex said:
I didn't get any monitor yet (no news since then). However, I have an experiment which may fix many HDMI things, but no one had the courage to try it yet :)
http://groups.google.com/group/ml-devel/browse_thread/thread/34a9efe0ec1b848e
Click to expand...

I saw that recent post, which is what prompted me to ask about SD over composite. I don't have an HDMI field monitor either.

I take it your fix attempts to send 720x480 to the HDMI output? I could test this on my PC monitor at home, but I'm not sure it would help, as my monitor only negotiates a 480p signal with the camera anyway, and the ML overlays are not right even then. Maybe I have it all wrong.

I wish I knew why my PC monitor won't show 1080p from the camera. It's a 1080p panel, and I'm not trying to view the output while recording. I've used a cable that carries 1080p from a different device. Anyone?

It's a shame those guys just went silent about the monitor. If I remember correctly, before the pledge to send you one, there was a motion on the ML dev list to organise a collection to buy one for you, which had good support.

I think we should get this idea going again. I will contribute, especially if it leads towards a fix for using composite out.
 
a1ex said:
What I believe is that there is some kind of software correction for flicker inside the firmware. Some interesting strings: "EP_SetFlickerMode >> 50Hz Mode" and "EP_SetFlickerMode >> 60Hz Mode". I don't understand yet how this is working, but I did notice different flicker behavior in movie and photo mode (with the same shutter speed).
Click to expand...

Interesting. So you're saying that the Magic Lantern shutter speeds were the real shutter speeds all along, you're just displaying them more accurately. And that Canon has a special software method to reduce flicker from power sources.

Very interesting. Thanks for the clarification, it's very helpful.
 
That's my hypothesis; I believe a blur test will show which are the real shutter speeds used.

First HDMI test worked, anyone wants to help with the second test? http://bit.ly/m3k3Z5
 
Last edited:
So you actually got 1080i during recording? Nice :)

Of course, I don't have any idea on how to remove those artifacts (clear the screen, as a workaround)

Edit: I've noticed now that it's repeating the last few frames...
 
Last edited:
You must log in or register to reply here.
Back
Top