Skip to main content
AndrewTheGreat
AndrewTheGreat
Known Participant
January 28, 2026

Pr 26.0 Render and replace issues

  • January 28, 2026
  • 1 reply
  • 81 views

Since I cannot find my previous bugreport after the redesign of Adobe community, not even in my profile > recent posts I have to start another one. This time it concerns the fresh 26.0 version of Premiere Pro.

Render and Replace feature is glitchy in v. 26.0. It fails with timeremapping. Steps to reproduce:

  • start an empty project, import media, cut it on your timeline
  • take one clip and timeremap it. Try to render and replace. Result:

 

Render and replace fails in vertical sequences. Steps to reproduce:

  • from the previously created horizontal sequence copy and paste a clip in a newly created vertical sequence. 
  • Fill the screen with it using the context command. Render and replace. Sometimes you get an error like above, sometimes you get this one:

 

Render and replace fails with the new object mask. Steps to reproduce:

  • in the horizontal sequence select a non-timeremapped clip, select it with an object mask, track it, place the unassigned mask on the opacity
  • Render and replace the masked clip. Result:

 

This all happens with Prores 4444 as a render and replace codec with the sequence source (the only one capable of embedding effects). This is what happens with a GoPro codec:

 

Different media, different resolutions. I use the sequence templates as a starting point:

 

Please, guys, I don’t need workarounds - know them all - I just want this disgrace to be fixed.

 

 

1 reply

D
Community Manager
Dani_V.Community Manager
Community Manager
January 29, 2026

Hi ​@AndrewTheGreat,

Thank you for reporting a problem and sorry for the issues. Content created between November 17 and launch day will be added soon and is in the process of being migrated.

 

Are you getting the yellow “Encode Error” (in the Events panel in your second screenshot) with different media as well? And following that, are you able to render and replace IMG_5936.MP4 without the time-remapping?

 

Does the issue persist if you first right-click > Restore Unrendered, and then also delete the render created in the chosen location and try again? There is a known bug that can cause the “error retrieving frame” warning when doing back-to-back Render and Replace on the same source file, where it is overwriting the previous render instead of creating a new one, and causing those issues—just want to rule that out.

 

Could you share your hardware information as well?


Really sorry for the frustration,
Dani

AndrewTheGreat
AndrewTheGreatAuthor
Known Participant
January 29, 2026

​@Dani_V. Hi, thanks for the clarification about my posts.

Yes, the error message happens randomly with different media. It happens at least once during my work (and once it has happened it won’t stop) so I basically stopped render-and-replacing at all. The problems with this function started to happen in Pr 25.6.x, I think, maybe earlier, but certainly > 25.4. And I have never had any of such issues in the earlier versions for 15 years. It’s not my computer, it’s not the drivers or the OS. I update regularly and my PC hasn’t changed for 3 years.

And you can see I could render the IMG_5936.MP4 but before that I had had this error with it too. It’s not file\project specific. 

“Does the issue persist if you first right-click > Restore Unrendered” - if I cannot render, I cannot unrender. Unrendering what has been rendered does not help. Once it has happened it stops working at all. It may then start working again with a different codec, but it will always happens again with that too. The starting point is the Sequence as the source and a Prores 4444 codec. It always happens with it first (I normally render and replace with it mostly)

Here’s a quick demo as of just now:

 

So far only purging all the media cache and restarting Pr helped - well, until the next time it happened again. But, yes, I removed the file that had been rendered and the render and replace feature worked again. But it broke in the next take.

So your guess about rewriting the same render file might be close.

 

My hardware: i7-14700K, RTX 4080, 64 Gb of ram, a system and a media files SSD disks (plus a HDD for archiving but it’s none of importance, I don’t have any media I work with on it, no cache or whatever either). 

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