Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro CS5 After Effects Composition Render Issues

  • CS5 After Effects Composition Render Issues

    Posted by Casey Pegram on September 2, 2011 at 3:03 pm

    I’m encountering a nasty bug in Premiere CS5 v5.0.4. I’m shooting a lot of greenscreen work and using Ultrakey to do most of the keying, but some shots I need more advanced spill suppression, and for that I’m using Keylight in AE. I’m doing this just by sending the shots to AE with the ‘Replace with AE Composition’ command.

    Once I’ve got my shot fixed in AE, I save the project and it updates back in the Premiere timeline. Great! However, once I render, I’m noticing weird duplicate/blended frame issues intermittently throughout my Premiere renders. There doesn’t seem to be a fixed pattern to them, and I’ve double checked my sequence settings and they seem to match. They render without issue if I do a RAM preview in AE.

    Has anyone else had this issue? I know the sequence settings are the first thing I would check, and I have, and it should work without issue since I haven’t change anything in Premiere or AE. It almost seems more like a system resources issue, like glitches occur when memory can’t be allocated properly. Anecdotally, I’ve noticed less glitches if I render after a fresh reboot.

    Any help would really be appreciated!

    Todd Perchert replied 14 years, 8 months ago 5 Members · 9 Replies
  • 9 Replies
  • Petros Kolyvas

    September 2, 2011 at 3:27 pm

    I found lots of AE CS5 (haven’t had the same issues with CS5.5) render issues were fixed by disabling the “Render multiple-frames simultaneously” option under multi-processing in AE or the AE render engine.

    When I got really stuck and was trying to export my final edit, in one case I simply used AE to render out all the scenes/shots and then just created a copy of the Premiere Sequence and manually replaced each one; it wasn’t fast, and wasn’t pretty – but it worked.

    I wish you the best of luck finding a solution that works – it can get very frustrating!


    There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger

  • Vince Becquiot

    September 2, 2011 at 4:21 pm

    One solution was to make the comp background black in AE, I guess there are working on that bug.

    Vince Becquiot

    Kaptis Studios
    San Francisco – Bay Area

  • Vince Becquiot

    September 2, 2011 at 4:22 pm

    I misread, I thought we were talking about Dynamic linking, Petros is indeed correct.

    Vince Becquiot

    Kaptis Studios
    San Francisco – Bay Area

  • Petros Kolyvas

    September 2, 2011 at 4:30 pm

    [Vince Becquiot] “I misread, I thought we were talking about Dynamic linking”

    I thought we were talking about it too…

    As far as I know (and I might very well be wrong) dynamically linked compositions will still use AE’s render settings (I’m actually opening up the discussion here.) 😉


    There is no intuitive interface, not even the nipple. It’s all learned. – Bruce Ediger

  • Vince Becquiot

    September 2, 2011 at 4:41 pm

    That reminds me of a render I did a while back at the last minute (about 16 hours worth with no time to re-render). Had to replace over 50 of those half black frames with stills from the timeline inside Premiere. Fun times…

    Vince Becquiot

    Kaptis Studios
    San Francisco – Bay Area

  • Tom Daigon

    September 2, 2011 at 4:48 pm

    I just bumped into a wierd-in-a-good-way thing when using dynamic link.
    When I render to ram (using Zero) in AE, when I tab back to PrP I can play back that AE comp with no rendering. Apparently PrP and AE share the same ram with DL. But of course eventually I have to render the file in PrP. Just a nice surprise for a change.

    Tom Daigon
    Avid DS / PrP / After Effects Editor
    http://www.hdshotsandcuts.com
    Mac Pro 3,1
    8 core
    10.6.8
    Nvidia Quadro 4000
    24 gigs ram
    Maxx Digita / Areca 8tb. raid

  • Vince Becquiot

    September 2, 2011 at 4:51 pm

    Yep, an extra TB of RAM sure would came in handy for that 🙂

    Vince Becquiot

    Kaptis Studios
    San Francisco – Bay Area

  • Casey Pegram

    September 2, 2011 at 6:22 pm

    Thanks everyone for all the helpful replies. Unfortunately, I already have multi-frame rendering disabled in AE, so that must not be the issue.

    I think in this instance I might just go with rendering each shot out from AE and bringing it back into Premiere. Long-term though I’d really like to get a handle on what’s causing this because as you can imagine it’s a major workflow hangup.

  • Todd Perchert

    September 2, 2011 at 6:53 pm

    Let me ask this… You say when you render in Pr it is showing this. Is that a Preview Render or render out to another file? Reason I ask is I had something before with using hardware acceleration and wiping between PNG files. It would kind of double up, so a drop shadow would seem twice as strong during the transition when rendering the preview, but rendering out the final product with AME to another file it would be fine. I was able to switch to using software only rendering and the problem would be gone.
    I haven’t seen it in the manner you’re describing, but it sounds similar enough.
    TC

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