Gamma shift between FCP and Motion

[Noah Kadner]

I would suggest rendering out lossless from Motion- it’s a time saver in the long run.

Noah

[Tom Bridges]

Hey thanks Noah – that was a quick response!

But it’s basically broken, right? We’ve been banging our head against the wall all day. We’ve ended up just rendering to a 10bit RGB format (AJA) and using a RGB timeline in Final Cut. It’s a graphics-only project.

A shame – it’s a nice idea to have that kind of integration with Final Cut. Just a pity about the implementation …

Thanks,

Tom

Split Image
http://www.split-image.co.uk

[Noah Kadner]

Why RGB? You need to be in YUV space in FCP to avoid these sort of shifts. It’s nothing to do with the integration and everything to do with the settings.

Noah

[Tom Bridges]

That’s strange. We were getting the shifts moving from YUV (AJA 10-bit timeline) to RGB and back again. We moved to a 10bit RGB timeline in Final Cut which has solved all our issues.

What codecs do you use to avoid getting a shift?

Thanks,

Tom

Split Image
http://www.split-image.co.uk

[Jeff Bernstein]

Tom is correct in keeping things in RGB. Apple has a real mess on their hands as it relates to RGB-YUV conversion. They basically decipher Gamma incorrectly. To avoid it, the best method is to use Tom’s method.

FCP is not required to use its YUV mode unless you are looking to perform any time of effect. Since Tom was simply using FCP to laying graphic elements, I think he will be just fine.

If you are less than thrilled about this workaround, and who wouldn’t be, I suggest a hike over to this url https://www.apple.com/feedback/finalcutpro.html

Jeff Bernstein

Digital Desktop Consulting
Apple Pro Video VAR
XSAN Certified

323-653-7611