T2i Magic Lantern for 550D in progress!

yep!
just to be sure, do i need the *.fir file when i update ML ? or this is only for the first install ?

after reading the install process, i think i've got my answer, it's not needed...
 
Last edited:
alfa: The .fir is needed only once per camera. It patches the camera so it will try to boot from SD card every time it’s (the card) bootable.
 
thanks to confirm, i deleted them as my camera is already patched since april 2011.

Yes, it could be a reason.

Can you try with aug17 without reformatting? Just for testing.
Click to expand...
no more buffer bar for now...it's "green" !! ;)
i've just done a quick little test, but it seems to be fine now, many thanks !

i like the colored infos, pretty cool !
 
Hi, A1ex

I've been shooting today at different CBR scalars (to show difference in quantization noise) until I realized that it stopped working for me! I mean if I shoot in "FW default" it gives me 41.7 Mb/s for video and in "CBR, 3.0X" it increases only to 44.7! How is it possible?

Thanks,
Mark.
 
When it hits QScale -16, it won't increase bitrate further. The bitrate meter should turn red when this happens.
 
i loaded the aug 17 build on two transcend 32gb class 10 cards. never had any issues with previous builds of ml on these cards.

the aug 17 build does not play nice with my t3i. it will show the overheating icon and stop the recording. more than once it locked the camera and the battery was removed to reset.

went back to the july 8 build. it would occasionally lock the camera but never overheated.

i believe all menu settings are the same between the aug 17 and july 8 build. we are on a family vacation and i did not bring along the t2i so the only camera i have to test with is the t3i.

any idea on what might be the issue with the temperature?

thanks
 
zobtron said:
i loaded the aug 17 build on two transcend 32gb class 10 cards. never had any issues with previous builds of ml on these cards.

the aug 17 build does not play nice with my t3i.
Click to expand...
1) Did the same, no problem so far. Everything's playing nice and smooth.
2) I used both and I kept the lastest build because of some minor changes. I've been using it quite intensively for 2 days and never had any issues so far.
 
drapeama said:
1) Did the same, no problem so far. Everything's playing nice and smooth.
2) I used both and I kept the lastest build because of some minor changes. I've been using it quite intensively for 2 days and never had any issues so far.
Click to expand...

that is the odd thing as i never had a problem with any previous builds. there are some really great additions to the aug 17 beta and i checked other sites and forums before posting here. i did not find any cause or solutions posted. will revert to the july build until vacation ends next week and i have more time.
 
I'm able to crash the July 8 build easily by pressing a lot of buttons very quickly (e.g. pressing the LiveView button 20 times on 550D, or changing disp presets very quickly on 60D, or pressing flash in movie mode at the same time with half-shutter). I can't crash the aug17 build yet.

But since I don't have a 600D/t3i to test it myself, I may miss some subtle issues. Each camera has its own little quirks.
 
a1ex said:
I'm able to crash the July 8 build easily by pressing a lot of buttons very quickly [...] I can't crash the aug17 build yet.
Click to expand...
Good news, as I never been able to crash the July 8 build. Or maybe 1 time, changing from M to Movie very quickly but I think it's the only time it happened.
 
changing from M to Movie very quickly
Click to expand...
Good point. I just enabled movie mode remap to A-dep (so movie mode is now at both ends), enabled false color, cropmarks, histogram and waveform (to stress the CPU a bit), and then turned the mode dial back and forth for a few minutes. No crash :)

Maybe I should write a series of tests to be run on the camera before a release.
 
Hi A1ex,

I've shot the clips for the comparison of smooth plates (160 ISO, standard profile).
It seems that qscale -16 means constant quantizer of 10.
It takes 9 frames to reach this quantizer (it begins with quantizer 18 and from the 3rd frame, each frame is decreased by 1.
Here are the crops (160 X 160, lossless x264, starting from frame 10):

Deafult - the quantizer is 16 - http://rghost.net/18865541
Qscale -16 - the quantizer is 10 - http://rghost.net/18866231

The -16 footage seems to be more "grainy-stable" compared to the "boiling-banding" X1.


Regards,
Mark.
 
Interesting... how did you see the quantizer? Does bitrate viewer display it?

For some reason I can't play the videos (only see the first frame). Can you post some still frames?
 
Vega H264 analyzer. It also shows the motion vector chaos because Canon's Dslr encoder does poor motion prediction.

Try VLC media player - seems to handle these files well. Still frame won't demonstrate the effect since it refers to the residual between frames.
 
Yes, there seems to be some finer detail in the QScale -16 shot, but there's still room for improvement.

BTW, I've removed CBR 3x in latest version, since current cards can only record up to 1.4x. I also know it's possible to remove the -16 limit (I pushed it to -70), but right now I don't have a reliable way of changing it.
 
Finer detail is good, but you will lose it when you'll try to get rid of the boiling.
In the following days I'll test the relationship between "CBR" and QP, and "QSCALE" and QP - to be more confident with what I'm writing.
But for now:
If Qscale and CBR have equal QP to the whole frame, pushing the Qscale won't give real results because of card limitation.
There should be a smarter prediction that will decide which macro block gets lower QP and which higher - so there will be macro blocks with QP=20 and others with QP=4 (for example).
This case it would give very interesting results.
Now we are limited with QP=10 (I guess Qscale -70 = QP0 = lossless).
 
update: i turned off movie logging and this seems to have helped, will continue testing.


quick follow up on my previous post with the aug 17 build. it is not the temperature icon displayed and the recording stopped as previously indicated. the icon displayed is the recording buffer.

the 1.0x fw default is selected in the ml menu and i have no issues with this in the july build. with the aug 17 build the recording stops and the camera will lock and needs the battery removed to reset the t3i.

any ideas why this happens with the aug 17 build? i did low level format the cards in camera before installing ml aug 17 build. these are transcend 32gb class 10 cards.

thanks and sorry for any confusion with the misreading of the temp and buffer icons.
 
Last edited:
Are you on auto exposure? If yes, movie logging might be updated a bit too often and overflow the buffer.
 
You must log in or register to reply here.
Back
Top