http://blogs.adobe.com/toddkopriva/2009/03/prores_422_colors_in_after_eff_1.html

If you looked at the image you would have seen the final comparison was in FCP. (I think the steps are clear enough – FCP to AE back to FCP for comparison. I can’t think of another way to do this.)

BTW — The “specifics are important line” you asked about was supposed to read “specifics are not important.” To me, that there’s a color shift is enough to render the codec unusable for the FCP to AE workflow. I don’t need to know anything else except when it’s fixed.

It’s easy to run the test yourself as described in the original post with any codec.

If possible, can you update your blog post so to clarify some stuff?

Can you expound upon these differences in behavior?

Placed on an AE timeline I assume? Rendered in AE and then imported to FCP? (the text isn’t clear)
I assume you are using ‘Difference’ mode in FCP…but you don’t mention it…

Can you explain these procedures and steps you took?
All this stuff will really help folks track with you exactly.

Thanks Frank, good catch on calling this one out.

Carey

There’s a new checkbox in After Effects CS3 that will let the user decide on how to handle QuickTime gamma conversions, due to bugs in QuickTime. You can either go with the AE7 method that will lead to gamma shifts between Mac- and Windows-rendered clips, or use the better CS3 method.

I’m not in front of a CS3 install at the moment, but I think it’s in the “Interpret footage” dialog box. Please try to change this setting and try again.