Canon does not make their own software for what you are trying to do. While we are unable to recommend anything specific that will work best for you, most professional or even consumer level video editing applications can work with the video from the EOS 5D Mark II and EOS 5D Mark III and burn video to a DVD. Firmware changes to EOS 5D Mark III Firmware Version 1.3.4. Firmware Version 1.3.4 incorporates the following fix: Corrects a phenomenon in which when using the camera with the EF 70-300mm f/4-5.6 IS II USM lens, even if lens aberration correction is set to “Enable”, correction will not be applied. Supported Models: EOS R, EOS 5D Mark IV OS: Windows 10 64bit (Version 1607 or later), Windows 8.1 64bit, Windows 7 64bit - The recommended system requirements for image display in HDR PQ are as follows. CPU: Core i-series 3.4GHz or higher RAM: 4.0 GB or more of RAM (8.0 GB or more recommended).
Main Builds » 5D Mark III 1.2.3
Latest Build (2018-07-03 00:12)
Test results: 7 passed, 0 failed
This build was tested, to a limited extent, in QEMU (a virtual machine modified to run Canon firmware). Please take the results with a grain of salt - this is not the same as running on a physical camera.
94442d9: features.tmpl edited online with Bitbucket: use id in th section heading to allow for direct linking via anchor
5e40987: Merged in edmac (pull request #886)u000au000aEDMAC module: fixes for DIGIC 4, connection map
b54a0c6: Merged in adv_int (pull request #907)u000au000aAdvanced intervalometer updates
58e11ee: Merged in memory-backend (pull request #906)u000au000aMemory backend improvements
87dfe3c: Makefile: fix 'make install_qemu CONFIG_QEMU=y' for minimal targets
7c04c75: memset64/memcpy64: use versions from b831cb1; fix calls from Magic Zoom to ensure proper alignment
375fa4e: Backout b831cb1 (breaks Magic Zoom and CONFIG_MARK_UNUSED_MEMORY_AT_STARTUP, as memset64 is not the same as memset)
287c785: adv_int: ignore empty lines when loading keyframes
6239bc6: adv_int: use strstr instead of my_strstr (fixes slow load)
284656a: Include strstr in ML core
ef21d82: adv_int: refactor keyframe time formatting
5ca412b: adv_int: auto-load the saved sequence at startup
a4869c8: adv_int: renamed menu entry to 'Ramping options'
86accb6: Memory backend: drop timestamps from history; show last 1024 events
d016ccf: Memory backend: show total allocations (number and amount), including untracked ones
0e56fe7: Memory backend: allow using shoot_malloc as a last resort, even for small blocks;u000aallow small blocks (smaller than minimum_free_space / 64) to break the minimum_free_space limit (until minimum_free_space / 4)u000afine-tuned until the old set of Lua scripts were able to run on 1100D without umm_malloc
28bf259: Memory backend: a pointer to task names (rather than copying the full string) should be enough
a67b3ed: Memory backend: renamed memcheck_mallocbuf to memcheck_entries
b831cb1: Moved memset64 and memcpy64 to bench.mou000a- simplified to accept only 32-bit aligned pointersu000a- using regular memset for Magic Zoomu000a- closing issue #1995
d7866ee: Memory backend: if shoot_malloc fails, try SRM nextu000a(poor man's autodetection, since we don't know how to query the available size in advance)
ee7abdb: exmem: reworked shoot_malloc to handle large requests betteru000a- moved autodetection to dedicated functions (for both fragmented and continuous allocations)u000a- autodetect the max available size for large requests (slower, but when it fails, it fails gracefully)
bd7a1dd: exmem: removed the 'relaxed' checks introduced in 04f02a4u000a(not sure why they were needed; we'll find out if it fails)
766ffbb: exmem: speed-up shoot_mallocu000a(1s timeout probably not needed)
51f6129: exmem: do not keep track of full shoot memory allocationsu000a(allows reserving some memory in advance and allocating all the remaining RAM afterwards)
f12eba5: Memory backend: fix handling of untracked blocksu000a(possible buffer overflow before this fix)
f9f3358: Memory backend: figured out why AllocateContinuousMemoryResource may crash with many small blocksu000au000a(todo: figure out where to keep 89e3b12 or not; adapt tests if not)
e4fd29d: Memory backend: when checking available memory, allocate both Shoot ans SRM at the same timeu000a(they may overlap)
1162fce: Memory backend: fix initialization
67f582f: mem.c: option to disable heap poisoningu000a(useful when running in QEMU with -d memcheck - with this, overflowing reads will be caught as well)
26f1647: Memory backend: allow breaking minimum_free_space for small blocksu000a(it was possible to fail the allocation for very small blocks that could not be covered by shoot_malloc)
c6d6699: Memory backend: allow AllocateMemory as a last resort, even if free space is below limitu000a(it was possible to fail the allocation for very small blocks that could not be covered by shoot_malloc)
1e4985e: memory backend: reduce memcheck area (should reduce overhead a bit)
4e59a74: memory backend: ignore null pointers passed to free (Lua does that)
2ade4a5: exmem: when autodetecting available memory, print all srm/shoot memory blocks to console
fee1ee2: edmac: make sure the log files don't have unnecessary newlinesu000a(channels with complex size configuration may get printed on multiple lines; that makes the log file harder to parse)
1508a54: edmac: LOG_INTERVAL can now be changed from menu (persistent setting)
564b0c5: edmac: use numbered log file names
edcb52f: edmac: fix behavior when the extra info buffer gets full
056e56e: edmac: use half-shutter as trigger for logging EDMAC channels;u000afine-tuned messages
2eddc9f: edmac: fix crash on models other than 5D3u000a(there was a hardcoded stub)
4b161ce: edmac: fix crash when using 'Log EDMAC usage' on D4 models
bc3bd0d: Merged unified into edmac
b4a8fad: Added edmac.mo to nightly builds
2061922: edmac-memcpy: check to make sure all models have AbortEDmacu000a(to make sure it's correct: selftest.mo -> Stubs API test)
u000du000au000du000aFirmware 1.2.3 is required if need any of those features from Canon:u000du000a
u000du000a
clean HDMI out
u000du000a
dual monitor support (internal+external)
u000du000a
AF at f/8 with teleconverters
u000du000a
u000du000au000du000a
If you don't need anything from the above list, please consider downgrading to 1.1.3.
u000du000au000du000a
Canon 5d Mark Ii Eos Utility Software Mac
A few ML features are not compatible with 1.2.3 (see the Features tab and the 1.1.3 forum thread).u000du000a If you need any of these features, you will have to downgrade to 1.1.3.u000du000au000du000a
Recommended card setup
u000du000au000du000a
u000du000a
install Magic Lantern to an SD card
u000du000a
use CF card(s) for taking pictures or recording videos
u000du000a
u000du000au000du000aHowever, any card configuration may be used.u000du000au000du000a
Installation
Make sure you are running Canon firmware 1.2.3. If you are running 1.3.3, 1.3.4 or 1.3.5, you can downgrade with EOS Utility (instructions). Downgrading from 1.3.6 is possible, but tricky.
Whatever you do, do not remove the battery in the middle of a firmware update!
Method B (recommended, one single card required, either SD or CF, source, discussion):
copy firmware 1.3.6 (5D300136.FIR) to the card
launch Update Firmware from Canon menu, click OK
open the battery door ASAP, but don't remove the battery!
if you did it right, the camera will turn off (wait for a few seconds to make sure it's really off)
if you see the Firmware Update Program Loading screen, it means you have opened the battery door a bit too late; wait until the camera turns off and try again!
open the card door and remove the card from the camera (do not close the battery door; also leave the power switch on; the camera should stay off)
copy firmware 1.2.3 (5D300123.FIR) to the card
put the card back into the camera, close the card door
you may leave the original 1.3.6 FIR on the card, or you may delete it; doesn't matter
close the battery door; you should see the Firmware Update Program Loading screen
if you get an error message at this step, remove the battery and reboot
confirm the firmware downgrade from 1.3.6 to 1.2.3
a successful downgrade should take about 4 minutes.
Method A (not recommended, two SD cards required, not CF, source, video tutorial):
prepare two SD cards:
one with firmware 1.3.6 (5D300136.FIR)
one with firmware 1.2.3 (5D300123.FIR)
insert the 1.3.6 SD card in the camera
launch Update Firmware from Canon menu, click OK
you should see the Firmware Update Program Loading screen
wait until the card LED goes off
swap the cards quickly (you have about 10 seconds to perform this trick)
confirm the firmware downgrade from 1.3.6 to 1.2.3
if the camera reboots into 1.3.6 after downgrading, please try the other method (details)
note: CF cards are not recommended for this procedure, as they are accessed by Canon bootloader without LED activity, so you won't know when to swap them.
Once you have the correct Canon firmware:
Format the card from the camera.
Unzip the archive and copy ML files to the memory card.
Run the Firmware Update process from Canon menu.
This procedure will enable the BOOTDISK flag in your camera's Flash ROM, allowing it to load and execute custom code from the memory card. A copy of the original (unmodified) ROM contents will be saved to the card.
Magic Lantern will run from this card; it won't replace your original firmware.
After installation, please copy your ROM backup files (ML/LOGS/ROM*.BIN on the card) to a safe place.
Detailed instructions on the wiki. Please don't forget to check the FAQ and the user guide.
Canon 5d Mark Iii Software Download
Uninstallation
From camera:
Run Firmware Update from your ML card.
Follow the on-screen instructions, including the fine print.
This procedure disables the BOOTDISK flag. You will no longer be able to run Magic Lantern, unless you reinstall it.
Some settings changed by Magic Lantern might be persistent; this procedure will not reset them. To restore the camera to factory state, you may also want to clear all camera settings and custom functions from Canon menu.
From one card:
Canon menu: Format card, remove Magic Lantern.
This procedure does not disable the BOOTDISK flag. With this method, you will still be able to run Magic Lantern from other cards.
Never delete the Magic Lantern files from the card! Format the card instead.
Troubleshooting
Camera doesn't boot?
Remove battery, remove card.
Put battery back, close card and battery covers.
Start the camera without card.
» Did it work? Format the card, reinstall Magic Lantern.
» Still not working? Double-check battery and card doors, run the diagnostic tools and get in touch with us.
Canon Eos 5d Mark Iii Software Download Mac
Troubleshooting tips
Canon 5d Mark Iii Price
If your camera locks up, remove the battery and reboot.
Make sure you have a backup card without Magic Lantern on it (just in case).
To restore ML defaults: Prefs → Config files.
To see what settings you have changed from ML defaults: Modified (Δ) menu.
To disable Magic Lantern temporarily: press and hold SET at startup.
Useful Links
Warning! Magic Lantern is not approved nor endorsed by Canon in any way, and using it will probably void your warranty. We are not responsible for any damages to your camera.
Copyright (C) 2009-2018 Magic Lantern Development Team
This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 2 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.