Messages

Do you use this setting or not?

Expo -> Dual ISO -> Alternate frames only

Workaround:
1) Add more strobes.
2) Add more powerful strobes.
3) Add more power to your strobes = External power pack. Can and will fry plastic parts if overdone.

Nightly Builds only.
Rest of a) and b) is answered in first post of this thread or FAQ/User Guide.
Remark to b): There will be a delay (<2 sec) during camera startup and wake from powersave mode even if a card is not enabled to run ML.

Number of bricked 7Ds by nightly builds (outside devs dungeon) = Zero (known to me).
And of course there is a chance because it is absolutely impossible to exclude such failures.

The thread starters problem is/was:
- Use a blank card or none: Cam will not start
- Use a bootable ML card: Cam will start

You have exactly the same problem?

And I would think twice about not saving your RAW files. Over time I saw various enhancements in RAW converters and add-ons. After driving some older RAWs through my workflow again I sometimes was glad having taken the effort a second time. Not always, of course!
I found a link:
http://www.pentaxforums.com/reviews/linux-for-photography/introduction.html

PSE has WINE rating "silver" so it may run in Linux
https://appdb.winehq.org/appview.php?appId=1794

As time of writing 1.1.4 is not supported.
Downgrade to 1.1.3 and proceed as adviced in
http://www.magiclantern.fm/forum/index.php?topic=3904.0

Sorry, but the argument about time wasted jumping over tabs sounds not that convincing.
And space? Please get real and check the space wasted by ML features you don't use.

ML is widely known for it's video features and - I give you that - is not that well known to be a treat for still shooters. But - IMO - splitting ML into two versions for stills and video will cause more confusion and that's quite the opposite of your intentions.

Suggestion: Test customized menu option.

PS: I consider myself to be a stills shooter. Macro and architecture/landscape most of the time.

Thanks for your input. I don't own a 550D.
I think it's about time for a second 550D user to jump in if your problems are reproducable.

Just to make sure: You recorded in Canon's H.264 (MOV) at the time the error occured?

Which modules loaded?

Updated ML by "Copied new version over old version"? Or update as in "Deleted AUTOEXEC.BIN and ML directory and copied extracted nightly contents"?
If first, try second and report results.

No.
Top of page -> Downloads
Depends.

http://www.magiclantern.fm/forum/index.php?topic=11017.msg130897#msg130897

First step to get a usable cam ...

Format card using a cardreader.

Please tell the whole story ...

Thanks for the correction!

"RAW error" is an indication for overwriting ML files instead of clean install. Config files will be written to card by previous installations, causing ML to mess up.

Backup card's ML folder, delete folder + AUTOEXEC.BIN from card and copy extracted nightly build contents to card.
You will loose all settings. Now try again. RAW error should be gone now.

Take a look here: http://www.magiclantern.fm/forum/index.php?topic=5705.0

5th batch is in and running far better than 4/3.
10 minutes to go.

Walter nice to see you turning believer 

Nah! For instance I don't believe history will be changed if 175.000 are rolling in. Neither believing it would be if numbers 174.999 or 175.001.
100.000 has potential but only history will tell. With hindsight.

Option to change sensor of 43s batch is given officially in comments. So 2 hours left to join the party and break the 170k

If this batch is going to hit big time (well beyond 170k) I might begin to believe people actually can read.

I stand corrected!
Sebastian, ready for a 5th?

What you want to do now?
- Stay with Canon's firmware 2.0.5 and get rid of ML?
- Stay with ML and get rid of Canon's firmware 2.0.5?