T2i Magic Lantern for 550D in progress!

manual exposure, previous releases have worked great. not sure what the issues is with aug 17.

just saw the post of the aug 22 build and will try that later today.

a1ex said:
Are you on auto exposure? If yes, movie logging might be updated a bit too often and overflow the buffer.
Click to expand...
 
I've tried to push the bitrate on my Transcend class10 card and got CBR 1.4 stable. With July 8 I could only achieve 1.3.

Also, Scrax (the 600D tester) was able to push it to 1.8 or 1.9 without sound.
 
You mention in the manual that we have to extract the WHOLE zip unto our cards. but the zip contains also .FIT and the PDF manual. surely one does not need that, right ? :-)

And the custom (Cine) cropmarks will be overwritten also....

What are the ABSOLUTE needed files in this release (in addition to the autoexec) ?

Thanks for bringing back the .diff file :thumbsup:
 
Removing files is for advanced users (they already know that PDFs are not needed). Also, if you use custom cropmarks, you already know what do do with them. Extra files will only take a bit of extra space (the entire ML archive, uncompressed, takes less than 10 MB... and a Raw file has around 30).

If you don't use certain features, you may delete some files. For example, if you never use Live Defish, you may delete rectilin.lut. Or if you never go into ML menu, you may delete the fonts file :)
 
I'm back again :cheesy:

the july build worked great on the t2i and t3i.

over the weekend on vacation i had trouble with the aug 17 build on the t3i. did not have the t2i with me.

the t3i would indicate a buffer error and stop recording, camera would lock and battery needed removed to reset.

got back today from vacation on the aug 17 build on the same card worked great on the t2i, no problems with buffering.

aug 17 still did not work on the t3i.

loaded the aug 22 build and all appeared ok on the t3i. then the error returned and the camera locked.

it seems ( i think ) the problem with the t3i only occurs after activating the 3x mode. even after exiting 3x the buffer error returns. if i pull the battery, reset and do not use the 3x mode it seems to work fine.

does this make sense that the 3x mode is causing the buffer problem?
 
It's possible. Disable features until you can isolate the problem, and let me know.

Edit: do you use any big cropmarks (non-RLE) ? These are known to cause memory errors on 60D, so might be related.

You can turn off GlobalDraw to pause almost all CPU-hungry ML tasks from ML.
 
Last edited:
a1ex said:
New release: bit.ly/​ml-aug22
Click to expand...
Thanks for that new version, but the cropmarks are horrible! (kidding!!)

USE THE FOLLOWING ONLY IF YOU ALREADY HAVE INSTALLED ML BEFORE ON YOUR CAMERA:
I've uploaded a version of mine, pre-installed pack with custom cropmarks that I find usefull. All that you need is only to copy/paste on the card and it also includes EOScard.exe to make it bootable. All in a .zip file.
Only thing that's not included is the Doc folder and the userguide.pdf to save some space (356kb instead of 10MB).

Hope you guys will like it.
 
Nice. BTW, EOSCard functionality is now available in ML (just run Firmware Upgrade from an unbootable card).
 
A1ex: Is it possible to raise the Qscale up to, lets say, -30 (still keep that option hidden) and let the CBR climb that Qscale when there is a non-complex scene?
 
Not yet (I can change the limits, but not in a controllable way... i.e. I can't set what value I want). It goes to high values for a few seconds, then ends with ERR70.
 
I set CBR paramters and pass them to Canon's algorithm. But Canon's algorithm does not allow QScale to go outside [-16...+16].

[strike]If you configure QScale via config file (it's still available as a hidden setting), you should be able to enter any value.[/strike]

Edit: didn't work.
 
Last edited:
a1ex said:
Nice. BTW, EOSCard functionality is now available in ML (just run Firmware Upgrade from an unbootable card).
Click to expand...
Just read the Install.pdf and it looks like a "first-time-installation-process" everytime you re-install ML on a card to make it bootable, right? Wouldn't it be simpler to copy/paste the files from the computer to the card (freshly formated) and use EOScard.exe apart? I mean you can do it within 20 seconds directly from the computer, then put the card in the camera, provided you already installed ML at least once before.
Anyway thanks for the update. Looks stable and works like a charm!
-Mark-
 
noise reduction in movie mode

noise reduction in movie mode

hi all,

I would like to know if noise reduction is enabled by default in movie mode or is there any way to adjust it either in the original firmware or with this nice little "hack" :)

Thanks.
 
Of course you can do. But I wanted to avoid the issues with many users saying EosCard/MacBoot doesn't work / is hard to use / etc.
 
with this release, zebras are "frozen" in space whenever I dial in CBR of 1.4 (1.3 is OK)

Repro :
Set CBR to 1.4 (card dependent - with my SanDisk 16Mb x30 its 1.4), point the camera to a dark space, yielding an under exposed image. pan the camera. result : the last zebra overlay is "stuck" in place until you press something (can't remember what. might have been the shutter)
 
a1ex said:
Go to the help page of BuffWarnLevel ;)
Click to expand...
Hehe...

Please do understand that I did not request the .diff file for no reason... I literally read ALL the things that have changed (+ the NFO you post at Magic Lantern firmware development on Google Groups) .

Now, I AM familiar with the buffer overflow and it's consequences (been through some of them before), but never have I seen this type of behavior. oh well, you learn a new thing each and every day...

I am really glad you have implemented the "REC mode" (previously known as "sci-fi feature" :D). I hope I had something to do with getting you going at it... :smile:

Take care man. me off to shoot...
 
:) zebra freezing was in the previous release too (but maybe you didn't push the bitrate so far, or you had it off).
 
You must log in or register to reply here.
Back
Top