FORUMS: list search recent posts

Re: FCP-X HW I/O-support: a hypothesis

COW Forums : Apple Final Cut Pro X Debates

Respond to this post   •   Return to posts index   •   Read entire thread

Chris Kenny
Re: FCP-X HW I/O-support: a hypothesis
on Jun 23, 2011 at 3:05:53 pm

[Clayton Burkhart] "No, what makes no sense is Colorsync for video output, because Colorsync is an RGB system which an I/O system bypasses.

So if you expect to actually USE Colorsync for video, that by it's very nature precludes YUV.

This does not mean of course that you cannot HAVE video output at the same time, it only means that Colorsync in reality will have little or no relation to your true YUV video image.

The reason that I have pointed this out is to show that Apple has almost exclusively concerned itself with the individual who creates WEB content which is RGB, not the video professional who creates for television, film, etc.

Anything that can be represented in YUV can be represented in RGB. There's no quality penalty for conversion if you do so in a sufficiently precise color space... and FCP X's engine uses high-precision floating-point processing. You know what other app processes everything in a linear floating-point RGB color space? DaVinci Resolve. Would you like to argue that's also not capable of accurate color output? Because my experience screening stuff I've graded with it in DI theaters says otherwise.

YUV, in the modern world, is best thought of as an internal implementation detail of some deliverable formats. With the precision of floating point, there's no reason it needs to have anything in particular to do with how processing actually occurs.

Digital Workflow/Colorist, Nice Dissolve.

You should follow me on Twitter here. Or read our blog.

Posts IndexRead Thread 

Current Message Thread:

© 2019 All Rights Reserved