Messages

If you  can't see them it doesn't mean they are not there ...
http://lumenatic.com/2011/08/17/hotpixel-removal-in-lightroom/

Canon H.264 uses quite some noise reduction and some sharpening and some upscaling and some softening and because of it's soft/mashy output Canon has been dissed quite often.
You're comparing incomparable things: RAW without that much image manipulation and a heavily manipulated one.
If you're happier with H.264 ...

Top of page -> Downloads -> Nightly builds
Erase autoexec.bin, ML directory and FIR from card and copy extracted nightly contents to card.

And be warned: 550D is limited to about 21 MByte/s in recording mode and that doesn't give you that much options for resolution/frame rate.

Sure, MLV_SND.mo relies on MLV_REC.mo which is missing on your list.

That'll let me speed up my intervalometer a bit and hopefully produce better ETTR results.

I might be genuinely surprised if there will be a difference at all, apart from an EXIF value.

High-ISO noise reduction will only be used in post-processing by tools actually reading Canon-specific MakerNotes section in EXIF. Put Canon DPP aside and this setting is just ignored.
Noise reduction on long exposure however will record a darkframe for each pic meeting requirement.

With your 64GB SD cards you're using in the 5DIII that are in exFAT (as formatted by the camera itself), can I ask how you installed ML on them?

If I remember correctly, for my 6D I just copied the ML files (a nightly build) on the card, threw them in the camera and did the firmware update to install ML.

Same for 5D3.

This probably sounds incredibly irresponsible or careless of me, but I read other instructions that say you must enable the card to be bootable first.

Which will be done by running Canon's firmware update procedure when using a card with ML files on it. Exception: 550D/600D

No, I think it's something which may have to be taken care of.
@devs: Is it possible to dissable powersave during this operation?

@whitep: Installation Guide + https://builds.magiclantern.fm/#/features

Seems like card got unbootable. This shouldn't happen. Run firmware update from Canon's menu.
Try to reproduce.
If able shoot a video about your issue. Quality doesn't matter here. And add some details about the card you used: Size, file system used and of course which nighty build version.

Using Canon's H.264 implementation for video recording requires about 6 MByte/s data write rate (without CBR tweaking, of course). Try another card. Any real Class-10 card should do.
Have you checked file sizes generated?

Sorry, your description is incomprehensible. Please add description in your native language.

Format card using cardreader and redo installation.

But just to make clear the Canon Firmware Update should be on a non ML SD Card right?

Nope. Canon firmware doesn't affect bootflag and there is no timeout updating Canon's native firmware.

a) To get it on every SD card I have to do the install procedure for every card
(put ML Files on SD, plug into 700D, start FW Update)?

Installation Guide.

b) On my PC I just copy and paste/overwrite the 'new content' AND do the install
procedure (FW Update on EOS)?

Sorry, no idea what you're trying to do in b).

C: Uninstall cameras bootflag by running firmware upgrade. After timeout restart your cam and format card.

At time of writing I haven't heard about adapters supporting UHS-II. And I haven't heard of adapters supporting UDMA-7.
Do a web search: There is simply no adapter worth a second look. Shitty performance and compatibility is on the same level.

Top of page -> Downloads -> Nightly Builds -> 6D.113 and read instructions.

Shortcut: Prefs tab -> Customize Menus

Thanks, a1ex, for correction!

Setup in mind:
----
Timer for AC adapter, cam switched to ON. Timer will startup cam. ML + modules will run (Debug tab -> Modules debug -> Load modules after crash ON). Loading script
- Wait short time
- Start movie recording
- After 20 seconds stop movie recording

Wait some minute and timer will cut power.

----
Any errors within this concept?

Tried to find another solution but failed. Problem with 5D2 is - as dmilligan pointed out - you have to enable Liveview in movie mode. There are cams not having this problem. 7D for instance has a movie mode switch and with switch set will startup in movie mode.

You tried Auto-ETTR to solve exposure problem using stills?

Top of page -> User Guide -> FAQ -> Troll Questions -> Last entries

If your recording exceeds 4 GByte and are using default file handling you get *one* MLV and subsequently M00, M01, M02, and so on.
All tools available for cDGN should be able to use them by just selecting MLV.
If unable to handle them there should be a small advice how to merge them.

First read first post in http://magiclantern.fm/forum/index.php?topic=7139.0
Using Magic Lantern -> Post-processing Workflow -> HDR and Dual-ISO Postprocessing
Newest compiled cr2hdr: https://bitbucket.org/kichetof/lr_cr2hdr/get/cr2hdr_unify.zip
You will find all executables needed in subdirectory "bin".

Please: Try using search next time.

If using MLVRawViewer: The number of processed files was 115 or a number nearby? And number was constant every time you tried?
If so: Move files to a subdirectory just below root and don't use blanks in naming! And keep it short. C:\workdir will be fine and drive doesn't matter (if sufficient free space). Retry.

Please check Debug tab -> Shutter Count.
The numbers you are showing are telling how much pics have been taken after battery was loaded last time (AFAIK).

No, it is not normal and should definitely not happen at all.
Please post a screenshot showing shutter count status.
And by "flashing firmware" you meant "firmware update" using ML?