Storage for native 4K workflow

[Shane Betts]

Excuse me if this has been covered elsewhere. Don't shout, just link:innocent:

With the exciting stuff we've seen from Adobe this week, and the possibility that other vendors will follow suit I feel one thing needs to be clarified.

If we're working with the R3D's all the way through, doesn't that mean we need only storage that will support 37MB/s rather than ten times that for DPXs?

Am I missing something?

 

[John Tissavary]

Sort of... but r3d is only for raw bayer sensor data - it is not a format that you can render to. As soon as you render you need storage for whatever format you've rendered to, which may well be in excess of that bitrate.


cheers,

JT

 

[Shane Betts]

And that's a part of the Adobe support I'm not yet fully understanding. In the video demo it seemed to do a few layers without the need to render so, in theory, we could do the cut on a typical talkie feature with a fairly pedestrian array and only when we do the final grade out to DPX for film out (where real time isn't needed) would the files get large. We could then get in a big array but speed still not critical. ??