Thanks to Arm.Indy for the new build process!
Meanwhile, there were a few code changes:
* User manual at your fingertips (I'll let you discover how to enable
this; thanks to Sztupy for making this possible with the RLE bitmap
engine)
* Config file load/save is now almost instant, which results in:
- Fast startup => boot logo is no longer needed
- Config file saved every time you close the menu => settings are
saved even if ML crashes
* Fixed crash in photo mode when ClearScreen was active (this needs
more testing; ClearScreen is now off by default due to this bug)
* Full-screen waveform (although with low-res to reduce memory usage)
* Some new power saving options in Debug menu
* Ghost image is back in the menu
* When AGC is on, ML displays current digital gain in the menu. Also
I've noticed AGC is only applied on digital domain => updated the
docs.
* HDMI option for forcing VGA resolution => this avoids the few
seconds of black screen when you start recording. Moreover, this mode
has the same resolution as built-in LCD, so most ML graphics tools
should work with the same code. In high-resolution mode you won't be
able to use most LiveView functions for a while (they didn't work well
anyway).
Thanks to SmallHD, Trammell Hudson and James Donnelly, I'll receive a
HDMI monitor soon and I'll be able to fix these issues.
I've also started a wiki page at http://magiclantern.wikia.com/wiki/Unified
600D port is still young; the audio module is disabled for now. You
can see what works and what not on its wiki page.
When installing, make sure you copy all the subfolders from the zip
archive on the card. The simplest way to upgrade is to unzip
everything.
https://bitbucket.org/hudson/magic-lantern/downloads/magiclantern-2011Jul08.550D.fw109.alex.zip
https://bitbucket.org/hudson/magic-lantern/downloads/magiclantern-2011Jul08.60D.fw109.alex.zip
https://bitbucket.org/hudson/magic-lantern/downloads/magiclantern-2011Jul08.600D.fw101.alex.zip
Enjoy!
--
http://magiclantern.wikia.com/
To post to this group, send email to ml-d...@googlegroups.com
To unsubscribe from this group, send email to ml-devel+u...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/ml-devel?hl=en
Try changing this line in magic.cfg:
Semitransparent gray:
waveform_bg = 20
Semitransparent black:
waveform_bg = 3
Transparent:
waveform_bg = 0
This is done from Custom Functions: on 550D, Shutter/AE lock button
should be AE lock/AF.
SztupY
What does "don't click me" do?
On Wed, Jul 13, 2011 at 9:47 AM, AlexV <al...@vafiopoulos.de> wrote:
> I am missing the lower row of info (ISO, shutter etc) on my 60D.
>
>
> Enjoy!
In photo mode, flash is blocked by placing something on the hot shoe
(a bubble level, a plastic cap or something similar). Flash can also
be enabled/disabled from Canon menu.
Restoring default settings from Canon menu should enable the flash.
If you are sure it's not a hardware issue, can you try older ML
versions to see which one works with your flash?
You may try one which has the flash/noflash option, and see what ML
shows about flash setting (it should say Flash: ON).
In latest ML version, the only flash-related option is flash exposure
compensation with a wider range (-10...+3 EV), and it's only applied
when you change it from the menu.
> I encountered something odd with this latest build and my 550/T2i.
> When using the bundled Canon EF-S 18-55 Zoom lens w/ the July 8th 2011
> build I noticed that when I manually zoomed the lens I would hear a
> clicking from the lens as if the aperture was engaging briefly ever
> few seconds. I would restart the camera to try to fix this but the
I can reproduce this behavior without ML, with my kit lens. If the
aperture would remain in the same position (mechanically), the
f-number would decrease as you zoom in. The camera opens the aperture
to keep the f-number (more or less) constant; this causes clicking
sounds and flicker.
If the focal length sensor is not accurate, the aperture may go back
and forth a few times.
> Thanks again for this awesome software. Just wanted to know if it is
> possible for you guys to put in a burst speed of say 15 fps or more at
> low resolution say 1 or 2 MP or more in the cam.
Movie recording is done at 24...30fps with around 2 MP ;)
--
http://magiclantern.wikia.com/wiki/Unified/UserGuide
Also, there's a script which logs in to wikia and updates this page,
so from now on, the wiki manual will be as up-to-date as the PDF and
in-camera versions.
This makes it easier for you to edit the user guide, so please feel
free to improve it. Probably it's best to add some images for certain
features (e.g. zebras, focus peaking...)
Enjoy!
You need to copy the /contents/ of this folder to the root of your SD
card for the files to be in the right place.
--
Paul Nolan, CEO Idruna Software Inc.
Scrax is testing the very latest builds, which can be obtained by
compiling the source code from the Mercurial repository.
I upload these builds to my Dropbox account for early testers; this
should result in more stable releases... in theory :)
If anyone would like to run some bleeding edge code, please let me know.
I didn't build the full archives yet; there are a few issues which I
want to fix before the next release.
Your idea would require some kind of a master autoexec.bin working as
bootloader. I also thought at some bootloader which would detect the
camera firmware (550D, 60D, 600D, 500D, 5D2) and load the right binary
(either named by the camera model/version, or in a separate
subfolder). For now, I was only able to freeze the camera with my
attempts.
Other ideas: take a look at Rockbox. They support a dozen of MP3
players, and they have a single installer (but a separate manual for
each device).
http://www.rockbox.org/download/
http://www.rockbox.org/manual.shtml
I'm also thinking at some kind of automatic build server, like the CHDK one.
http://mighty-hoernsche.de/
The camera can only boot from B:/autoexec.bin (this is hardcoded in
the firmware).
It would be possible to rename/overwrite files from Magic Lantern
menu, but as soon as you will select an older autoexec.bin, you will
be stuck with that.
What about the other two power saving options? Do they work or not?
Download this autoexec.bin, set "turn off display after 5 seconds" and
tell me what does the top left number show.
http://dl.dropbox.com/u/4124919/bleeding-edge/550d/autoexec.bin
When you press any button, the number should become 50, and countdown
to 0. When it reaches 0, it should turn the display off. Sometimes it
may get tricked by changes in exposure (ML may believe they are button
presses, since they both go through gui_main_task).
Chris71,
Download the same version and tell me the other numbers, and whether
you see a "bbar" somewhere in the middle of the screen, or not.
On Wed, Jul 27, 2011 at 9:21 AM, Marcin Konopski
Tip: on 550D you can bring the display back on by putting your hand
near the LCD sensor.
For even more power saving in LiveView while not recording (and also
in photo mode), probably it would make sense an option which goes to
Play or Menu mode and then turns off the display. I believe this will
turn off the sensor, too. What do you think?
I've only added these debug messages to the existing code.
An option would be to include these settings in display profiles.
Experimental builds can already toggle picture style in this way (this
behavior can be enabled/disabled from Tweaks menu).
I'm not sure which is the best way to balance between extreme
customizability and ease of use / low complexity and memory usage, so
I'd be happy to hear your opinions.
It could be an option, and it could be extended to different power