Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro Dynamic Links not updating in Premiere Pro and Media Encoder

  • Dynamic Links not updating in Premiere Pro and Media Encoder

    Posted by Claire Presnall on April 3, 2015 at 11:20 pm

    The dynamic linking inside Premiere is not updating to reflect changes that are being made to the linked comps inside of AfterEffects. This is sometimes exibited inside of the Premiere sequence where it will not register that an update has occurred inside of AE and continues to use the previously current prerender. Sometimes the dynamic link displays correctly inside of Premiere but renders incorrectly from Media Encoder. When it does this, it is displaying the dynamically linked AE comp from a previous state of being that does not reflect how the comp looks inside of the actual project in AE.

    Restarting the programs and computer does not seem to help.

    Flushing the cache does not seem to help.

    Manually deleting the video preview files from Explorer triggered Premiere to have to rerender the sequence, which did produce an update that reflected the current state of the AE project, but then rendered incorrectly out of Media Encoder.

    And then, sometimes, it all works just fine and everything updates the way it is supposed to. I’m running CC 2014, Window 7.

    Anyone else having this issue of have a solution?


    Mads Nybo jørgensen
    replied 1 week, 3 days ago
    5 Members · 5 Replies
  • 5 Replies
  • Oki Pienandoro

    April 5, 2015 at 7:29 pm

    Never having one of those, similar, but usually it’s just really heavy AE comp, and Premiere is struggling to keep-up with the changes, crashed. etc (due hardware limitation).

    3rd party plugin related problem, maybe ?
    Do this happen on every project ? Or just specific project/comp ?

    Sorry, not much of a help..

    Sorry for the english, not native speaker.

  • Ht Davis

    April 6, 2015 at 10:07 pm

    Most people don’t realize what the linker is doing. It’s not linking directly to your program and watching you make changes. It’s linked to the project file, and the xml reader that the program uses (the project files are essentially xml instruction sets for the rendering engine).

    Unfortunately, there have been issues with memory linkage in dynamic link and with CUDA or other accelerated graphics. There are major changes occurring at the system level where memory is concerned, as well as changes to how graphics are handled.

    The dynamic link problem you describe is an old one, I think, but I’ll give you both solutions. I’ll start with the old answer.

    When you link to your comp, it’s looking into the saved project file. Save your AE file, close AE and go to premiere. You should see a bar updating the files. If not, check the comp. Right click and see if there’s an update to it. Try a save and close, then reopen. It may update that way. If it renders out incorrectly, even after a save operation, the dynamic link is showing the memory issue (a new problem). Also make sure you name your comps uniquely.

    Let me describe this problem for you:
    Program A sends data to Program B, and Program B opens a new copy of the XML reader of Program A (but Program A has it’s own already open). Program B then sends data back to program A, which opens a new copy of the XML reader of program B, but program B is already running it in different memory. Both programs attach a separate piece of the instructions for the data, and because they don’t link to the same reader, the memory has to be copied to be linked together. However, that memory isn’t being copied because of the new way memory is protected by the system.
    One solution I’ve found is drag-linking. With the premiere project open, drag your clip into AE and edit there, then drag the comp back to premiere. This associates to the xml reader each program is already running, and (I don’t know which) either forces the memory copy or simply uses the original set of xml readers. Doing so will allow the linkage to work even after closing and re-opening; again I’m not sure if there is some sort of process link id that is included in the xml, but it would make sense. The drag should work going right from AE to Premiere with a simple effect (you don’t have to start your clip in premiere). The same logic would apply as well. If you start an autosaved project, you may have to relink a comp or a clip. This means you’ll have to do a drag and replace the comp.
    If it still has trouble on exporting, you may want to export within premiere first, then out to a compression with AME.

  • Claire Presnall

    May 13, 2015 at 10:04 pm

    Thanks for your response. Sorry for the delay in mine.

    Solution #1 wasn’t doing anything for me. That was my initial thought. It would play correctly in Premiere, but rendered out legacy graphics.

    The work-around I found that seems to have the most consistent results is just duplicating the dynamic link and stacking it on top of the offending layer which I disable. Of course, this has left me with some annoyingly tall stacks of layers. I can’t delete unused layers, though, as it reads the new one as the old one and renders out the problem again.

    I finished that project with my work-around and haven’t had the issue in any projects since, but I’ll try your dragging solution next time it rears its ugly head!


  • Paul Roper

    July 2, 2024 at 2:03 pm

    It’s funny how:
    (a) over 9 years the Adobe CC price has shot up
    (b) some issues still have not been resolved (hmmm…”Resolve”…that gives me an idea…)

    I just had this exact same issue today, in July 2024: I have a ~7 minute edit with ~30 linked AE comps. I changed one of the comps in AE, and in PPro it looks perfect – all updated and nice. I sent the export to Media Encoder, where it sat slowly encoding for about half an hour. Imagine my joy, when I played it back, to find that rogue, old AE comp in there…even though this comp technically no longer exists anywhere…and how I had to embarrassingly and unprofessionally stall my client while I frantically fixed the problem. Thanks, Adobe.

  • Mads Nybo jørgensen

    July 3, 2024 at 2:20 am


    I feel your pain.

    Suspect that Adobe Bridge is not keeping up with assets – who uses that thing anyway, except when rogue elements invade your timeline?


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