-
MAC / CS3 / DVCPRO-HD color shifting
-
this has been dealt with b4, just install pro codec so that AE uses same codec to open it. It’s the same thing when you can have xvid, divx, ffshow open a movie, they all can, but they all interpret the gamma differently. Then just double check that the pro codec from FCP is set HDTV color and colorspace for AE will work fine. We’ve confirmed it.
-
Also from the FCP 6.0.2 Release notes:
“Gamma Import Option Has Been Renamed
In Final Cut Pro 6.0.2, the Imported Still/Video Gamma option in the Editing tab of the User Preferences window has been renamed Imported Still/RGB Video Gamma.”
There are 4 options for this setting:
Source
1.80
2.20
2.22
CustomCould it be that this will overwrite the gamma flag and force FCP to use the gamma of choice? This is strictly speculative that it is doing the RGB>YUV calculation and FCP is just reading the gamma wrong. If there is an encoding error, I doubt that this will have the affect desired.
kw
kris@wotipka.com
Image maker -
I am afraid you will have to explain your response a bit more. I am not understanding your post.
kris@wotipka.com
Image maker -
Chris Wright writes: “just install pro codec”
Anybody know what”pro codec” is? It does seem to me that AE interprets gamma incorrectly from outputted FCP DVCproHD files. My work-a-round is to export from FCP using animation codec. Somehow I tend to frequently lose a frame of video on the round trip (and I mean wrong frame rates).
-
Apple has not released the DVCPRO HD codec for general QuickTime users, and especially not PC users. It’s a closed-end format that can only be read by the codec included with FCP.
Adobe and Apple used to play nice, now their dvc pro hd codecs interpret gamma differently. You need to keep same codec from output of FCP to input of AE. Some choices are Mainconcept, Canopus, Cineform, and Raylight. Unless you can hack the decoder reader, you’ll have to shell out some dough or rollback to an older FCP and AE.
btw. animation codec is very very buggy. If you can use something else, do it.
-
Ok, look, I think I’m just trying to do something simple and common, but it’s broken. So what say we get together right here and solve this problem, once and for all, for everyone.
THE CHALLENGE: Getting DVCProHD video exported from Final Cut Pro, into After Effects, and then back into Final Cut Pro without shifting color or gamma.
THE PROBLEM: Apple and Adobe interpret Gamma differently when using the DVCProHD codec. Each use their own version of a DVCProHD codec.
SUGGESTED SOLUTIONS: Use the same 3rd party codec in both software packages (FCP and AE).
CURRENT WORKAROUND: Export from FCP using Animation Codec (found under “other”), but it’s slow, buggy and the files are huge.
MY QUESTIONS: How would one implement a 3rd party solution which really works with current releases of Final Cut Pro and After Effects. Has anyone solved this problem? What are the details of a solution. Is there any test signal anyone can point to that might help us measure the solution? And finally, why isn’t this problem front page news?
-
I’m having the same problem. And it doesn’t sound like there’s any definitive solutions yet…
——————————————–
Mac Pro | Leopard 10.5.3
2.66GHz Dual-Core Intel Xeon | 4GB Ram
Final Cut Pro Studio 2 | Avid Media Composer -
I have had a similar problem with the Quad-Core Intel (2x3Ghz) and Apple ProRes files (originally shot on Red camera and exported via Red Cine). I’ve been working at a company that still has a bunch of PPC machines (how last century), and the gamma shift with the new machine(s) is huge.
From the Almost Silver Lining Department:
One way to test to see if you have this problem (even if you can’t compare to other machines) is to import the movie file in question into AE, make a comp for it, open that comp and toggle different bits per channel (bpc) settings by option-clicking the bpc button at the bottom of the project window. When you shift from 8 bit to 16 bit, you should see a major gamma shift if you have this problem. If you do compare with another (‘safe’) machine, you’ll see that the 8-bit is shifted considerably from one machine to the other (check specific pixel values). When you change to 16-bit on the ‘bad’ machine, the values will be much closer to ‘correct’ (16-bit) values, but still off. Of course I am assuming the ‘safe’ machines have the correct values (which I believe is a safe assumption). -
I’ve found that exporting using the Animation codec from AE gives the same gamma when using DVCPRO HD as the original footage. I assume it would be the same if you used ProRes as well.
Not an ideal solution I know, but one that would give you a correct image that you could then export or compress using whatever codec you want.
——————————————–
Mac Pro | Leopard 10.5.3
2.66GHz Dual-Core Intel Xeon | 4GB Ram
Final Cut Pro Studio 2 | Avid Media Composer -
You can check and edit the gamma flag in quicktime with “Dumpster”. That way you can see what AE is coding the output for decompression. If its 2.2 change it in dumpster to 1.78666(? not exactly sure of the # but if you dig around you can find it)
heres the link from apple.
https://developer.apple.com/quicktime/download/
del
you cant hear my inner voice scream… can you..?
Reply to this Discussion! Login or Sign Up