Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy AE render won’t match

  • AE render won’t match

    Posted by Ron Craig on April 12, 2008 at 8:40 pm

    I’m having trouble getting a render from After Effects (CS3) to match the source material from Final Cut Pro (6). I want to fix a distraction that moves through the background of an interview for just a few seconds. The fix is easy. But when I render out those few seconds from After Effects and drop them back into the interview sequence there is a distinct color and brightness shift. It’s unusable.

    It must just be a setting thing but I have tried lots of different settings in the render and output module selectors and I can’t create an export clip that will match back in FCP. My source material in FCP is DVDCPRO HD 720/30p, which was captured via Kona 3 card as DVDCPRO HD 59.94 ProRes 422 (HQ). I exported the few seconds of interview as a Quicktime movie directly, not through Compressor. Coming out of AE I have tried animation and DVDCPRO HD 720p 60.

    Can someone suggest settings for me that will make the AE render match the source interview scene? I hope so…

    Jim Greenslade replied 17 years, 11 months ago 7 Members · 21 Replies
  • 21 Replies
  • Rafael Amador

    April 13, 2008 at 2:33 am

    Hi Ron,
    You are doing nothing wrong. i’m afraid this have not solution. AE renders in RGB whatever the codec you use on exporting. It will always be a kind of shift in color/bright respect to the YCbCr footage. If you can do it in FC this shift won’t happens.

    Mac OX 10.5.2-FC 6.02-QT 7.4.1
    G5 2x2Gh 4GbRAM-BlackMagic Extreme
    PMBP 17″Core2Duo 4GbRAM-AJA ioHD
    JVC DTV-17″
    SONY EX-1 . SONY PD170
    ..and always a big mess on top of the table.

  • Tim Mclaughlin

    April 13, 2008 at 2:47 am

    Sorry news for you. But…

    Render out the whole interview clip, fix what you need and bring the whole thing back in.

    At least then you won’t have the shift…

  • Simon Webb

    April 13, 2008 at 7:20 am

    You might also try redoing the After Effects fix in Motion. I can’t guarantee that it’ll work, but you never know.

  • Ron Craig

    April 13, 2008 at 4:27 pm

    Wow, what a bummer.

    Well, thanks for the information. At least I know it isn’t operator error (as usual).

    And to think of all the versions of After Effects I have purchased and used through the years…and the fact that I just upgraded to the newest version with expectations that it would play nicely with my new High Def studio! Real bummer!

    Since everybody but me (until now) seems to know about this, do you know if Adobe is doing anything to address this problem or is it so ingrained in the AE way of doing things that a fix won’t appear?

    Are there any render settings in AE or Color adjustments in FCP that are shown to ameliorate this? Otherwise, I guess I’m going to have to learn Motion a lot better — and hope it has the capabilities that I need.

    Bummer!

  • Aaron Neitz

    April 13, 2008 at 5:19 pm

    I’ve just done a bunch of work in AE with DV-50 and uncompressed codecs in SD and not a single pixel drifted in color or gamma! What’s up with ProRes??

    check out this thread

    https://forums.creativecow.net/thread/2/932015#932448

  • Ron Craig

    April 13, 2008 at 5:45 pm

    Aaron,

    I don’t believe the posters above were saying that this is a ProRes issue. I take it that it is a more general colorspace issue.

    Are you saying, Aaron, that you have been able to accomplish successfully what I have so far failed to do, as described in my initial post, above? If so, I would really appreciate you passing along the workflow/settings that you used.

    Cheers,

    Ron

  • Rafael Amador

    April 14, 2008 at 1:29 am

    Nothing to fix in AE (why AE, Shake, Combustion etc do not render in YCrCb?).
    Is not a problem of the codecs but of the color space. You will get similar color/bright shift rendering inside FC in RGB.
    This article of Poynton gives the clue:
    Merging computing with studio video: Converting Between R’G’B’ and 4:2:2
    https://www.poynton.com/papers/Discreet_Logic/index.html

    Mac OX 10.5.2-FC 6.02-QT 7.4.1
    G5 2x2Gh 4GbRAM-BlackMagic Extreme
    PMBP 17″Core2Duo 4GbRAM-AJA ioHD
    JVC DTV-17″
    SONY EX-1 . SONY PD170
    ..and always a big mess on top of the table.

  • Rich Rubasch

    April 14, 2008 at 1:37 am

    In AE, go to File-Project Settings and in the Color Settings select in the pulldown either HDTV or SMTP-C. We have successfully taken DVCPro50 and DVCProHD from FCP and back with no shift doing this. You will also have to choose your footage and match the setting you chose in the project settings for color. Click on a footage clip in the project window and hit Command-F (Control-F on a PC) and in the second tab you will see a setting at the bottom with your color settings. By matching this to your project setting, and a little trial and error, you should be able to take clips back and forth with no shifting.

    Try it and post back. Has been working for us, even though other posters have not been successful. It took a couple tries, but we got it to work.

    Best way is just to render out a clip from a comp without doing any effects and put it back in FCP and compare it to the original…

    Rich Rubasch
    Tilt Media

  • Ron Craig

    April 14, 2008 at 2:52 am

    Thanks! I’ll give it a try and post back.

    Ron

  • Aaron Neitz

    April 14, 2008 at 3:06 am

    Rich has got it right. Check out those colorspace tabs…. Even though we’re all dealing with YUV to RGB and back again, the resulting renders should be virtually indistinguishable from the original footage.

    When I get in the office tomorrow, I’ll look at my AE settings. I actually haven’t been bothering with the colorspace preferences working in standard def – AE’s initial settings have worked perfectly well. Are you on Leopard by chance?

Page 1 of 3

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy