Messages

Notice hot pixels flaring on her zipper below the pendant at ~1:03.

You're right... I'm seeing them too now. Not just in that one clip, but others too. Is this happening with anyone else's footage?

I just tested this on the Mark III, and it seems to make a difference in my May 22nd build. I've never really past 70MB/sec peak on my 128GB Komputerbay (in actual recording) but now I'm seeing 72.5 MB/sec sustained in a test clip. CF card workaround on, global draw off, ex-Fat formatted card.

This was posted in the "Raw video on 5DMK2" thread, but I thought it was well worth mentioning in case it hasn't been seen by all.

If you have RAW selected as your photo type and record, say you get 100 frames at any given resolution and fps.

If you then change your photo settings to disable RAW and shoot only Small JPG, you'll get MANY more frames of RAW video.

It seems like there was 2-3 more *'s worth of buffer when I did this.

Benchmarks are the same, so it appears it just opens up some more buffer room.

In my tests, I went from 150-170 frames to 290 just like that!

My latest! Comparing H264 Technicolor Cinestyle to ML Raw. Highlight recovery, curves tweaked slightly in Adobe Camera Raw. No other correction applied, and no post sharpening applied. Didn't touch cinestyle H264 footage at all because frankly, it's no longer pleasurable to tweak compressed footage. Camera settings were identical for each set of shots.

Shot on May 22nd build, on 128GB Komputerbay 1000x.

My write speeds have gotten slower with the May 22nd. I can no longer hit 70MB peak at all and struggle to maintain 64MB/sec needed for 1920 x 840. Most clips have at least one dropped frame. I use CF workaround which seems to help. Global draw fully off.

Vimeo is set to 1080p, so please give it a second to load and then hit fullscreen. The parrot shots and the clocktower shots are my favorites in terms of showing off the power of the extended DR and color corrective capabilities.

Need a hand. I tried to go back to an earlier build and loaded the older files on to the CF card.

When I booted up the camera with this older build, ML did not run. Strange. So I tried to update firmware again. Partway through the process it appeared frozen at the 'boot flag enabled' message. I had to take the battery out.

Upon restart, ML does not run at all, no matter which build I have on my CF card. Also, when I try to update the firmware, it says no firmware update found and I have to pop out the battery.

Edit: Went and loaded the Mk3 alpha... then went back to the development May 17 build and it's back to normal. Leaving this one here in case someone else encounters this.

Ok, my new test clip which aren't of plants or dogs!

Every now and then I need to remove the battery and put back in before the camera will start (after re-inserting the card after offload). Using Lorenco's May 17 build. Otherwise, everything is working great.

I'm struggling to even complete files in 1920 x 840.

I wonder if I can format the card in a different way... perhaps it's writing blocks fragmented. Is formatting using EOScard or Macbook sufficient?

I get similar speed results as you with my 128.  I have written about this issue here and on Cinema5D.  Bottom line, the KomputerBay 128s seem to be slower then the 64s.  Cinema5D has assured me that their 128s are fast so they just might have been lucky with theirs.  EOSHD was using 64s for his tests.  Most current reports of the 128s are benchmarking around 70MB/s.

My 1000x Komputerbay 128GB arrived today. Just as I had expected, it is quite slow. Topping out at 70MB/s... so I'm stuck with 1920 x 900 on a good take and most often 1920 x 840 to be safe. This is a slow 1000x card. I'm not sure how others like Cinema5D are writing 1920x1080 to the 128GBs.

Still waiting for my Komputerbay 1000x cards to arrive, but couldn't resist testing on my Kingston 266x 32GB CFs. These only get just under 30MB/sec, leaving me with a 1280 x 540 crop. Even at this low res, the image is very good and extremely easy to work with. Loving the photo-esque flexibility in post, it is really something.

Cinema5D's photoshop/ quicktime workflow is the one to use. It's blazing fast and if using Premiere, you can even skip the quicktime to prores step. Just import the TIFF files as an image sequence, interpret as 23.98 and away you go.
This one here: http://vimeo.com/66355682

Another crappy plant video below to add to the mix. I'll shoot an actual project with it this weekend, once I get my hands on the Komputerbay 1000x cards. Hopefully it won't be as slow as reported by others here.

Big thanks to Lourenco for continuing to compile latest builds for us. This is SUCH a huge help and we really appreciate it.

I'm using the build he provided in post 1075 here:
http://www.magiclantern.fm/forum/index.php?topic=5247.msg36099#msg36099