Magic Lantern es una mejora en el firmware original de Canon que libera tu Canon DSLR, que permite utilizar muchas características útiles. Se trata de un código abierto (GNU) para el desarrollo de extensiones para el software oficial.

No. Magic Lantern se ejecuta desde la tarjeta de memoria como un complemento (add-on) sobre el firmware estándar de Canon. Se tendrá acceso siempre a todas las funcionalidades del firmware de Canon.

Para regresar al firmware original de Canon, se debe de:

• Mantener presionado el botón de SET mientras se enciende la cámara.
• Formatear la tarjeta de memoria.
• Deshabilitar la bandera de reinicio (esto desinstalara ML de la cámara; para hacer esto, correr Firmware Upgrade y seguir las instrucciones).

No. Las primeras versiones fueron desarrolladas por filmakers independientes y adaptadas para la producción de video en la 5D Mark II. Las cosas han cambiado cuando Magic Lantern fue llevado a cámaras más pequeñas (APS-C) tales como: la 550D, 60D, 600D y 500D, las cuales atrajeron a desarrolladores interesados en ambas cosas: la fotografía y el vídeo.

Visite la galería para ejemplos de fotos.

Esto es esfuerzo en ingeniería inversa (cuarto vacío / caja negra) y como tal, debería de estar bien.Preguntas frecuentes acerca de la ingeniería inversa 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.

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.

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:

Quote

(…) 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.

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.

Press the DELETE button.

You may be in Easy menu mode, where Magic Lantern only shows the features considered essential. This menu may vary with the shooting mode (photo mode, movie mode, LiveView, HDMI etc).

Press MENU to open the advanced menu, where all options are displayed.

Delete the config file (MAGIC.CFG) and restart the camera.

Canon menu → Format → Format card, keep Magic Lantern.

• 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).

You may use:

• `Bulb timer`_ (for a single photo).
• `HDR`_ bracketing in manual mode.
• `Bulb ramping`_ (for timelapse).

Look in `Debug`_ menu.

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.

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.

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.

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).

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.

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.

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.

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.

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.

• 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.

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.

`Trap focus`_ may be active.

Mirror Lockup (MLU) is active.

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 ;)

You may need to register it from Canon menu. This is not related to ML, but people tend to blame ML for Canon quirks.

• 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.

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.

• 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.

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.

Originally the project was called just 5D Mark Free, but out of an abundance of caution it seemed best to avoid Canon's trademarks.

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.

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.

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.

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.

System Message: ERROR/3 (faq.rst, line 118); backlink

Unknown target name: bitrate.

System Message: ERROR/3 (faq.rst, line 119); backlink

Unknown target name: movie restart.

System Message: ERROR/3 (faq.rst, line 130); backlink

Unknown target name: bulb timer.

System Message: ERROR/3 (faq.rst, line 131); backlink

Unknown target name: hdr.

System Message: ERROR/3 (faq.rst, line 132); backlink

Unknown target name: bulb ramping.

System Message: ERROR/3 (faq.rst, line 137); backlink

Unknown target name: debug.

System Message: ERROR/3 (faq.rst, line 172); backlink

Unknown target name: power saving.

System Message: ERROR/3 (faq.rst, line 215); backlink

Unknown target name: dim display.

System Message: ERROR/3 (faq.rst, line 217); backlink

Unknown target name: af patterns.

System Message: ERROR/3 (faq.rst, line 218); backlink

Unknown target name: fps override.

System Message: ERROR/3 (faq.rst, line 245); backlink

Unknown target name: trap focus.