Home Page › forums › Applications › After Effects › ProRes 422 Workaround for AE CS3?
- This topic has 3 replies, 4 voices, and was last updated 7 years, 4 months ago by Anonymous.
-
AuthorPosts
-
November 2, 2010 at 2:31 pm #203045JL1138Participant
Hello,
How do I render out animation in CS3 for use with ProRes 422 Live Action footage? I don’t have Final Cut Pro (and thus no ProRes) on my machine and the Live Action we are compositing to is in ProRes422. Someone suggested outputting to 8-bit uncompressed QT would be comparable, but I don’t see that as an option in my dropdown menu. Any help would be greatly appreciated. Thanks.
JLApril 21, 2011 at 11:19 pm #218196charles wesleeParticipantI believe you’d be looking for “none”… CineForm is also a very good codec, and even though you need to purchase it separately, the pricing just came down significantly…
May 6, 2011 at 2:15 pm #218197pepijn schroeijersParticipantI believe you could render out to the Avid DNxHD codecs which are free. I’m pretty sure they are of the same quality as prores
July 2, 2013 at 6:54 am #218198AnonymousInactiveHi all, previous testing of the ProRes codec comparing it the Avid DNxHD codec yielded some unexpected results when Adobe After Effects was used to generate test media. While the Avid codec made the round trip from Media Composer 2.7 to After Effects and back without issue, the ProRes codec showed what appears to be an YUV to RGB conversion issue.
Further testing reveals that the issue is not consistent between a recent beta release of Adobe After Effects 8/CS3 and After Effects 7.
ProRes 422 through After EffectsPictured (click to enlarge) are the waveform and vectorscope images when the original ProRes 422 HQ material is placed on V1 of a Final Cut Pro 6 timeline and the same image placed on V2 after being run through After Effects with no changes made to the image – the clip was placed in an AE timeline and simply re-rendered with ProRes 422 HQ.
For the time being I don’t recommend using Adobe After Effects to render ProRes 422 material. While we can be confident this issue will be addressed shortly, this is exactly the kind of gotcha that can be expected when a new codec is released in the latter phases of a beta cycle. I’ve been transcoding clips to the Animation codec with Final Cut’s Media Manager before going to After Effects. Allowing FCP to handle the YUV-RGB conversions seems to work well.
The bigger lesson is that whenever a new codec is introduced to your workflow it should be tested in the applications it will be used in.
Looking down the road, color space, codec, and file format, and frame rate conversions will be with us for a long time. Make hardware and software decisions with eye towards the future and compatibility, That is all.
-
AuthorPosts
- You must be logged in to reply to this topic.
