Messages

That totally slipped my mind! I'm actually on a mac so I used Macboot and everything works as it should again

Thanks for the help, really appreciate it!
- Aviel

Hello,

I've had ML on my 5D Mark III since it was released and haven't really had any problems updating/installing until now. A couple weeks ago my SD wouldn't let me delete pictures off of it, so I went ahead and made a copy of the existing ML firmware on it, formatted the card then put ML back on it and that's where the problem started. Now when installing ML everything goes as it's supposed to, I get the "Enable Bootdisk Flag " message but then when I restart the camera it doesn't have Magic Lantern on it. I go into the menu and it just says firmware version 1.1.3. Yes I am using a card under 32gb, yes i am on 1.1.3, no I'm not installing while the CF is in, and yes the Battery is charged (tried multiple batteries)

This is what i've tried so far to solve the problem (as far as I can remember):
- 2 different SD's
- low level format the SD
- low level format the SD then just the regular format
- reinstalling 1.1.3 then trying
- installing 1.2.1 then 1.1.3 then trying
- installing in different modes (i.e. M, P, Av, Tv, C1, ect.)
- installing earlier raw builds
- installing alpha 3 then upgrading to early raw builds
- installing alpha 3 then upgrading to recent raw builds

Really hope someone has a fix for this and sorry if someone has already posted about this

Thanks in advance,
Aviel

Has anyone had any problems with random exposure changes using ML raw on the 5D3? The camera is set on fully manual and this doesn't happen using the standard H.264. I went through the ML menu trying to find out why I'm getting this but didn't see settings that seemed to apply to this. I started shooting a somewhat important video in raw a couple days ago only to discover this problem. I used the July 11th build and converted it in RAWMagic then imported it into After Effects. I tried using raw2dng but I'm getting the same results. Also I shot a video using the raw function in early June and only encountered this in 1 shot out of about 25, this time it's more extreme. Is there a fix for this? Are my settings or workflow off somewhere? Can I recover the footage or should I go ahead and re-shoot it? I can post a short sample as well if need be. Sorry if this question has already been addressed, I haven't come across this after reading quite a bit about ML raw in the past month or so.

Thanks,
Aviel

Hey guys, made a short edit testing out the raw video just to see how it compares to the usual H.264 workflow. I shot in pretty harsh lighting and purposely overexposed a few shots to see how far it could be pushed in post. This was shot in roughly 1-2 hours with a 5D Mark III, Rokinon 14mm t/3.1 Cine, Nikkor 50mm f/1.8 AI-S, & Nikkor 135mm f/2.8 AI-S. I used a KomputerBay 64gb 1000x card and was getting around 88 mb/s out of it (only ran the short benchmarks). Footage was color corrected in ACR, and graded in AE using filmconvert, curves, and sharpen (at 20). Overall it worked very well with only a few minor problems which is awesome considering it's free and not yet a final version. Oh and I used the June 2nd build

***Make sure to download through vimeo to get the best possible quality***

Unfortunately I can't get 24p working in full 1920x1080 mode on my 1000x Transcend 64gb. I posted some benchmarks in the other thread. If I read the already posted chart correctly the 32gb transcend seems to be faster. In 1920x1080 I have about 1 frame skipped every 1-2 seconds Just a tad too slow

Have you tried turning on Hak3d in the raw menu?