jmac698
9th January 2011, 13:07
This just blew me away - a quick guess and it worked!
Here's how to read v210 mov files with rawreader (sashimi):
fn="G:\project001a\deepcolor\v210.mov"
RawReader (fn, format="y8", width=5120, height=1080, numframes=0, filehead=21192, framehead=0)
In this case, my file is 1920x1080. Each 5120 bytes represents one row. A group of 6 pixels is stored in 4 bytes. 6 Y samples with 3 each of (cb, cr). There's 2 extra bits per byte, btw.
You can easily see an outline of your picture and step through the frames to see motion, even in encoded form, some of the luma looks like picture.
Some work with masktools and this can be decoded completely in script.
My file had no audio, so how do you guess the filehead for your file? It's easy, for HD just use 5120x1080 size per frame, multiply by number of frames, and whatever is leftover is all header! Example, my sample had 3 frames, 16588800, filesize was 16609992, so 16609992-16588800=21192. This was from a Blackmagic declink capture.
Here's how to read v210 mov files with rawreader (sashimi):
fn="G:\project001a\deepcolor\v210.mov"
RawReader (fn, format="y8", width=5120, height=1080, numframes=0, filehead=21192, framehead=0)
In this case, my file is 1920x1080. Each 5120 bytes represents one row. A group of 6 pixels is stored in 4 bytes. 6 Y samples with 3 each of (cb, cr). There's 2 extra bits per byte, btw.
You can easily see an outline of your picture and step through the frames to see motion, even in encoded form, some of the luma looks like picture.
Some work with masktools and this can be decoded completely in script.
My file had no audio, so how do you guess the filehead for your file? It's easy, for HD just use 5120x1080 size per frame, multiply by number of frames, and whatever is leftover is all header! Example, my sample had 3 frames, 16588800, filesize was 16609992, so 16609992-16588800=21192. This was from a Blackmagic declink capture.