T2i Magic Lantern for 550D in progress!

I rely heavily on watching the audio levels for interviews (currently lost my cable to monitor to headphones), so I've been scared to upgrade since I heard there were issues on the newer builds and the levels not moving on screen.

Is this a serious problem for other people? I saw it get mentioned a couple of times, and then ceased as if the problem went away. But I didn't see a1ex say it was fixed, so... anyone fill me in on this?
 
Audio meters are severely undersampled => not very accurate. They are moving (of course, the signal level should be higher than -40 dB, otherwise you won't see them).

To adjust the curves, use EOS utility to load/edit presets.

CBR and VBR (QScale) are different beasts. One is constant bitrate, the other one is constant quality. Read the manual and look at the bitrate meter in ML.
 
a1ex said:
Audio meters are severely undersampled => not very accurate. They are moving (of course, the signal level should be higher than -40 dB, otherwise you won't see them).
Click to expand...

Are they the same as they always were, or is this a new development? Because I've been using an older build (early Jan I think?) without a problem, gotten used to where they stand, etc. I was under the impression they had changed and didn't work the same way anymore judging by complaints on the forum. I would try it myself, but I haven't had time to test and I'm actually filming someone tonight. So, I guess I could just stick with the build I have since I know it works, and experiment later.
 
They are the same (just a bit smaller so they can display input source besides them). I've compared them to the ones in 0.2.0 build and did not find any difference.
 
ajm1945 said:
I downloaded and installed Magic Lantern, really loved that. Can anyone tell me how to adjust gamma curve, knee point or color matrix? Are those options possible with Canon T2i?
Click to expand...

you'll have to use canon's picture profile editor

it's not a very good app, I wouldn't recommend toying with anything other than the curves

plus, if you shoot flatter than you need and then correct it in post, you end up with more options but also more noise than you would have had if you tried to get it closer to the final look in camera
 
yeah,messing with contrast or gamma in pic style will make dark areas bit brighter and will expose noise in them,you would have ugly moving noisy pixel termites in dark areas.
 
Do all builds install the same or go through the same process? I found this tutorial video on you tube that takes your through the steps of installing magic lantern but the version is from December 20th.

Also another thing I noticed was the some the menu flickers a bit, is this normal?
 
The first time you install ML is different than updating to a newer version.
The first installation is best outlined here:
http://magiclantern.wikia.com/wiki/550d_install

And that will work for any version.

To install a newer version (once you have ML on your camera and your card has been made bootable) just drag and drop the new contents onto your SD card. I think the only one you need to replace is the autoexec.bin

The flickering is normal...it is a hack after all.
 
Sounds easy enough. So far the only files I have on my memory card are, autoexec, LOG000, magic.cfg, magiclantern.fir, and ROM0.... So I would keep all files EXCEPT for autoexec.bin(which will be replaced) correct? And not have to redo the steps for creating a bootable memory card since I've done that already?

Again, I'll being going from the dec. 20th build to the latest feb. 25th build.

Here's an experimental build which attempts to save the config file
automatically at shutdown, so all ML settings should be now
persistent.

Also, the LCD display off setting will be applied until you disable it
manually for ML menu (so if the screen turns back on for whatever
reason, it will be turned back off).

This build is experimental and may have some side effects, so please
use it with caution and report all the bugs.

magiclantern-2011Feb25.550d.fw109.AudioMon.persistent-config.alex.zip
Click to expand...

Thanks for the quick reply, Zech.

And one more noob question, but would I have to reinstall the firmware and take out the battery again?
 
Last edited:
As long as its the same bootble card and the same hacked camera, yes. Just drag the new autoexec file onto the card and say overwrite.


Heres what each of those files are (at least as far as I know, hopefully someone corrects me if I'm wrong):

autoexec: The bootable file which is magic lantern (the firmware mod is not ML but just makes it so your camera boots an SD card) DO NOT PUT YOUR CARD IN THE CAMERA WITHOUT THIS FILE!!!!
LOG000: No idea what this actualy is, I think its a log of errors. I deleted this off of my card ad I've been running just fine for a while.
magic.cfg: This is the saved settings for ML (this is automaticly created/updated every time you hit "Save Config" in the Debug menu) I shoot with 2 cards so i copy this over to the other and all my default settings are on both
magiclantern.fir: This was the firmware mod that you put on your camera when you first installed ML. You don't need this on the card and its also something I deleted a while ago and been fine without.
ROMO: Just an extra file that ML used to create. I also deleted this and have been fine.

When I update I just drag the autoexec onto the card, that way I keep all my default settings and my custom crop marks.
 
Thanks for explaining all that, Zech. I just replaced the autoexec file and everything appears to be running fine. I noticed that this gave me a temperature reading on the lower left hand corner.... What are safe temperatures for the cmos? I'm also noticing the camera feeling a bit warmer than usual...
 
No idea what is "safe" but mine is usually in the 150's.
if your higher than that, Id turn off the camera and take out the battery.
 
Hmm, I wonder how much footage can one fit on a 16GB card with QScale -16? I wonder if 16GB card would be decent enough.

Also, I right now have a class 4 card and I can get max QScale -5, did they implement a feature where you can't set a QScale value higher than your card can handle?
 
What's the proper way of testing for stability? Right now I have my camera set at QScale -12, ISO 320, and Shutter 1/50. I'm recording indoor footage using a Tokina 11-16mm wide angle lens on a Class 6 Transcend 16gb card. There have been ZERO problems for me.
 
Ok, thanks Alex.

Well, I guess I'll just have to see, will order a 16GB class 10 card today and see how much can it handle.

Could you please verify my 2nd question, though?

And if you're the Alex Alex, who I think you are, thanks so so much for the ML! It's great!

EDIT: Never mind, I didn't realize you have to configure the QScale with the Q button. Ok, gonna try and see how much my class 4 can handle.
 
You must log in or register to reply here.
Back
Top