- 1 Magic Lantern v2.3 - FAQ
- 2 Generale
- 3 Usage
- 3.1 How do I bring up the Magic Lantern menus?
- 3.2 Why can't I see the Magic Lantern overlays I enabled?
- 3.3 How do I restore ML default settings?
- 3.4 How do I erase all of the images without removing ML?
- 3.5 How do I record for more than 12 minutes?
- 3.6 How do I get exposure times longer than 30 seconds?
- 3.7 How do I see shutter counter / CMOS temperature?
- 3.8 Can I use LiveView in complete darkness?
- 3.9 How do I shoot timelapse?
- 3.10 I want to use my camera as fast as possible. Can ML help me?
- 3.11 Does Magic Lantern consume more power than standard Canon firmware?
- 3.12 Why the audio is so quiet / noisy after disabling AGC?
- 3.13 How do I disable AGC on 600D/T3i, 5D Mark III, 6D and so on?
- 4 Installation
- 5 Troubleshooting
- 5.1 It won't boot!
- 5.2 What happened with movie mode remap?
- 5.3 Why does the camera take pictures when pressing the shutter half-way?
- 5.4 Why do I have to press the shutter button twice to take a picture?
- 5.5 Why did the autofocus stop working?
- 5.6 Why picture style X does not appear in movie mode?
- 5.7 My camera freezes / I get ERR70/80/99 / I get corrupted files. Why?
- 5.8 What about ERR20 when taking pictures?
- 5.9 Why feature X doesn't work properly?
- 6 Technical
- 7 Misc
- 8 Troll Questions
- 8.1 When will we be able to shoot in our Canon 100 fps, 200 fps, 1000 fps!?
- 8.2 My Sony camera can record 1080p @ 60fps, why my 650D can't?
- 8.3 I am new here I dont know anything about coding [...] I want to be able to shoot Raw and 4K
- 8.4 Why is it so difficult to change the LiveView resolution, when elements like bit rate control and HDR video seem to be relatively easy to implement?
- 8.5 Canon has announced that the SX280 will shoot 60fps at 1080p and a 14 fps Burst rate. I am sure the Digic 6 can easily handle the double of both rates.
- 8.6 When will you release the next version?
Magic Lantern v2.3 - FAQ[edit | edit source]
Generale[edit | edit source]
Cos'è?[edit | edit source]
Magic Lantern è un miglioramento del firmware Canon che libera la vosta DSLR Canon, consentendo di utilizzare molte funzioni utili. È un framework aperto (GPL) per lo sviluppo di estensioni per il software ufficiale.
Magic Lantern sostituisce completamente il firmware Canon?[edit | edit source]
No. Magic Lantern funziona sulla memorycard,come aggiunta al firmware standard. Sarete ancora in grado di accedere a tutte le funzionalità di Canon.
Per tornare al firmware Canon, puoi:
- Premere e tenere premuto SET all'accensione per bypassare ML solo una volta (solo per l'ultima versione di ML).
- Formattare la tua memorycard tramite la DSLR e scegliere di rimuovere Magic Lantern.
- Disabilitare il bootflag (questo disinstallerà ML dalla fotocamera, per fare questo, eseguire l'aggiornamento del firmware Canon e seguire le istruzioni)
Magic Lantern è soltanto per i video della Canon 5D Mark II con sensore Full Frame?[edit | edit source]
No. Le prime versioni sono state create da registi indipendenti e su misura per la produzione di video su 5D Mark II. Le cose sono cambiate quando Magic Lantern fù portato su macchine fotografiche più piccole (APS-C), come la 550D, 60D, 600D e 500D, che ha attirato gli sviluppatori interessati sia alla fotografia che ai video su DSLR.
E' legale?[edit | edit source]
Si. E`legale perche`installato sulla memoria CF o SD e non modifica la Firmware della camera.
This is a clean room / black box reverse engineering effort and as such should be OK. Frequently asked questions about reverse engineering addresses the legality question; producing an interoperable product is one of the explicit allowances enshrined in law.
Magic Lantern does not contain any Canon code. Also, we do not distribute any copyrighted code or cryptographic secrets, neither from Canon nor from any other third party. All the knowledge used for development was obtained by analyzing ARM code, by experimenting, and from lawfully obtained documentation.
Is it safe?[edit | edit source]
No. Magic Lantern was created by reverse engineering an undocumented system that controls hardware. Therefore, we can't be certain that it's 100% safe.
Magic Lantern does not replace Canon code (which is stored in ROM), but it does change the settings (which are saved to a non-volatile memory). If Magic Lantern would set incorrect values for certain settings, this may cause the camera not to boot (even without ML).
The same risk is present if you use third party software for USB remote control. These programs use the same API for changing camera settings (properties), and Canon code does not always check the validity of the settings before saving them to NVRAM. Here's a proof. Even developers of USB control software, who use Canon's own SDK, agree with this.
Imagine that your config file gets corrupted and you can't just delete it and start from scratch. We consider this a design flaw in Canon software. We did encounter such problems during development, but we were able to recover from them. For technical details, see Unbricking.
Probably the safest way to run Magic Lantern (or any third party camera control software) is to use custom modes - in these modes, Canon code does not save user settings to NVRAM.
In practice, we are doing our best to prevent these situations, and thousands of users are enjoying it without problems. However, this does not represent a guarantee - use it at your own risk.
Actually, using Magic Lantern we have successfully unbricked a 5D Mark II damaged by a USB remote controller app.
Does it void my warranty?[edit | edit source]
A Magic Lantern user posted this on dpreview:
I've spoken to canon Cps (pro service in UK) and they've advised me that it's quite possible to downgrade firmware from new version to older version BUT they advised me to send it in to Canon for them to do it and test. Small service charge would be involved but could be done while I wait.
Interestingly enough, they also advised me that Magic Lantern firmware would not invalidate my Canon Warranty as it's not a hardware modification. Though I'm reluctant to find out for sure And another user posted this on t2iforum: I contacted Canon Support Portugal about using ML, the answer was the following:
(…) the use of custom firmware or any other third party acessory with our equpment will void the warranty of the product IF PROVEN that the malfunction of the device was caused by the use of those.
Canon respects the rights that their customers have to decide what accessories or firmware to use, although we do not recommended their use, and we are not responsible for any damage to the equipment.The Magic Lantern firmware is distributed with NO WARRANTY and NO GUARANTEES are provided. It might work. It might not. It hasn't destroyed any cameras yet, but who knows.
How will it interact with future upgrades from Canon?[edit | edit source]
We have updated it to work with the latest version of Canon firmware on all supported cameras. This is a manual process to find the symbols in each new version, although tools like patchdiff2, Gensig/Finsig and GPL Tools/match.py make it much easier. Each new version must be statically linked against addresses in the firmware ROM as if it were a library, which requires locating the entire set of symbols.
Despite this tight integration, Magic Lantern software does not contain any Canon code. It is entirely a clean-room implementation that runs along side the official Canon firmware as a separate DryOS task.
Usage[edit | edit source]
[edit | edit source]
Press the DELETE button.
Why can't I see the Magic Lantern overlays I enabled?[edit | edit source]
Magic Lantern Overlays are only displayed when the Canon overlays are disabled. Turn GlobalDraw on. Then, while in Liveview or Movie mode, press the DISP or INFO button until the Canon overlays are turned off.
How do I restore ML default settings?[edit | edit source]
Delete the config file (MAGIC.CFG) and restart the camera.
How do I erase all of the images without removing ML?[edit | edit source]
Canon menu → Format → Format card, keep Magic Lantern.
How do I record for more than 12 minutes?[edit | edit source]
- Lower the `bitrate`_ (CBR 0.4 will let you record continuously for 30 minutes).
- Use `Movie restart`_, but you will lose a few seconds when a new file is created.
- To record continuously for more than 30 minutes, you need to use a HDMI recorder. Enable the Clear Overlays feature to hide the focus box and the 16:9 bars, and make the half-shutter button sticky to prevent the camera from turning off LiveView after 30 minutes.
Technically, there's no 12 minute limit. There's a 30 minute limit and a 4 GB limit, whichever comes first. With default bitrate settings, the 4 GB limit is reached after around 12 minutes (more or less).
How do I get exposure times longer than 30 seconds?[edit | edit source]
You may use:
- `Bulb timer`_ (for a single photo).
- `HDR`_ bracketing in manual mode.
- `Bulb ramping`_ (for timelapse).
How do I see shutter counter / CMOS temperature?[edit | edit source]
Look in `Debug`_ menu.
Can I use LiveView in complete darkness?[edit | edit source]
Yes. Increase display gain, use a low FPS (with FPS override), or both.
Also check out the dark color schemes optimized for night shooting, or try disabling exposure simulation.
How do I shoot timelapse?[edit | edit source]
You have a couple of options:
- Intervalometer - the classic way. You will have to postprocess the shots in order to create the final movie. In this mode, you also have access to advanced options like bulb and focus ramping, HDR timelapse or very long exposures.
- FPS override - simply select a low FPS value (down to about 0.2 FPS) and ML will record a timelapse.
- Silent picture timelapse. Only for very advanced users.
I want to use my camera as fast as possible. Can ML help me?[edit | edit source]
Yes. Check out these features:
- Shortcut keys for commonly used functions.
- Display presets - create custom LiveView modes (for example, your favorite settings for checking exposure, focus, framing and so on).
- Ultra fast zoom in playback mode.
- Change image review mode to PLAY - after taking a picture you can press Zoom In right away and check critical focus in a split-second.
- Navigate the menu using the scrollwheels - much faster than with arrow keys.
- Simple menu - only display the essentials, so you don't have to scroll through lots of menus.
Does Magic Lantern consume more power than standard Canon firmware?[edit | edit source]
In LiveView it draws 3-5% more power (measured on 60D and 5D Mark II with zebra and focus peaking active). You can do your own tests if you have a 60D.
Magic Lantern can reduce power consumption by dimming or turning off the LCD screen, or by pausing LiveView without moving the mirror. See `Power saving`_ for details.
In plain photo mode with display off, the power draw is a bit higher, because Magic Lantern disables CPU powersaving features (otherwise, intervalometer and other ML functions would stop running). We have measured 6% / hour on 60D (compared with 4% / hour with Canon firmware), and 10% / hour on 5D Mark II (compared with 5% / hour with Canon firmware).
Why the audio is so quiet / noisy after disabling AGC?[edit | edit source]
You will have to adjust the volume manually; use the audio meters to determine the proper level.
Best audio is obtained by use of a preamp system fed to the camera. As a general rule, the use of a quiet preamp to send the signal to the camera will result in better the sound recorded in camera. Use of a preamped XLR adapter like the JuicedLink CX231 or a field mixer will give superior results. You may also use a recorder like Zoom H1, H2 or H4n, but since the line out level is much higher than the mic level, you will have to turn the output down from your recorder or use a pad cable.
For more info, check out the Canon DSLR Audio thread on dvxuser and AGC Disable - Magic Lantern vs. Juicedlink? on dvinfo.
How do I disable AGC on 600D/T3i, 5D Mark III, 6D and so on?[edit | edit source]
From Canon menu.
Installation[edit | edit source]
How do I install it?[edit | edit source]
Follow the install guide. You will have to copy Magic Lantern files on your card and run Update firmware from the menu. The running firmware shuts down, loads the file into RAM and starts it running. Rather than reflashing the ROMs, this new program starts the DryOS boot process to install itself.
How do I uninstall it?[edit | edit source]
Simply format the card. The bootflag will be still there, but it will not affect normal operation (except for EyeFi cards).
To remove the bootflag (for using EyeFi cards), run Firmware Update from a ML card and follow the instructions.
What if I try to use it on a wrong firmware version?[edit | edit source]
It will not boot. Magic Lantern checks firmware version before attempting to run - if it doesn't match, the card LED will start blinking and you'll have to take the battery out.
Sometimes you have the right version number, but a different sub-version number (there are 3 more version digits, which are not displayed on the screen). If it happens, simply upgrade Canon firmware from the links mentioned in the install guide.
Does ML do any persistent changes to my camera?[edit | edit source]
Yes. Besides the bootflag (which is required for auto-boot), there are a couple of other changes which are saved into NVRAM. These are:
- ISO, shutter, aperture, white balance;
- Exposure compensation, drive mode;
- Picture style and associated parameters;
- Flash settings (enabled/disabled, exposure compensation, red eye reduction);
- AF points, AF mode in LiveView, focus box position;
- Exposure simulation setting (in Expo menu; disabled temporarily when using 5x/10x zoom modes);
- Backlight level (for example, it's lowered temporarily if you use `Dim display`_ for power saving);
- Autofocus is moved temporarily to back (*) button whenever ML has to take a picture without autofocusing. This includes HDR bracketing and bulb exposures.
- Autofocus is moved temporarily to half-shutter when you use `AF patterns`_, while changing the AF point;
- Sound recording is disabled temporarily when you use `FPS override`_;
- On 600D, video mode may be changed via ML shortcut key;
- On 50D, movie recording function is changed from ML menu (yes, this is a persistent Canon setting, but it's not present in Canon menus).
With few exceptions, these settings can also be changed from Canon menus or controls.
A few settings are changed temporarily during certain operations (for example, autofocus for bracketed shots), but these settings are saved by Canon firmware in NVRAM. If you take the battery out in the middle of the operation (for example, in the middle of taking a picture), ML won't be able to restore these settings back to your initial values, and you'll have to change them back from Canon menus.
To the best of our knowledge, all these settings are restored to default values when you run Clear camera settings and Clear custom functions from Canon menu.
All persistent changes can be seen in ML source code by examining the calls to prop_request_change. Some of the changes are not persistent (for example, LiveView zoom level), and they were not included in the above list.
Troubleshooting[edit | edit source]
It won't boot![edit | edit source]
- If the LED is blinking continuously, you have the wrong Canon firmware version.
- Make sure you didn't delete AUTOEXEC.BIN from your ML card. If you did, format the card, take the battery out, and reboot.
- If you still have problems, ask on the forum.
What happened with movie mode remap?[edit | edit source]
We had serious problems with it, so it was disabled. The problems were confirmed with a minimal example code, so the issue is either in Canon firmware (which was probably not designed for dynamic mode remapping) or in the way we request the mode remapping procedure.
The only way to get it back is to show us a safe way to change the shooting mode. For this you need to point out what's wrong with this call: prop_request_change(PROP_SHOOTING_MODE, &new_mode, 4), and suggest a different method - which can only be done by examining Canon code and understanding how mode switching works.
Testing will not help - the probability of things going wrong is very low, but nonzero.
Why does the camera take pictures when pressing the shutter half-way?[edit | edit source]
`Trap focus`_ may be active.
[edit | edit source]
Mirror Lockup (MLU) is active.
Why did the autofocus stop working?[edit | edit source]
It was probably moved to back button (* or AF-ON). Check your custom functions. It may happen if you take the battery out in the middle of photo shooting.
Anyway… any serious DSLR user should set AF to back button ;)
Why picture style X does not appear in movie mode?[edit | edit source]
You may need to register it from Canon menu. This is not related to ML, but people tend to blame ML for Canon quirks.
My camera freezes / I get ERR70/80/99 / I get corrupted files. Why?[edit | edit source]
- Format your card from the camera. Some of these problems are caused by filesystem corruption or cheap card readers. Always use the safe removal feature before you unplug your card from your computer.
- If you get ERR70, you will also get a crash log on your card, under ML/LOGS directory. Please send this file to developers.
- Run the stability tests from the Debug menu. If the tests fail, report a bug and send your config file to developers.
- To report bugs, go here.
What about ERR20 when taking pictures?[edit | edit source]
This problem is not related to (or caused by) Magic Lantern.
You will get this error when your shutter mechanism no longer works properly. Contact your Canon service center.
Consider entering your shutter count in the Camera Shutter Life Database.
Why feature X doesn't work properly?[edit | edit source]
- Read the manual. Some features may not be 100% intuitive, or it may be a known issue.
- Look in the forum. If you don't find the solution, ask for help.
Technical[edit | edit source]
Does it work with CHDK?[edit | edit source]
We have used some of the CHDK tools to learn about Canon firmware files, but this is all new code. They have done an amazing job of supporting hundreds of different camera models across multiple architectures and operating systems. At some point in the future chdk might be ported to the 5D Mark 2, but this project is much more focused on just the 5D Mark II and the needs of film makers. CHDK is a great project for Canon's Point-and-Shoot cameras. Without their initial effort in understanding DryOS, Canon's firmware files and the boot process, I wouldn't have been able to make as much progress as quickly as I did. While I was able to use modern tools to analyze dump files of ROM images thanks to their efforts, they got started bitbanging a UART via the status LED on a camera body. That's truly hardcore.
Why the name change?[edit | edit source]
Originally the project was called just 5D Mark Free, but out of an abundance of caution it seemed best to avoid Canon's trademarks.
What is it written in? Can I get the source?[edit | edit source]
The firmware hack is in C, with some inline assembly for boot strapping. The firmware build tools are in Perl and use Makefiles for dependency tracking. You need an arm-linux-elf build of gcc and binutils. Most of the code analysis has been done with objdump, strings and the IDA demo. No tech support will be provided. If it breaks you get to keep both pieces. If you know what all of these terms mean and aren't scared of the possibility of breaking your camera, you can download the Magic Lantern firmware source code.
How do I get a ROM0.bin firmware image?[edit | edit source]
We do not distribute ROM images, nor IDA .idb files, since they are verbatim copies of Canon's copyrighted code. You can generate the ROM images from your own camera by compiling with CONFIG_DEBUGMSG=1 and then selecting Dump ROM from Debug menu.
What are all of the 0xff81beef things and funny names like EP_SetManualMovieMode()?[edit | edit source]
These are the addresses in the official ROM firmware for different functions and names that we have given to functions. If you load the ROM0.bin image into IDA or use objdump you can trace through the instructions to determine how the software works. If you are just using the camera, they don't need to mean anything to you, but they give other developers a place to look in the firmware image.
The function names are unlikely to be the same as the ones in Canon's source code, which we have never seen. We name functions based on what they seem to do, or debugging / diagnostic strings embedded in the function. It isn't perfect, but it is sufficient to locate the important things for task creation, file I/O and GUI operation.
Misc[edit | edit source]
Has Canon contacted you?[edit | edit source]
No one at Canon has contacted us regarding Magic Lantern or software development for their DSLR cameras. We are very eager to discuss the project with them, however, so if you have any technical contacts inside of Canon's software team, please put them in touch with us.
Troll Questions[edit | edit source]
Ask one of those and you may get banned from our forum ;)
When will we be able to shoot in our Canon 100 fps, 200 fps, 1000 fps!?[edit | edit source]
When you buy this camera and slap a Canon sticker on it.
My Sony camera can record 1080p @ 60fps, why my 650D can't?[edit | edit source]
Because the 650D isn't your Sony camera.
I am new here I dont know anything about coding [...] I want to be able to shoot Raw and 4K[edit | edit source]
Why stop at 4k? Why not 8K?
Why is it so difficult to change the LiveView resolution, when elements like bit rate control and HDR video seem to be relatively easy to implement?[edit | edit source]
What's that got to do with the price of rice in China?
Knowing where to tweak which register values to get other resolutions is as simple as translating a pile of Egyptian glyphs.
Canon has announced that the SX280 will shoot 60fps at 1080p and a 14 fps Burst rate. I am sure the Digic 6 can easily handle the double of both rates.[edit | edit source]
How exactly did you reach this conclusion?
When will you release the next version?[edit | edit source]
When it's done.
Magic Lantern is a free and open-source project being developed in our free time. We have full-time jobs, families, children, so the progress is not always as rapid as we would like. More info here and here.
Not only that, but the nature of development, especially the kind of reverse-engineering that goes on in the case of something like ML, is unpredictable. A single issue might be fixed in five minutes, or it may take six months to solve.
Chasing the devs for ideas about timescales, feature implementations and so on is a little pushy. They will get to it in their own time and announce what they are working on and so on here. So feel free to ask about features, the progress of things and so on, but the “when” question only really serves to slightly irritate devs.