New features:
* GUI menus (of course): press the ERASE button to display them.
* Zebra also for underexposed areas
* Simple intervalometer
* Wireless shutter trigger using the LCD sensor and your own hand
(i.e. put your hand near the LCD to take a pic)
* AE bracketing (like on 5D2 ML)
* Stack focus works (you have to go to Live View, then Play, then back
to LiveView, then start it from menu)
* Debug features, like GUI and property logging => you can help the
development without writing a single line of code!
* Piers' audio options accessible from menu
* No more need for disabling powersave (but you can, if you like)
Known bugs:
* Sometimes the menu gets overwritten by Canon's drawing routines.
* After closing ML menu, screen may not redraw automatically (half-
press the shutter to trigger a redraw)
* Playing with debug options may lead to strange behaviors of the
camera (if it happens, restart it).
* I did not try the Boot menu entries => be careful with them!
> New features: > * GUI menus (of course): press the ERASE button to display them. > * Zebra also for underexposed areas > * Simple intervalometer > * Wireless shutter trigger using the LCD sensor and your own hand > (i.e. put your hand near the LCD to take a pic) > * AE bracketing (like on 5D2 ML) > * Stack focus works (you have to go to Live View, then Play, then back > to LiveView, then start it from menu) > * Debug features, like GUI and property logging => you can help the > development without writing a single line of code! > * Piers' audio options accessible from menu > * No more need for disabling powersave (but you can, if you like)
> Known bugs: > * Sometimes the menu gets overwritten by Canon's drawing routines. > * After closing ML menu, screen may not redraw automatically (half- > press the shutter to trigger a redraw) > * Playing with debug options may lead to strange behaviors of the > camera (if it happens, restart it). > * I did not try the Boot menu entries => be careful with them!
<barbosa_f...@hotmail.com> wrote: > hi alex...inside the Zip file there is no congif file...should we use > the old ones or it's not necessary anymore?
> To post to this group, send email to ml-devel@googlegroups.com > To unsubscribe from this group, send email to ml-devel+unsubscribe@googlegroups.com > For more options, visit this group at http://groups.google.com/group/ml-devel?hl=en
The fir file is the same as in the RC1 release. I believe it's necessary (I don't know whether it's need only for first time install or not... I didn't try to start ML without it).
> To post to this group, send email to ml-devel@googlegroups.com > To unsubscribe from this group, send email to ml-devel+unsubscribe@googlegroups.com > For more options, visit this group at http://groups.google.com/group/ml-devel?hl=en
> New features:
> * GUI menus (of course): press the ERASE button to display them.
> * Zebra also for underexposed areas
> * Simple intervalometer
> * Wireless shutter trigger using the LCD sensor and your own hand
> (i.e. put your hand near the LCD to take a pic)
> * AE bracketing (like on 5D2 ML)
> * Stack focus works (you have to go to Live View, then Play, then back
> to LiveView, then start it from menu)
> * Debug features, like GUI and property logging => you can help the
> development without writing a single line of code!
> * Piers' audio options accessible from menu
> * No more need for disabling powersave (but you can, if you like)
> Known bugs:
> * Sometimes the menu gets overwritten by Canon's drawing routines.
> * After closing ML menu, screen may not redraw automatically (half-
> press the shutter to trigger a redraw)
> * Playing with debug options may lead to strange behaviors of the
> camera (if it happens, restart it).
> * I did not try the Boot menu entries => be careful with them!
> If the camera goes to sleep with power save, you can't turn it back on > without removing the battery. For now I just turned power-save off.
My camera turns on by half-pressing the shutter... and reloads Magic Lantern. It may depend in which mode it was before going to sleep. I've tested in AV mode, with and without LiveView, and it worked.
>> New features: >> * GUI menus (of course): press the ERASE button to display them. >> * Zebra also for underexposed areas >> * Simple intervalometer >> * Wireless shutter trigger using the LCD sensor and your own hand >> (i.e. put your hand near the LCD to take a pic) >> * AE bracketing (like on 5D2 ML) >> * Stack focus works (you have to go to Live View, then Play, then back >> to LiveView, then start it from menu) >> * Debug features, like GUI and property logging => you can help the >> development without writing a single line of code! >> * Piers' audio options accessible from menu >> * No more need for disabling powersave (but you can, if you like)
>> Known bugs: >> * Sometimes the menu gets overwritten by Canon's drawing routines. >> * After closing ML menu, screen may not redraw automatically (half- >> press the shutter to trigger a redraw) >> * Playing with debug options may lead to strange behaviors of the >> camera (if it happens, restart it). >> * I did not try the Boot menu entries => be careful with them!
> To post to this group, send email to ml-devel@googlegroups.com > To unsubscribe from this group, send email to ml-devel+unsubscribe@googlegroups.com > For more options, visit this group at http://groups.google.com/group/ml-devel?hl=en
AWESOME WORK Alex! (and I'm VERY happy to see the intervalometer feature! =) )
I've not installed ML yet on any camera, as I'm waiting for... well I guess a more "final" and mature release since I use both of my T2i's in a production environment. But I'm reading these boards and happy to contribute with ideas (like the intervalometer).
What a shame Canon cant release a SDK to actually ENCOURAGE users to develop their own features and extensions to push the boundaries of their cameras. Not open source... but perhaps open API? I mean if you're Canon, why NOT take advantage of "free" labor from the user community of your product to make it that much better? I understand them not wanting to release source code, but will never understand whats to lose for them NOT encouraging the user base to develop the features that THEY the users want to see!
(are you listening Canon??? Probably not *sigh*)
To everyone in the ML development community - keep up the great work! Your efforts are greatly appreciated!
> New features: > * GUI menus (of course): press the ERASE button to display them. > * Zebra also for underexposed areas > * Simple intervalometer > * Wireless shutter trigger using the LCD sensor and your own hand > (i.e. put your hand near the LCD to take a pic) > * AE bracketing (like on 5D2 ML) > * Stack focus works (you have to go to Live View, then Play, then back > to LiveView, then start it from menu) > * Debug features, like GUI and property logging => you can help the > development without writing a single line of code! > * Piers' audio options accessible from menu > * No more need for disabling powersave (but you can, if you like)
> Known bugs: > * Sometimes the menu gets overwritten by Canon's drawing routines. > * After closing ML menu, screen may not redraw automatically (half- > press the shutter to trigger a redraw) > * Playing with debug options may lead to strange behaviors of the > camera (if it happens, restart it). > * I did not try the Boot menu entries => be careful with them!
> To post to this group, send email to ml-devel@googlegroups.com > To unsubscribe from this group, send email to > ml-devel+unsubscribe@googlegroups.com<ml-devel%2Bunsubscribe@googlegroups.c om> > For more options, visit this group at > http://groups.google.com/group/ml-devel?hl=en
> AWESOME WORK Alex! (and I'm VERY happy to see the intervalometer feature!
> =) )
> I've not installed ML yet on any camera, as I'm waiting for... well I guess
> a more "final" and mature release since I use both of my T2i's in a
> production environment. But I'm reading these boards and happy to
> contribute with ideas (like the intervalometer).
> What a shame Canon cant release a SDK to actually ENCOURAGE users to develop
> their own features and extensions to push the boundaries of their cameras.
> Not open source... but perhaps open API? I mean if you're Canon, why NOT
> take advantage of "free" labor from the user community of your product to
> make it that much better? I understand them not wanting to release source
> code, but will never understand whats to lose for them NOT encouraging the
> user base to develop the features that THEY the users want to see!
> (are you listening Canon??? Probably not *sigh*)
> To everyone in the ML development community - keep up the great work! Your
> efforts are greatly appreciated!
> On Sat, Dec 11, 2010 at 1:28 PM, Alex <broscutama...@gmail.com> wrote:
> > Here's the new release for 550D/1.0.8:
> > New features:
> > * GUI menus (of course): press the ERASE button to display them.
> > * Zebra also for underexposed areas
> > * Simple intervalometer
> > * Wireless shutter trigger using the LCD sensor and your own hand
> > (i.e. put your hand near the LCD to take a pic)
> > * AE bracketing (like on 5D2 ML)
> > * Stack focus works (you have to go to Live View, then Play, then back
> > to LiveView, then start it from menu)
> > * Debug features, like GUI and property logging => you can help the
> > development without writing a single line of code!
> > * Piers' audio options accessible from menu
> > * No more need for disabling powersave (but you can, if you like)
> > Known bugs:
> > * Sometimes the menu gets overwritten by Canon's drawing routines.
> > * After closing ML menu, screen may not redraw automatically (half-
> > press the shutter to trigger a redraw)
> > * Playing with debug options may lead to strange behaviors of the
> > camera (if it happens, restart it).
> > * I did not try the Boot menu entries => be careful with them!
> > To post to this group, send email to ml-devel@googlegroups.com
> > To unsubscribe from this group, send email to
> > ml-devel+unsubscribe@googlegroups.com<ml-devel%2Bunsubscribe@googlegroups.c om>
> > For more options, visit this group at
> >http://groups.google.com/group/ml-devel?hl=en
does anybody owns the original fw1.0.8? i found one on the internet
but i'm not sure it's the right FW... i think i'm gone disable the
DISKBOOT flag and downgrade from 1.0.9 to 1.0.8...does anybody tried
this way?
Now you can do speed/quality tests like on 5D2. You can also record 30
minutes of FullHD in 4 GB at lower quality, or even use slower SD
cards (less than class 6)!
> does anybody owns the original fw1.0.8? i found one on the internet
> but i'm not sure it's the right FW... i think i'm gone disable the
> DISKBOOT flag and downgrade from 1.0.9 to 1.0.8...does anybody tried
> this way?
Most features are already there, waiting to be enabled. They were not
active because the video RAM address was not known, and the GUI
handling code was a bit different from the 5D2. Once those were found,
the extra features were relatively easy to enable.
The new ones are the intervalometer and the remote trigger with LCD
sensor :)
Behind the scenes, there was a lot of work for understanding how the
camera works, to develop analysis scripts (the firmware is huge)...
Also, many thanks to AJ and Arm.Indy; I've used lots of bits from
their findings.
On Dec 12, 2:32 pm, Alex <broscutama...@gmail.com> wrote:
i downgrade to 1.0.8 and run your last fw...everything works ok :D
i disable bootdisk flag in config file of your 1.0.9 fw and them i've
done the downgrade...finally i run your last 1.0.8 fw and
now...everything still ok
On Sun, Dec 12, 2010 at 3:54 PM, Pedro Barbosa <barbosa_f...@hotmail.com> wrote: > good news
> i downgrade to 1.0.8 and run your last fw...everything works ok :D
> i disable bootdisk flag in config file of your 1.0.9 fw and them i've > done the downgrade...finally i run your last 1.0.8 fw and > now...everything still ok
> To post to this group, send email to ml-devel@googlegroups.com > To unsubscribe from this group, send email to ml-devel+unsubscribe@googlegroups.com > For more options, visit this group at http://groups.google.com/group/ml-devel?hl=en
i'm playing with the qscale and even at -16 the camera never stops...i
made 15sec clips with +8,-8,-16 and the buffer bar never show...my
cards are all silicone power class 6
> i'm playing with the qscale and even at -16 the camera never stops...i
> made 15sec clips with +8,-8,-16 and the buffer bar never show...my
> cards are all silicone power class 6
i didn't try other framerates..i only tested 24p but as soon as i can
i'll test with other...both 720p and 1080p and maybe 480p just to try
figure the diference between diferent qscale
> i downgrade to 1.0.8 and run your last fw...everything works ok :D
> i disable bootdisk flag in config file of your 1.0.9 fw and them i've
> done the downgrade...finally i run your last 1.0.8 fw and
> now...everything still ok
With Arm.Indy's help, I'm upgrading to Magic Lantern 1.0.9 and porting
the new features there. Therefore, downgrade will not be necessary any
more (if everything goes well).
On Dec 12, 6:30 pm, "arm.indy" <arm.indi...@gmail.com> wrote:
> So there might be a check added by Canon to prevent downgrade if
> bootflag is enabled...
> Indy
> On 12 déc, 14:54, Pedro Barbosa <barbosa_f...@hotmail.com> wrote:
> > good news
> > i downgrade to 1.0.8 and run your last fw...everything works ok :D
> > i disable bootdisk flag in config file of your 1.0.9 fw and them i've
> > done the downgrade...finally i run your last 1.0.8 fw and
> > now...everything still ok
> With Arm.Indy's help, I'm upgrading to Magic Lantern 1.0.9 and porting
> the new features there. Therefore, downgrade will not be necessary any
> more (if everything goes well).
> On Dec 12, 6:30 pm, "arm.indy" <arm.indi...@gmail.com> wrote:
> > So there might be a check added by Canon to prevent downgrade if
> > bootflag is enabled...
> > Indy
> > On 12 déc, 14:54, Pedro Barbosa <barbosa_f...@hotmail.com> wrote:
> > > good news
> > > i downgrade to 1.0.8 and run your last fw...everything works ok :D
> > > i disable bootdisk flag in config file of your 1.0.9 fw and them i've
> > > done the downgrade...finally i run your last 1.0.8 fw and
> > > now...everything still ok
Frikkin' awexome. This camera now beats practically anything else I've
ever used. The only thing I was missing was on-the-fly gain control,
and now that's solved.
I'd say "keep up the good work," but it would appear that just about
all the good work has already been kept up. :D
On Dec 11, 3:28 pm, Alex <broscutama...@gmail.com> wrote:
> New features:
> * GUI menus (of course): press the ERASE button to display them.
> * Zebra also for underexposed areas
> * Simple intervalometer
> * Wireless shutter trigger using the LCD sensor and your own hand
> (i.e. put your hand near the LCD to take a pic)
> * AE bracketing (like on 5D2 ML)
> * Stack focus works (you have to go to Live View, then Play, then back
> to LiveView, then start it from menu)
> * Debug features, like GUI and property logging => you can help the
> development without writing a single line of code!
> * Piers' audio options accessible from menu
> * No more need for disabling powersave (but you can, if you like)
> Known bugs:
> * Sometimes the menu gets overwritten by Canon's drawing routines.
> * After closing ML menu, screen may not redraw automatically (half-
> press the shutter to trigger a redraw)
> * Playing with debug options may lead to strange behaviors of the
> camera (if it happens, restart it).
> * I did not try the Boot menu entries => be careful with them!
