QT wrappers knock it down to 8 bpc, right?

[Colin Rider]

I've read here that there's no difference between R3Ds and their wrapped QT files but I've also heard that the QT wrappers can access only 8 bits per channel (bpc). This might be outdated info, though.
I'm color grading and I want to work with the full color depth for but it looks like I can only do that during the one-light pass (without something like Scratch).
Thanks in advance.

 

[Uli Plank]

Graeme has confirmed that if you calculate in high-precisdion in FCP it's using 10 bit.

If you grade in Color it will access the sources anyway.

 

[Ben Brainerd]

The wrappers may/may not be 8-bit while viewing/editing, depending on system settings, but llike Uli said, once you jump to Color (Or whatever native-based grading suite you use) you'll have access to the full range.

 

[Alexander Ibrahim]

Quicktime is 8 bits per channel, if you are viewing through Quicktime Player.

Final Cut and other pro apps will see greater bit depth.

 

[Colin Rider]

Damn, I love RED. And now I love its workflow even more. I thought REDCINE-X was my only option. Thanks, Uli, Ben, and Alexander.
Since I might build my grade around Colorista I'll test that the QT wrappers in a After Effects 16 bpc log project access the full 12 bpc range. Besides playback this should work well...I think.

 

[Graeme Nattress]

A Quicktime codec can represent it's data to another app in a number of formats. The RED Quicktime codec will present the data in 8bit if asked (for RT in FCP and playback in Quicktime Player) and if the app asks for r4fl it will present the data in 32bit floating point format (FCP10bit pathway for instance).

Quicktime is only a wrapper. It is the responsibility of the app requesting the data to ask for it in the most appropriate format.

Graeme

 

[Uli Plank]

Take care, though, not to use filters or transitions in FCP that knock it down to 8 bit. CoreMelt has a pretty good whitepaper on the subject.