T2i Magic Lantern for 550D in progress!

When I said Sci-Fi, I understood one thing should be displayed and another thing should be recorded. That's not possible (i.e. only AJ can do this in ASM :P )
But that's exactly what happens... you think of it as coding new RAW algos when its only a matter of toggling between two Styles... it may be PERCEIVED as how you depicted it...

Regarding the Sci-Fi:
Don't take the Sci-Fi thingy too seriously, man... I was not talking about coding RAW algorithms :)

Well, the funny thing is that only AFTER I have written that it is "Sci-Fi" did I understand that it's really not :-) it might LOOK like one, but its not...

It's an interesting test... to see how this comes out... previewing with one PictureStyle and recording with another (this is what Shane Hurlbut do, IIRC)

Perfect solution within the constrains we live in...
 
Sandro: try with GlobalDraw off and see if it has any influence. It may be ML using too much CPU power.
 
but the LUT thing I mentioned should be feasible!!

just like you do false color, you can apply an S curve, right?

in any case, changing picture styles is already pretty straightforward: hit Q, change with wheel
you just have to have your preferred settings loaded to the camera on the 3 picture style preset slots

edit: and by the way, yes, that's what I think Shane Hurlbut says he's doing: light with preset 1 (neutral), record with preset 2 or 3 (ultra flat, and calibrated differently for each body, because they're not all the same; I guess it's just CineStyle for all now, as he seemed to like it and there's no way to further tweak that one)
 
False colors are displayed on an 8-bit color overlay, and they are only computed from Luma. Try Magic Circles on 5D2 to see what I mean.

Moreover, ML does not have access to the curves of picture styles.
 
Sandro: try with GlobalDraw off and see if it has any influence. It may be ML using too much CPU power.

I tried but it still happens. It seems like with "FW default" it tries to use higher bitrates and it drops, infact I see that it stops when the bitrate goes to about 70mbit , then after like 3 tries it stops dropping but the bitrate stays at 30Mbit. I don't get if I'm the only one that has this problem, cause this make it unusable for someone who wants reliable thing to at least shoot videos the standard way
 
Try doing some tests like the ones made by Dorian (see http://magiclantern.wikia.com/wiki/Bit_rate ), with "FW default" and without ML. If the results are different, it may be a bug.

Ok so without ML I recorded 1:20 without any problems, avg bitrate 44mbit, peak 46mbit. With ML FW default/cbr 1.0x didn't stop this time but the avg bitrate was 37mbit peak 42mbit. I'm more confused than before.
I also tried cbr 2.0x that before was impossible to achieve without drops.
It still doesn't convince me because yesterday night did the same thing, the drops happened randomly. Could be a CPU issue (ML interface + bitrate data to show)? I can't afford to go out shooting with the risk the camera decides randomly to not work
 
Because if it means "toggling MANUALLY between PictureStyle"...well, it is a l-i-t-t-l-e cumbersome, to say the least...

Its easy, just use the canon menu instead of ML.
Press [Q], arrow down one if its not already on picture style, turn the click wheel till your at your style, press [Q] again. Record away.

I think that is plenty easy, and is better than a toggle button would be, and heres why:
I light, expose, and white balance to what I plan to grade to, whether thats most like neutral, standard, portrait, or I build a custom PP for a unique grade.
 
I'm having issues with ML, tonight I tried to shoot my first videos to use the better ISOs.
I'm using latest version and transcend 16gb class 10 card and i've never had a buffer problem before. I have set the bitrate to FW default that from my understanding should be the canon's standard (i'm fine with it) but for no reason it happens that when I start a recording at random the bitrate goes way high and the recording stops after 3 seconds. Then I think that its must be set a higher bitrate, but the setting it's still "fw default", so I try to change it and put it back to fw default but then I get a recording at about 12mbit. I have to restart ML to make it work. I don't understand why this happens

EDIT: i tried to update to magiclantern-2011May12.550d.fw109.CBR and FW default now seems to use the proper bitrate, i think, but still stops the recording, how can this be usable??

I experienced a similar problem, I'd hit record, with all standard bitrate settings, and the buffer would fill up and stop within the first few seconds, but when I hit record again, it usually worked fine, never happening more than three times in a row. But then my card decided to format itself and seriously screw itself up, so I didn't know if it was ML or my card, and I haven't experienced it with my back up card (which is only a class 4, but never have had a problem with it).
 
Ok so without ML I recorded 1:20 without any problems, avg bitrate 44mbit, peak 46mbit. With ML FW default/cbr 1.0x didn't stop this time but the avg bitrate was 37mbit peak 42mbit.

It was a similar scene? Bitrate still depends on what you are shooting. I think it's good to record some sequence from a movie, which you can replay (i.e. to record the same thing). Or use two cameras if you can (one with ML, one without).

Also try one of the builds before May 12, in FW default mode. Restart the camera after setting FW default in menu, just to be sure.
 
I light, expose, and white balance to what I plan to grade to, whether thats most like neutral, standard, portrait, or I build a custom PP for a unique grade.
I don't know, the more I engage myself in the subject, the more I'm feeling reluctant to use CineStyle. but I'm no pro and I prefer to stay away from too much grading.

a1ex, is it not feasible to simulate menu entries sequence ? or do I miss something far more deep ?...
 
Simulating menu entries... are you talking about scripting capabilities? There's not enough memory to have both LUA and all other ML features at the same time.
 
Hey a1ex- is there a technical reason ML can't rewrite itself to a card?

I'm wondering if there could be an option in the ML menu to replace itself post-format in camera. I know ML exists until the camera is powered off, which why we still get the Magic.cfg after formatting. Would it be as simple as setting the flags on the card (bootable, etc) and creating a dump/write of the ML system in memory after formatting? I know it can't be automatic since ML can't change the Canon system menu, but perhaps an option one can find in the ML menu after formatting the usual way?

I guess things like crop marks, etc, wouldn't exist in memory, but the core system (or whatever still works post formatting) could work, right?

This would greatly improve my current workflow, as I could just reformat the card and keep going instead of needing a laptop available.
 
Simulating menu entries... are you talking about scripting capabilities? There's not enough memory to have both LUA and all other ML features at the same time.
I have no idea how to implement it... can't you do within the current code itself ? (I'm no coder, so I have no idea)

