Activity › Forums › Adobe After Effects › Where is the 10-Bit 4:2:2 codec in AE CS3?
-
Where is the 10-Bit 4:2:2 codec in AE CS3?
Posted by Jay Lee on June 24, 2008 at 11:10 pmHi guys,
I am sharing the frustration of many in terms of producing gamma accurate renders from AE CS3. None of the suggestions such as Color Management, Legacy etc are helping. My renders are also noticeably soft & with a dark gamma shift. I wonder if the Black Magic 10 bit codec is part of the problem here? I went to select the 10-Bit 4:2:2 codec that we use in Final Cut but it is not listed in AE? Why is this? Can we not come in and out of AE via Final Cut using the same codec?All thoughts most appreciated.
Cheers,
J
Jay Lee replied 17 years, 10 months ago 4 Members · 19 Replies -
19 Replies
-
Chris Wright
June 25, 2008 at 1:13 amuse file->project settings -color depth 32 bits/channel, working space, one of the RGB’s, adobe or apple, then use a YUV codec that doesn’t change color space from 4:2:2 to anything else. Some YUV’s go yuv12 yuvu, etc and bits get flipped around and color lost from RGB to YUV and back again.
—10-Bit 4:2:2 codec that we use in Final Cut but it is not listed in AE?
Oh yea? go video for windows-10 bit, YUV 4:2:2 YUVunless your strapped for size, RGB uncompressed output 4:4:4 will guarantee no generation loss.
-
Jay Lee
June 25, 2008 at 5:40 amHi Chris,
So appreciate your taking the time to respond. Thank you.
Are you suggesting that we should choose an Adobe or Apple color space over SDTV NTSC?
The files being imported into AE have an embedded profile listed as SDTV NTSC Y’CBCR but this profile is not listed in AE.
32 Bit……great tip thank you.
In regards to a codec for rendering the only YUV type option listed is Blackmagic 8 Bit (2VUY). This is a Mac machine so no Windows options or RGB 4:4:4.Your thoughts most appreciated.
Cheers,
J
-
Chris Wright
June 25, 2008 at 6:48 amo ic.
Well. I only suggest RGB because it has a larger range and can do more saturated colors.
If your footage is 8-bpc, then keep working color space the same as the output color space, but I’d still recommend 32-bpc because working in 32-bpc color allows over-range colors.
The cool thing is, 32-bpc are not limited to the color boundaries of even high def footage. The over-range colors are simply a more accurate way to color correct even if you are going back to a smaller color range.
The most important thing is knowing where the final footage is going. If its for SDTV, color boundaries should be SD or you’ll have illegal chroma or luma and have to use plugins to subtly soften the extremes. There’s a HDTV (Rec. 709) for high def and a sRGB IEC61966-2.1 for the web, too.
-
Jay Lee
June 25, 2008 at 7:04 amYep…solid advice thank you.
The challenge still remains that rendered footage appears soft and dark!!Cheers,
J
-
Chris Wright
June 25, 2008 at 7:15 amThis kind of dilemma is showing up more and more frequently these days, and it is almost always due to type of file imported into AE. If your files are any of the following:
• Native HDV
• Mpeg2
• Mp4
• H.264You need to convert them into something else. The compression in these files results in many frames that contain incomplete picture information, interframe IBBP. AE wants complete picture information for each and every frame,intraframe. IIIIIIIII
What you convert them to depends on your platform (mac/win).
from:
https://forums.creativecow.net/readpost/2/929330 -
Jay Lee
June 25, 2008 at 7:28 amI wish that was the case Chris but our source files are 10 Bit Uncompressed Quicktimes captured straight from Digi. The only processing they undergo before coming into AE is a reverse telecine via Compressor.
The original source is 35mm film.Cheers,
J
-
Chris Wright
June 25, 2008 at 7:44 amuh 35mm, better read this cuz quicktime aint gonna have enough gamma information.
https://library.creativecow.net/articles/oconnell_pete/cineon.php
-
Santiago Gutierrez
June 25, 2008 at 2:22 pmJay,
Does the computer running AE have FCP installed on it? I ask because if you captured a 10 bit Uncompressed using a Blackmagic card, it is using the Apple 10 bit Uncompressed codec. This codec is only installed with an install of FCP. So the AE machine must have that FCP install to have the correct codec loaded. In AE, when you are setting up your render que for a Quicktime output, under the Format Settings, pick Apple FCP Uncompressed 10 bit 4:2:2. That should be the same as what you originally digitized. As far as the gamma goes, when I’ve had this problem, I check the “Match Legacy After Effects Quicktime gamma” and that fixes most of them. It’s in the Project Settings. And obviously make sure you’re working at the same frame size and frame speed as your original file.Santi
-
Jay Lee
June 25, 2008 at 4:12 pmGood morning Santiago,
Thank you for your reply. Yes, this machine has Final Cut Pro Installed although it was not the system we captured on. The capture system used a Kona card.
The only Apple codecs listed in AE on our machine are the Pro-Res and Intemediate. No Apple 10 Bit.
In regards to gamma shift upon render/output we have scoured the Cow and tried all permutations of the Legacy & color management theories with out improvement.
To make things more frustrating renders out of both Final Cut and Color are suffering major gamma and chroma shifts??Best,
J
-
Joey Burnham
June 25, 2008 at 6:53 pmAE will pick up on whatever codecs the system has, so have you tried getting the latest blackmagic drivers and doing a re-install. AE would then see Blackmagic Uncompressed 10-Bit, which should work.
As for your recent problems out of FCP and color I have no clue. What kind of render out of FCP?
Reply to this Discussion! Login or Sign Up