User Tools

Site Tools


faq

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
faq [2021/02/09 18:08] – [How long it will take to port ML on camera XYZ?] a1exfaq [2024/01/15 03:14] (current) – [Is it legal?] fix to archve.org links petabyte
Line 24: Line 24:
 ===== Is it legal? ===== ===== Is it legal? =====
  
-This is a ''clean room'' / ''black box'' reverse engineering effort and as such should be OK. [[http://www.chillingeffects.org/reverse/faq.cgi|Frequently asked questions about reverse engineering]] addresses the [[http://www.chillingeffects.org/reverse/faq.cgi#QID195|legality question]]; producing an interoperable product is one of the explicit allowances enshrined in law.+This is a ''clean room'' / ''black box'' reverse engineering effort and as such should be OK. [[https://web.archive.org/web/20140207082343/http://www.chillingeffects.org/reverse/faq.cgi|Frequently asked questions about reverse engineering]] addresses the [[https://web.archive.org/web/20140321133324/http://www.chillingeffects.org/reverse/faq.cgi#QID195|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. 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.
Line 33: Line 33:
 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). 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. [[https://vimeo.com/groups/magiclantern/forum/topic:255083|Here's a proof]]. Even developers of USB control software, who use Canon's own SDK, [[http://www.reikan.co.uk/photography/blog/?p=1550|agree with this]].+**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. [[https://web.archive.org/web/20120619120503/https://vimeo.com/groups/magiclantern/forum/topic:255083|Here's a proof]]. Even developers of USB control software, who use Canon's own SDK, [[https://web.archive.org/web/20130327144523/http://www.reikan.co.uk/photography/blog/?p=1550|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]]. 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]].
Line 41: Line 41:
 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**. 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**.
  
-As a precaution, the installer asks you to make a backup copy of your ROM files on the PC. That way, if something goes wrong, we have higher chances of being able to diagnose or fix he issue.+As a precaution, the installer asks you to make a backup copy of your ROM files on the PC. That way, if something goes wrong, we have higher chances of being able to diagnose or fix the issue.
  
-Actually, using Magic Lantern we have successfully [[http://vimeo.com/groups/magiclantern/forum/topic:255083|unbricked a 5D Mark II damaged by a USB remote controller app]].+Actually, using Magic Lantern we have successfully [[https://web.archive.org/web/20130622070509/http://vimeo.com/groups/magiclantern/forum/topic:255083|unbricked a 5D Mark II damaged by a USB remote controller app]].
 ===== Does it void my warranty? ===== ===== Does it void my warranty? =====
  
Line 52: Line 52:
 > 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 :-)  > 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 [[http://www.t2iforum.com/firmware-updates/noob-questions-about-magic-lantern-and-warranty/msg28145/#msg28145|posted this on t2iforum]]:+And another user [[https://web.archive.org/web/20161025003359/http://www.t2iforum.com/firmware-updates/noob-questions-about-magic-lantern-and-warranty/msg28145/|posted this on t2iforum]]:
  
 > I contacted Canon Support Portugal about using ML, the answer was the following: > I contacted Canon Support Portugal about using ML, the answer was the following:
Line 65: Line 65:
 ===== How will it interact with future upgrades from Canon? ===== ===== How will it interact with future upgrades from Canon? =====
  
-We have updated it to work with the latest version of Canon firmware on all supported camerasThis is a manual process to find the symbols in each new version, although tools like [[http://code.google.com/p/patchdiff2/|patchdiff2]], [[http://magiclantern.wikia.com/wiki/Gensig_finsig|Gensig/Finsig]] and [[http://magiclantern.wikia.com/wiki/GPL_Tools/match.py|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.+ML builds/versions are branded for a dedicated camera and an exactly matching firmware version. If Canon supplies a new firmware ML and new firmware version become incompatible after installation. Cam will not startup properly with ML card inserted. If a dev finds time to port ML to the new firmware version and changes are essential a new ML version may be there in time. However it is completely possible that this new firmware will be ignored because of lack of time. In this case you have to downgrade to previous (compatible) firmware version to make ML run againML project provides links to compatible firmware versions. According to Canon downgrade is not possible but [[glossary#firmware_update_upgrade_downgrade|we think otherwise.]]\\   
 +Porting ML to a new firmware version is a manual (and extensive) process to find the symbols in each new version, although tools like [[http://code.google.com/p/patchdiff2/|patchdiff2]], [[http://magiclantern.wikia.com/wiki/Gensig_finsig|Gensig/Finsig]] and [[http://magiclantern.wikia.com/wiki/GPL_Tools/match.py|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. 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.
  
 +===== Is Magic Lantern available in other languages? =====
 +Currently, Magic Lantern releases do not have multiple languages built in.
 +You can find a work in progress module that aims to translate menus [[https://www.magiclantern.fm/forum/index.php?topic=26228.msg236617#msg236617|here]].
 +
 +PS: We know there is a chinese version in the wild which is payware. This ML project team has no affiliations with it and neither endorse its usage nore support it.
 +
 +===== Is this FAQ available in other languages? =====
 +No. If there are any they are not supported/updated/maintained and may be outdated/incorrect.
 +
 +PS: If you feel encouraged to offer your assistance to translate this FAQ ... we have no way to maintain it properly. It has been discussed but until we find a sustainable way to keep it up-to-date with limited man-power we have to decline your offer. 
 ====== Usage ====== ====== Usage ======
  
Line 74: Line 85:
  
 Press the ''DELETE'' button. Press the ''DELETE'' button.
 +
 +===== Can I start my cam without ML? =====
 +
 +Yes, press SET before startup and keep it pressed until startup is completed.
 +
 +And you can insert a card not enabled for Magic Lantern and startup cam. 
  
 ===== Why can't I see feature X in the menu? ===== ===== Why can't I see feature X in the menu? =====
  
-The feature you are looking for is probably available in a module (for example, raw video, dual ISOLua scripting).+The feature you are looking for is probably available in a module. These are the features coming with ML programmed as loadable modules:{{wiki:modules_1.png?380  }} 
 +  * Advanced Intervalometer -> adv_int.mo  
 +  * Arkanoid -> arkanoid. mo 
 +  * Auto Exposure -> autoexpo.mo 
 +  * Benchmarks -> bench.mo 
 +  * Deflicker -> deflick.mo 
 +  * Auto-AFMA -> dot_tune.mo 
 +  * Dual-ISO -> dual_iso.mo 
 +  * EDMAC Tools-> edmac.mo 
 +  * Auto ETTR -> ettr.mo 
 +  * File Manager -> file_man.mo 
 +  * Image Name -> img_name.mo 
 +  * Lua Script -> lua.mo 
 +  * MLV Lite -> mlv_lite.mo 
 +  * MLV Replay -> mlv_play.mo 
 +  * MLV (Full-MLV-> mlv_rec.mo 
 +  * MLV Sound -> mlv_snd.mo 
 +  * Picture Viewer -> pic_view.mo 
 +  * Selftests -> selftest.mo 
 +  * Silent Pics -> silent.mo
  
 Navigate to the Modules tab, load the module(s) you need (**not** all of them!), then restart your camera. Navigate to the Modules tab, load the module(s) you need (**not** all of them!), then restart your camera.
  
-More info about modules: [[http://www.magiclantern.fm/forum/index.php?topic=12713.0]]+More info about modules: [[ml>forum/index.php?topic=12713.0|How to install and load modules]] 
 + 
 +If you still can't find it, the feature is probably not available on your camera. See [[http://builds.magiclantern.fm/features.html|feature comparison table]]. 
 + 
 +===== Which Magic Lantern build is running on my camera? ===== 
 + 
 +Build version is visible in Help tab/screen's bottom section. You should always provide this information if you have a question/issue to share with ML forums. Your build designation may be different, though. 
 + 
 +{{wiki:Help_tab.png?480}}
  
-If you still can't find it, the feature is probably not available on your camera. See [[http://builds.magiclantern.fm/#/features]] for a feature comparison table. 
  
 ===== Why can't I see the Magic Lantern overlays I enabled? ===== ===== Why can't I see the Magic Lantern overlays I enabled? =====
  
-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.+Magic Lantern overlays are only displayed in ML's own liveview screen(s). [[camera_help#Global_Draw|Global Draw]] must be enabled (ON){{wiki:global_draw_1.png?20}} and [[camera_help#Clear_overlays|Clear Overlays]] must be disabled {{wiki:clear_overlays_1.png?20}} for the modes you are using. Then, while in Liveview or Movie mode, press the DISP or INFO button until you are past Canon's own liveview screens.
  
 In general, ML features that require some extra setup will be grayed out in the menu, and the help text at the bottom of the screen will tell you why. In general, ML features that require some extra setup will be grayed out in the menu, and the help text at the bottom of the screen will tell you why.
Line 93: Line 136:
 ===== How do I restore ML default settings? ===== ===== How do I restore ML default settings? =====
  
-Prefs -> Config -> Restore ML defaults.+Prefs -> Config -> Restore ML defaults.{{wiki:Restore_ML_Defaults_1.png?100}}
  
-Alternative: format the card and do a fresh install.+Alternative: format the card and do a fresh install.\\ 
 +Just re-installing Magic Lantern does **not** change/reset existing Magic Lantern settings!
  
 ===== How do I erase all of the images without removing ML? ===== ===== How do I erase all of the images without removing ML? =====
Line 101: Line 145:
 Canon menu -> Format -> Format card, keep Magic Lantern. Canon menu -> Format -> Format card, keep Magic Lantern.
  
-===== How do I record for more than 12 minutes? =====+===== How do I record for more than 12 minutes? (Digic 4 cameras) =====
  
   * H.264:   * H.264:
-    * Lower the [[#id1|`bitrate`_]] (CBR 0.4 will let you record continuously for 30 minutes). +    * Lower the [[#id1|`bitrate`_]] (CBR 0.4 will let you record continuously for 30 minutes).{{wiki:bit_rate_1.png?20}} 
-    * Use [[#id3|`Movie restart`_]], but you will lose a few seconds when a new file is created.+    * Use [[#id3|`Movie restart`_]], but you will lose a few seconds when a new file is created.{{wiki:movie_restart_1.png?20}}
     * 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).     * 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).
  
-  * RAW:+===== How do I record/stream for more than 30 minutes? ===== 
 + 
 +  * H.264: 
 +    * There is no flawless way to achieve this but a workaround: 
 +    *  Use [[#id3|`Movie restart`_]], but you will lose a few frames until a new file is created.{{wiki:movie_restart_1.png?20}} 
 +     
 +  * RAW/MLV   
     * Can record continuously until the card gets full (no 30-minute limit).     * Can record continuously until the card gets full (no 30-minute limit).
     * File sizes are huge; you may want to reduce resolution and/or FPS; also use a large card.     * File sizes are huge; you may want to reduce resolution and/or FPS; also use a large card.
-    * exFAT recommended; otherwise, when creating a new 4GB segment, the speed drops a bit and recording may stop.+    * exFAT recommended; otherwise, when creating a new 4GB segment, the speed drops a bit and recording may stop. Don't forget to enable ExFat option in MLV menu.{{wiki:Files_4GiB_1.png?20}} 
 + 
 +  * External HDMI recorder or HDMI capture device connected to PC + recording software: 
 +    * Enable the [[camera_help#clear_overlays|Clear Overlays]] feature to hide focus box in AF mode and 16:9 bars.{{wiki:clear_overlays_1.png?20}} 
 +    * Make the half-shutter button sticky (Prefs menu) to prevent the camera from turning off LiveView after 30 minutes. This method is kind of outdated. It is recommended to use:  
 +    * [[https://builds.magiclantern.fm/experiments.html|Experimental lua_fix build]] and setting "30-minute timer Disabled" in Prefs menu -> PowerSave in LiveView {{wiki:30-minute_timer.png?20}} 
 + 
 +  * USB with EOS Utility and liveview: 
 +    * Enable the [[camera_help#clear_overlays|Clear Overlays]] feature to hide focus box in AF mode and 16:9 bars.{{wiki:clear_overlays_1.png?20}} 
 +    * Make the half-shutter button sticky (Prefs menu) to prevent the camera from turning off LiveView after 30 minutes.\\  This method is kind of outdated. It is recommended to use:  
 +    * [[https://builds.magiclantern.fm/experiments.html|Experimental lua_fix build]] and setting "30-minute timer Disabled" in Prefs menu -> PowerSave in LiveView {{wiki:30-minute_timer.png?20}} 
 +    * You need recording/streaming software able to grab liveview content like OBS. 
 +    * Resolution is fixed to 576p! 
 + 
 +  * USB with EOS Webcam Utility: 
 +    * There is no 30 minute limit and therefore no need for ML to interfere! 
 +    * Output is clean, there are no overlays! 
 + 
 +(Some new cameras support UVC/UAC: Cam works as webcam via USB without the need of additional software or drivers. Just plug cam into USB port and you are ready to go. Works with Windows, macOS and Linux. 
 +Supported cameras: R6 Mark II, R8, R10, R50, PowerShot V10) 
 + 
 +===== Will I get better HDMI resolution/bitdepth/... with Magic Lantern? ===== 
 + 
 +At the moment ML can do nothing to enhance HDMI resolution, bit depth, frame rate, ... \\ 
 +ML is able to bypass 29:59 time-out (see topics above) and is able to enforce VGA resolution. And of course it can force clean HDMI output: No overlays, no boxes/rectangles even with active AF. 
 + 
 +===== Can ML suppress black columns left and right in HDMI streaming? ===== 
 +No. If your cam gives you 1920x1080 output via HDMI but "active" area is actually 1620x1080 (3:2 ratio)+ black borders left and right: Nothing ML can do about this. You may have to use tools like OBS to grab a 16:9 frame from active area and stretch 1620x911 to Full-HD. 
 + 
 +===== What can Magic Lantern do to enhance "EOS Webcam Utility" performance? ===== 
 +Sorry, nothing ML can do about it. It's 576p for all cams.  
 + 
 +===== RAW/MLV: Can't set resolution to Full-HD: "1920 is not possible in current video mode (max 1728)" ===== 
 + 
 +{{:wiki:raw_non-crop_message.png?400  }} 
 +You have to enter ML's crop mode (see below) to activate settings above [[glossary#native resolution]]. 
 + 
  
-  * External HDMI recorder: 
-    * Enable the ''Clear Overlays'' feature to hide the focus box and the 16:9 bars. 
-    * Make the half-shutter button sticky (Prefs menu) to prevent the camera from turning off LiveView after 30 minutes. 
  
 +===== RAW/MLV: How to enter "crop mode"? =====
  
 +Press magnify/loupe/zoom button while in liveview screen.
 +On some cams you will find an additional entry "Crop mode" in Movie tab. Despite sharing the name those modes are not identical.
 ===== How do I get exposure times longer than 30 seconds? ===== ===== How do I get exposure times longer than 30 seconds? =====
  
Line 125: Line 212:
   * [[#id7|`HDR`_]] bracketing in manual mode.   * [[#id7|`HDR`_]] bracketing in manual mode.
  
-===== How do I see shutter counter / CMOS temperature? =====+===== How do I see shutter counter / internal temperature? =====
  
-Look in the [[#id11|Debug]] menu.+Look in the [[#id11|Debug]] menu. Temperature will be displayed in ML's liveview overlay, too. 
 +{{wiki:shutter_count_1.png?150}}
  
 ===== Can I use LiveView in complete darkness? ===== ===== Can I use LiveView in complete darkness? =====
Line 141: Line 229:
 You have a couple of options: 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 ramping tools, HDR timelapse or very long exposures. +  * Intervalometer - the classic way in photo mode. 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 ramping tools, 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. +  * FPS override - In video mode simply select a low FPS value (down to about 0.2 FPS) and ML will record a timelapse. 
-  * Silent picture timelapse, to save the shutter count. +  * Silent picture timelapse, to save the shutter count. For timelapse best to be combined with Intervalometer
-  * For exposure ramping, the preferred method is [[http://www.magiclantern.fm/forum/index.php?topic=5705.0|AutoETTR followed by deflickering in post]]. +  * For exposure ramping, the preferred method is [[ml>forum/index.php?topic=5705.0|AutoETTR followed by deflickering in post]]. 
-  * For ramping other parameters, try the [[http://www.magiclantern.fm/forum/index.php?topic=8431.0|advanced intervalometer]] module.+  * For ramping other parameters, try the [[ml>forum/index.php?topic=8431.0|advanced intervalometer]] module.
 ===== I want to change the settings quickly, without having to press lots of buttons. Can ML help me? ===== ===== I want to change the settings quickly, without having to press lots of buttons. Can ML help me? =====
  
Line 152: Line 240:
   * Shortcut keys for commonly used functions (including push-button white balance)   * Shortcut keys for commonly used functions (including push-button white balance)
   * Display presets - create custom LiveView modes (for example, your favorite settings for checking exposure, focus, framing and so on).   * Display presets - create custom LiveView modes (for example, your favorite settings for checking exposure, focus, framing and so on).
-  * [[http://www.magiclantern.fm/forum/index.php?topic=8499.0|Config presets]] for all ML settings.+  * [[ml>forum/index.php?topic=8499.0|Config presets]] for all ML settings.
   * Ultra fast zoom in playback mode.   * 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.   * 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.
Line 225: Line 313:
 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. 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.
  
 +===== 5D Mark III: Why are there 2 different ML versions for firmware 1.1.3 and 1.2.3 and which one should I install? ===== 
 +There are major differences between both firmware versions. You have to choose which one fits your needs best. Detailed explanations in [[ml>forum/index.php?topic=14704.msg142089#msg142089|first post in "5D Mark III 1.1.3" thread]].
 +
 +===== Where can I find "Stable/V2.3" version? =====
 +Stable v2.3 is outdated and no longer supported. \\ 
 +Some years ago dev team switched to some kind of rolling release model: Each validated change to ML code (aka: "confirm") creates a new build. \\ 
 +But - essentially - Nighlty Builds are frozen since 2018. Later all work on official experimental builds stopped, too. \\ 
 +For those reasons it is highly unlikely to get another "stable build" in foreseeable future. 
 ====== Troubleshooting ====== ====== Troubleshooting ======
  
Line 232: Line 328:
   * Remove battery and card. Put battery back and start the camera without card.   * Remove battery and card. Put battery back and start the camera without card.
   * If the above works, just format the card and do a fresh install of ML.   * If the above works, just format the card and do a fresh install of ML.
-  * If it still doesn't boot, try running our [[http://magiclantern.fm/forum/index.php?topic=2296.0|diagnostic tools]]. +  * If it still doesn't boot, try running our [[ml>forum/index.php?topic=2296.0|diagnostic tools]]. 
-  * If you still have problems, [[http://magiclantern.fm/forum/|ask on the forum]].+  * If you still have problems, [[ml>forum/|ask on the forum]].
   * Old versions only: if the LED is blinking continuously, you have the wrong Canon firmware version.   * Old versions only: if the LED is blinking continuously, you have the wrong Canon firmware version.
 +
 +===== ML won't work with my SD-to-CF adapter =====
 +ML does not support SD-to-CF adapters. Period. If ML fails to run you are on your own.
 +
 +===== I get an error message "Help files not found" =====
 +
 +{{wiki:help_error.png?480  }}
 +
 +And you get advice to make sure you copied all files. Sorry, but this error message may be considered to be a running gag for insiders. Long story short: You have done nothing wrong and you can do nothing about it! 
 +The help files are missing for a long time and it is not known when they will come back. In the meantime you may want to access the online version (WIP): [[camera_help|Camera Help]]
  
  
 ===== Where is bulb ramping? ===== ===== Where is bulb ramping? =====
  
-It was replaced with AutoETTR followed by deflickering in post. Check this forum thread: [[http://www.magiclantern.fm/forum/index.php?topic=5705.0]]+It was replaced with AutoETTR followed by deflickering in post. Check this forum thread: [[ml>forum/index.php?topic=5705.0|Flicker Free ETTR Timelapse: - -Beginners Guide & Basic Post Processing --]]
  
 This method gives much better results, compared to the old implementation. Why? Because AutoETTR attempts to minimize noise (subject to various constraints), and the deflicker algorithm also corrects variations such as quantization errors when ramping the exposure (up to 0.125 EV for shutter speed) or natural flicker. This method gives much better results, compared to the old implementation. Why? Because AutoETTR attempts to minimize noise (subject to various constraints), and the deflicker algorithm also corrects variations such as quantization errors when ramping the exposure (up to 0.125 EV for shutter speed) or natural flicker.
Line 247: Line 353:
 You can even use the deflickering algorithm for regular pictures, to get consistent brightness in post. You can even use the deflickering algorithm for regular pictures, to get consistent brightness in post.
  
-For advanced ramping options, check out the [[http://www.magiclantern.fm/forum/index.php?topic=8431.0|Advanced Intervalometer]] module.+For advanced ramping options, check out the [[ml>forum/index.php?topic=8431.0|Advanced Intervalometer]] module.
  
 ===== Where is movie mode remap? ===== ===== Where is movie mode remap? =====
  
-We had [[http://www.magiclantern.fm/forum/index.php?topic=1126.0|serious problems]] with it, so it was disabled. The problems were confirmed with a [[http://theoval.cmp.uea.ac.uk/~nlct/latex/minexample/|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.+We had [[ml>forum/index.php?topic=1126.0|serious problems]] with it, so it was disabled. The problems were confirmed with a [[http://theoval.cmp.uea.ac.uk/~nlct/latex/minexample/|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. **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.
Line 281: Line 387:
 You may need to register it from Canon menu. This is not related to ML, but people tend to blame ML for Canon quirks. You may need to register it from Canon menu. This is not related to ML, but people tend to blame ML for Canon quirks.
  
-https://www.youtube.com/watch?v=aMdvMWcHUa4+[[https://www.youtube.com/watch?v=aMdvMWcHUa4|YouTube: Getting Technicolor Cinestyle to work on your T2i in video mode. - DSLR FILM NOOB]] 
 ===== My camera freezes / I get ERR70/80/99 / I get corrupted files. Why? ===== ===== My camera freezes / I get ERR70/80/99 / I get corrupted files. Why? =====
  
Line 288: Line 395:
   * Run the stability tests from the Debug menu. If the tests fail, report a bug and send your config 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.
   * Make sure the problem goes away with stock Canon firmware.   * Make sure the problem goes away with stock Canon firmware.
-    * If yes, it's probably a ML bug. Find a way to reproduce it with the latest nightly build, and report it [[https://bitbucket.org/hudson/magic-lantern/issues?status=new&status=open|on the issue tracker]].+    * If yes, it's probably a ML bug. Find a way to reproduce it with the latest nightly build, and report it [[https://foss.heptapod.net/magic-lantern/magic-lantern/-/issues|on the issue tracker]].
     * Otherwise, it's probably a hardware issue - try a different card, card reader, lens or whatever else might be relevant to your particular problem.     * Otherwise, it's probably a hardware issue - try a different card, card reader, lens or whatever else might be relevant to your particular problem.
-  * To report bugs, [[https://bitbucket.org/hudson/magic-lantern/issues?status=new&status=open|please use the issue tracker]]. +  * To report bugs, [[https://foss.heptapod.net/magic-lantern/magic-lantern/-/issues|please use the issue tracker]]. 
-  * For general questions, installation issues, or for assistance with potentially bricked cameras, [[http://www.magiclantern.fm/forum/index.php?board=4.0|please use the forum]].+  * For general questions, installation issues, or for assistance with potentially bricked cameras, [[ml>forum/index.php?board=4.0|please use the forum]].
  
 ===== What about ERR20 when taking pictures? ===== ===== What about ERR20 when taking pictures? =====
Line 304: Line 411:
  
   * Read the manual. Some features may not be 100% intuitive, or it may be a known issue.   * Read the manual. Some features may not be 100% intuitive, or it may be a known issue.
-  * Look in the [[http://magiclantern.fm/forum|forum]]. If you can't find the solution, you may ask for help. +  * Look in the [[ml>forum|forum]] and here in the [[faq|FAQ]]. If you can't find the solution, you may ask for help. 
-  * If you suspect a ML bug, find a way to reproduce it with the latest nightly build, and report it on the [[https://bitbucket.org/hudson/magic-lantern/issues?status=new&status=open|issue tracker]].+  * If you suspect a ML bug, find a way to reproduce it with the latest nightly build, and report it on the [[https://foss.heptapod.net/magic-lantern/magic-lantern/-/issues|issue tracker]]
 + 
 +===== During installation error message "ML directory not found! Please copy all ML files." appears ===== 
 +{{https://a1ex.magiclantern.fm/bleeding-edge/BigMac/err60D.jpg?260  }} 
 +Known bug with Big Sur (macOS 11.x) and flash memory cards with ExFAT file system. \\  
 +Workaround: Format card with FAT32 file system and proceed with installation as before: Copy extracted build files and directories to card, insert card to camera and use Canon Firmware Update option to install again. Error will not be seen this time.\\  
 +After installation and startup it is recommended to format card inside camera with "Keep ML" option. Camera will apply ExFAT file system again and ML will rewrite files and directories to card automatically. 
 + 
 +For details see [[ml>forum/index.php?topic=25656|Folders created by macOS Big Sur on exFAT cards are unreadable in Canon EOS cams]] 
 + 
 +===== Loading MLV_SND.MO failed "tcc: error: undefined symbol 'mlv_rec_[...]'" ===== 
 +{{wiki:mlv_snd_tcc_err.png?350  }}MLV_SND.mo requires MLV_REC.mo to run.\\  Make sure to have MLV_REC.mo activated, too.
  
 ====== Technical ====== ====== Technical ======
Line 319: Line 437:
 ===== What is it written in? Can I get the source? ===== ===== What is it written in? Can I get the 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 [[https://bitbucket.org/hudson/magic-lantern/|download the Magic Lantern firmware source code]].+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 [[https://foss.heptapod.net/magic-lantern/magic-lantern/|download the Magic Lantern firmware source code]].
  
 ===== How do I get a ROM0.bin firmware image? ===== ===== How do I get a ROM0.bin firmware image? =====
Line 330: Line 448:
  
 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. 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.
 +
 +====== ML Development ======
 +
 +===== The project is dead, right? =====
 +
 +Not dead yet!
 +
 +Here is some status update for all users (and devs). Warning, long read! Posted April 2023: \\ https://www.magiclantern.fm/forum/index.php?topic=26852.msg242979#msg242979
 +
 +Here is a dev/programmer oriented write-up about build concerns and stuff. Warning: Deep tech lingo! \\
 +https://www.magiclantern.fm/forum/index.php?topic=26814.msg245407#msg245407
 +More updates in linked thread.
 +
 +===== Can't you use ChatGPT (or other AI) to help developing/porting? =====
 +
 +Nope, won't work!
 +
 +ChatGPT's fame in programming is largely based on having access to vast amounts of freely distributed data and code (as in Stackoverflow) accumulated over years. \\ 
 +This doesn't apply to ML development. Canon never published its code or tools involved creating it. It is a very, very small community trying to make sense of what is found in camera (aka: reverse engineering). 
 +ChatGPT simply doesn't know what is going on.
 + 
  
 ====== Misc ====== ====== Misc ======
Line 336: Line 475:
  
 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. 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 ====== ====== Troll Questions ======
Line 388: Line 528:
 When we will get around to it. When we will get around to it.
  
-As surprising as it may seem, we actually have families and lives that involve things other then Magic Lantern. This is a hobby project, we enjoy working on it, and we enjoy seeing you using it. We don't particularly enjoy getting nagged about doing things.+As surprising as it may seem, we actually have families and lives that involve things other than Magic Lantern. This is a hobby project, we enjoy working on it, and we enjoy seeing you using it. We don't particularly enjoy getting nagged about doing things.
  
 -> [[https://snarky.ca/setting-expectations-for-open-source-participation/|Remember that people do free work because it is fun, not to get stressed by strangers!]] -> [[https://snarky.ca/setting-expectations-for-open-source-participation/|Remember that people do free work because it is fun, not to get stressed by strangers!]]
  
-===== How long it will take to port ML on camera XYZ? =====+===== Will ML ever be available for 999D? ===== 
 + 
 +(999D = any camera model not yet supported) 
 + 
 +If you start to learn C, Assembler and reverse engineering embedded devices with ARM architecture and are willing to put several hundred hours of work into it: Sure, there will be! 
 + 
 +===== How long it will take to have ML on 999D? =====
  
-Estimated: at least several hundred hours for the initial port, without including maintenance.+Estimated: at least several hundred hours for the initial port, without including maintenance or advanced features (such as raw video).
  
 In practice: In practice:
   * assuming a developer __were employed to work on this port full-time__: at least 2-3 months, without any guarantees of success.   * assuming a developer __were employed to work on this port full-time__: at least 2-3 months, without any guarantees of success.
   * assuming a developer __dedicates 20 minutes/day on average__ to this particular port: [[ml>forum/index.php?topic=19737.msg225763#msg225763|about 3 years]].   * assuming a developer __dedicates 20 minutes/day on average__ to this particular port: [[ml>forum/index.php?topic=19737.msg225763#msg225763|about 3 years]].
-  * if everybody waits for somebody else to complete the port:  [[ml>forum/index.php?topic=17695.msg207023#msg207023|code doesn't grow on trees]].+  * if everybody waits for somebody else to complete the port:  [[ml>forum/index.php?topic=17695.msg207023#msg207023|code doesn't grow on trees]]. Sun entering red giant phase, proton decay and such things... might actually happen first ;)
  
-===== Why camera model XYZ isn't supported yet? =====+===== Why camera model 999D isn't supported yet? =====
 ===== Why feature XYZ isn't implemented yet? ===== ===== Why feature XYZ isn't implemented yet? =====
 ===== Why bug XYZ isn't fixed yet? ===== ===== Why bug XYZ isn't fixed yet? =====
Line 431: Line 577:
 ===== When will you release the next *stable* version? ===== ===== When will you release the next *stable* version? =====
  
-As soon as **you** will provide us with clear and concise testing and bug reports for all ML features from the [[http://www.magiclantern.fm/forum/index.php?topic=3072|nightly builds]].+As soon as **you** will provide us with clear and concise testing and bug reports for all ML features from the [[ml>forum/index.php?topic=3072|nightly builds]].
  
 Since this did not happen for the past few years, and we no longer have the time and resources to do the testing ourselves, there are currently no plans for a new stable release. Since this did not happen for the past few years, and we no longer have the time and resources to do the testing ourselves, there are currently no plans for a new stable release.
  
 However, the nightly builds can now be considered somewhat stable, and if something important breaks, it's usually fixed quickly [[https://foss.heptapod.net/magic-lantern/magic-lantern/-/issues|if you report the issue]]. However, the nightly builds can now be considered somewhat stable, and if something important breaks, it's usually fixed quickly [[https://foss.heptapod.net/magic-lantern/magic-lantern/-/issues|if you report the issue]].
faq.1612890505.txt.gz · Last modified: 2021/02/09 18:08 by a1ex