The idea was that when a flag is set the 1 (first time pressing REC) it would initiate sequence of menu operations and upon pressing REC again (flag=0), it would initiate another sequence of menu operations (three for both : 1] set LV = on ---> 2] Set menu = expo ---> 3] set picture style = 1/2/3).... and there you have it : one mode for recording and another for previewing and better assessing color/sharpness/white balance. the thing is : we are forced to do it anyway (if we are to use CineStyle and want to assess color/sharpness/white balance) - so why not automate it ? (IF it is feasible). I think Shane Hurlbut might be forever grateful :)

Mind you, this is just a layman view of things. if I'm just hallucinating, by all means... tell me.
 
Last edited:
For restoring ML after reformatting, I'd have to:

1) Make the card bootable. This means doing the job of EOScard and MacBoot. Code exists for 5D2, but it didn't work on 550D. ExFAT is more difficult.
2) Find some free memory. Maybe some image buffer (which is only used when taking pictures). After this, copying ML files to RAM and back should not be difficult.

Intercepting the formatting option from Canon menu shouldn't be a problem; usually it's not difficult to see what dialog is currently active. ML could copy itself to RAM when you open the Format dialog, and then copy itself back to card after you close this dialog, if autoexec.bin is no longer there.

So the biggest issue right now is how to make the card bootable (this requires low-level card IO and it's a bit beyond my current knowledge).
 
Last edited:
It was a similar scene? Bitrate still depends on what you are shooting. I think it's good to record some sequence from a movie, which you can replay (i.e. to record the same thing). Or use two cameras if you can (one with ML, one without).

Also try one of the builds before May 12, in FW default mode. Restart the camera after setting FW default in menu, just to be sure.

It was the same scene and steady, I'll try that and report back
 
I experienced a similar problem, I'd hit record, with all standard bitrate settings, and the buffer would fill up and stop within the first few seconds, but when I hit record again, it usually worked fine, never happening more than three times in a row. But then my card decided to format itself and seriously screw itself up, so I didn't know if it was ML or my card, and I haven't experienced it with my back up card (which is only a class 4, but never have had a problem with it).

the problem is that sometimes it would not stop doing that game until i changed the settings many times and tried again
 
Back
Top