Messages

-It does shut down cleanly. What happens exactly is after 30 seconds or so the mirror clicks back into place and all the screens shut off and there is a flashing empty battery icon in the bottom right hand corner of the display on the top of the camera. Turning the on-off switch to off causes the red LED light to flicker a bit, so I'm guessing this is ML shutting itself down cleanly

-formatting the card did not help

-restoring settings did not help

-switching it to global draw off did not help, putting it into photo mode seems to fix the problem, but as a video shooter that obviously doesn't help me much, if I switch to video mode from photo mode it flashes Err on the top screen and the remaining images count says 20. I had to take the battery adapter out to get it to boot up again.

-the battery indicator in ML's overlays says 100%, the screen on the top of the camera says empty

-forgive me I've used ML for years but I'm not sure how to compile.

Interesting. I've checked a few of my genuine Canon batteries and they all say 7.2, truth be told I haven't bought new batteries in a few years. I guess I'll try upping the voltage, the camera does say DC 8.0v on it, I'm just really afraid of frying it.

EDIT: Well I went up to 8.0v and that didn't seem to solve it. I also tried disabling the image stabilizer on the lens and that didn't help either. I don't really dare go higher than the voltage on the camera. I definitely can't afford to fry it. Any other thoughts?

I just took delivery of an Omnicharge 20 from their indiegogo campaign. It comes with a DC out port on the side which has a user-dialed variable voltage. I set it to 7.2v as the LP-E6s are listed as (this is actually a preprogrammed preset on the device), and used an LP-E6 to DC port adapter I've had and been using with great success for a while now when connected to a V-lock plate.

For some reason it seems that Magic Lantern is causing the camera to shut down after less than a minute when connected this way. It does not shut down when I have the ML SD card removed from the camera, and it runs my wife's 60D without ML fine as well. I have had no problem using the LP-E6 adapter with my V-locks, and recent testing reveals this to still be the case.

Is there a power setting somewhere in ML that's causing this? I can't seem to find anything on this topic anywhere online. Thanks!

That's about as sharp as this shot gets. Like I said, it's the worst of it, but it's definitely a major problem throughout.

I have a 5Dmk3 that I have used ML on since I got it and always loved it.  I finally installed it on a 60D an office I work for had.  I haven't checked if my 5D has it, but under image fine-tuning there is a feature called noise reduction.  I don't remember enabling it, but perhaps the firmware defaults to on.  Either way, the operator they hired shot a whole event with it and looking at the footage it all looks a bit blurry, but in a weird digital way.  I found the noise reduction had been turned on. 

I'm sure this data is baked in, but is there any way to undo the damage?  Any suggestions would be helpful.  This is definitely not a feature I will be using in the future.

Thanks

example (not all the footage is this bad off but the weird crunchy edges are in everything):

I have been wondering about this myself for a while now.  Have you heard anything?

The elapsed time REC indicator is a function I used to use all the time and it seems to have disappeared from the nightly builds for the 5D3 since the UI change.  I really enjoy the UI change, especially the ability to choose between ft and m for the focus distance, but I really need the elapsed time indicator.  Have I just done something wrong in setting up ML or is it just gone?  I tried to be patient assuming someone would bring it back, but it's been months now and still nothing.  Any news? 

wait, i've been away on a production shoot. what did i miss about stitching consecutive files together?
how is it done? i  dont have to buy a mark iii now to record past 4gb?

The most recent build starts a new clip once the 4gb limit has been reached.  You can use terminal or command prompt to stitch them together.  On mac open a terminal window in the folder you have the clips, enter the following

cat [file1name].RAW [file2name].R00> [newfilename].RAW

hit enter.  The file will take a bit of time to compile, so don't try to convert it or move it until it shows the right file size.

Don't have a PC but I've seen comments on that process around as well.

Hey guys,

So I tried the latest raw2dng for MAC and it won't open any files, not even of a few seconds.  This is the "error" I'm getting.

raw2dng converter GUI for 5D2
Beta ver.0.3
/script: line 10:   506 Segmentation fault: 11  raw2dng "$fldr$name".RAW


All it does is it creates a folder in my desktop with the name of the RAW file and does nothing else.

I had this same problem with the file from bitbucket, I went to the forum page for the GUI and downloaded the current version there.  That seems to work fine.

I have no problems with smaller files but I am unable to get some combined files for videos over 4gb to read in raw2dng, it comes back with the "This ain't a lv_rec RAW file" error. 

video specs are below:

5d2
5/31 build d6786d675069
transcend 400x 32gb
Global draw on
1320x562
file 1: M31-1319.RAW - 4.294.967.295 bytes
file 2: M31-1319.R00 - 2.255.851.017 bytes
combined file - 6.550.818.312 bytes

I have seen elsewhere people having problems with certain aspect ratios, so I tried 1280x544 and was able to get raw2dng to recognize it.  I haven't tried any higher aspect ratios as these are the only cards I have.