Skip to main content
C
core787
Known Participant
February 27, 2026

Render and replace of changes to Dynamically linked AE comps causes errors

  • February 27, 2026
  • 1 reply
  • 22 views

Use the template below to provide us with information: 

  • Issue – When I make a change to something that was previously rendered and replaced, it overwrites the previouss render rather than increasing the filename number as it used to do. 
  • Steps to reproduce – Render and replace a comp, restore unrendered, and render and replace again. Premiere gives “cannot find frame” errors until you close and open Premiere again. 
  • Expected result – The file names of the renders should increase. 002, 003, 004 etc. 
  • Actual result – Its overwriting the same file ending in _Rendered.mov
  • Adobe Premiere Pro version – 26.0.1 Build 3
  • Operating system – macOS Tahoe 26.2
  • Affects all projects.

      1 reply

      R
      Community Manager
      Rach McIntireCommunity Manager
      Community Manager
      February 27, 2026

      Hi ​@core787,

      Thanks for providing all the details — that’s very helpful.  A few follow-up questions.

      • Are the dynamically linked AE comps saved locally or on a network/Team Project?

      • Does this happen with any comp or only specific ones with certain effects or layers?

      • Are you using the default Render and Replace settings, or custom output paths?

       

      Thanks again for the thorough info — we hope we can help get this sorted quickly.


       

      C
      core787Author
      Known Participant
      February 27, 2026

      No problem. 

       

      They are saved on a Lucid Link drive. So.. whatever that qualifies as, but for years I have used that functionality on Lucid drives and it worked fine. 

       

      As far as I can tell it happens with any and all comps that are dynamically linked in Premiere. 

       

      I am using these settings:

       

       

      I just tried a new project on my desktop and have the same thing happen:

       

      And then moved the project to a folder internal drive just in case the Desktop’s syncing to iCloud Drive was causing issues and still got the error:

       

      IanB_360
      Community Manager
      IanB_360Community Manager
      Community Manager
      February 28, 2026

      Hi ​@core787 
      Do you recall the last version of Premiere you used where this was functioning as expected? Currently, whenever you choose the location “Next to original media,” you will get the file overwritten and an error when retrieving frames. Right now, the workaround is to choose a separate folder for your media to render and replace. So if you make a new folder called render_and_replace and use that as your location, you will be able to work as expected, with files incrementing by _001, _002, _003, etc. 
      Here to Help.

      Ian

      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices