Messages

1920 width is technically not possible with 5D2. Thats according to A1ex when he looked at actual res beoing pulled out of the 5d2 sensor.

This he has mentioned "several" times already.

yeah my bad, realized that 1920x1080p was being upscaled.

getting 66mb/s with manual LCD brightness.
64mb/s with LCD brightness set to auto.
about a 2mb/s boost.

june 27 build
transcend 600x
small hacks-on

"ps-do we still have to put the camera mode on C1/C2/C3 mode for more buffer?"

Correct me if I'm wrong, but I think the perceived effect of the C modes was down to photo settings and switching them down.

so at this point, C-modes have no bearing on buffer space.

The new hack option puts my 600x Sandisk 16GB card just into continuous levels at 1880x854! Write speed seemed to stick around 64.7 MB/s. Gonna inspect the frames to see if I get anything like ted ramasola is seeing. I'll also have to account for the fact that I left the unofficial 1880 option on as well...

edit: It was probably a bad idea to record my LCD screen for this test due to the moire lol. I don't see anything wrong, but I'll test it again later.

Whoa, I pushed the res a little higher to see where the write speeds will top off and it seems to be at around 67.5 MB/s @ 1880x940 24.000 FPS. It started off at 68.5 MB/s for a good 10 seconds or so, but dropped. We've come a long way since the early days where I couldn't get more than 53 MB/s.

im getting the same results here.
im on a transcend 600x 16gb.
continuous recording at 1872x796.
peaking at 68mb/s and averaging around 64mb/s.

well done gentlemen

ps-do we still have to put the camera mode on C1/C2/C3 mode for more buffer?

im sticking to h.264 for commercial work, the workflow is a pain to deal with.
but i did convince the producer i work with to do our next series of films to shoot with ML raw.
although, im dreading the fact im going to be processing a lot of files

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.

absolutely wonderful news.

Success ! i recorded 5145 Frames @1880x854 24p 13.6 GB (14,656,130,312 bytes)
Joined the 3 segmented 3.99 GB (4,294,967,295 bytes)=9.46 GB (10,163,543,257 bytes
Join A File  with B file 3.99 GB (4,294,967,295 bytes)=13.6 GB

Drop on the new raw2dng.exe & everything look Great no more Pink Noise Frame
I still need to do a Full Card Record which is a Lexar 1000x 32GB
to see if there is any frame corruption, that when i had all my problems

i use the May 31st Bulit with the new raw2dng.exe
it looks like there maybe a little Speed increase, i was recording @ 64.2 MB/s
with only 1 Buffer Star   no frame drops.
As long as i have no problem with a full Card record i Have plans to
completely  Film in RAW a 60 Mintue  Documentry about  a Young Street Artist in Central Alberta.
i should get about 8 Mintue per 32 GB card @ 1880x854 24p 

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?

there's no way to get around the 4gb limit?
so that means getting 5dm3. 

You don't have to leave it on Protune. Protune set as the output curve will give you a "finished" look. When working in 10-bit and 12-bit, especially for color grading, cineon (logarithmic gamma curve), compresses the all of the data into a range where each stop of light in the file gets around the same number of code words (bits of data for detail). This is why film is scanned to cineon log files. The entire dynamic range of the film frame can be captured and stored in the log file. Same principle applies to raw. That's why ARRI, Red, Sony, Blackmagic Design, etc. have there own versions of cineon log designed specifically for the sensors of their cameras. If you compare Alexa Log-C, RedLogFilm, and BMD Film (I actually did a post on BMCUser about using Cineon 95-685 to get extremely close to this curve with CF) , you'll see that they are all fairly similar looking with differences mainly in color science. With Cineform we can take a raw file and basically transform it to a mathematically correct cineon file, Log-C file, S-Log, or whichever curve you choose file. However, when compositing or editing, I'd work with the Protune output curve so you don't have to create proxies and you can stay with the CF raw file until you actually have to render an intermediate composite or something like that.

For up-converting the 8-bit to 10-bit, it depends largely on which profile you shot with. If you used Cinestyle, there is a preset in CF Studio to set the i/o curve to CStyle. For any other profile I'd say leave it at Video Gamma because in the H.264 file there's only about 6-8 stops of usable dynamic range depending on the ISO setting you shot with.

very useful information. thanks!
so basically if you're shooting raw, use cineon.
if you're upconverting, leave it at video gamma.
as for picture styles, i've been using visioncolor and lightform

Cineform Raw is 12-bit log, which means it can store the same amount of data as 16-bit linear, more than the 14-bit linear that comes from the Canon DSLR sensors. Cineform doesn't need a highlight recovery slider because it automatically restores all the highlights contained in the raw file. For proof look at the default ACR settings vs Protune with no lut. Or set the output curve to Cineon 95-685 or Custom Log 400 to gain back all dynamic range from the file.

i've read to leave it to protunes.
what are the pros cons on protunes vs cineon?
coming from 8-bit to 10bit?

So after entering all of those values and finally getting that clip set up properly, is there a way to apply those settings across a set of imported clips?

in the "step 2" or "EDIT" panel. load the clip you want to copy the settings from as well as all the clips you want to paste the settings to.
first you select the source clip and selecting "Copy" or "ctrl + C" from the Edit menu and then selecting your destination clips and selecting "Paste" or  "ctrl + v"

nice. that hack3d 3d option seems to give me more framerates.
managed to reached 1785 frames on a transcend 600x 16gb on 1888x720

it still bugs me i mananged to reach the 4gb limit a few times with an earlier build though. 

Can you tell me please: if i render my DNG file in After Effects to cineform 4-4-4 : it will be raw? or just compressed 12 bit 4-4-4?

i dont know what you mean by raw, but cineform is a losssless (visually lossless) codec.
the only difference is that you'll be working on a 12-bit color space vs 14-bit.
the converted file will be cineform raw.
any changes you make with your footage will be done on cineform studio premium and the beautiful thing is that the meta data is imbedded within the file itself so you can reset or change the meta data within CFSP and the changes will be immediate in video editing program.

Press the LiveView-Button on your DSLR.
Go to the ML-Menu Debug->Benchmarks->Card R/W benchmark

here you go. used both of my transcend 16gb 600x
so if im reading this right, my cards can't get past 56mb/s yet i've managed to reach the 4gb limit a few times.
strange right? maybe just a fluke on my end.

i've been using cineform studio premium for several weeks now for a short film we've been working on.
converting 5d mark ii h264 to 10-bit cineform. its great that it gives me much better flexibility in doing aggressive color grading.
and loving the white balance picker. saving me tons of time.

but downsampling from raw to 10-bit cineform isn't as good as raw to dng sequence using after effects.
ACR has a much better control than cineform. and i dont think cineform even has highlight recovery slider.
cineform is great for upconverting from 8-bit to 10-bit color space though.
just my two cents.

@pholler
forgive my stupidity. but can you show me how?
im curious see that too actually.
i'll post results after lunch.

Did you deactivate Global Draw?

yeah, global draw was off.

hi ladies and gents.
first time poster here.
loving and appreciating shooting raw.
my utmost gratitude to you guys.
now that's out of the way.

i was using an earlier build (last weekend perhaps?) and i managed to reach the 4gb limit on my transcend 600x card several times.
shooting at 1880x840

now with the may 16/17th build, i can't even reach 200 frames without frame skipping even if i shoot at 720.
i dont know if its the card or different build, but something to consider.
i honestly couldn't tell you which earlier build i used.