Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
2

P: MOGRT "Render and Replace" shows incorrect result and replaces files

Participant ,
Sep 23, 2025 Sep 23, 2025

Using MOGRT in Timeline and changes e.g. text value. "Render and Replace" renders .mov-File with default values! After "Restore Unrendered" and again "Render an Replace" rendered .mov-File is correct. Using MOGRT multiply times in timeline "Render an Replace" always use same filename (not increasing) and replace files thats leads to error retrieving frames.

Steps to reproduce: 

  1. Import MOGRT via Graphics Templates-Panel multiple times to Timeline
  2. Change e.g. text value
  3. Render and Replace (Source: Sequnece, Format: Quicktime, Prest: Match Source - Apple ProRes444, Location: Next to Original Media) - select clip for clip (not selct mulitple clips)
  • Result: Renderd .mov-File shows wrong (default) values, all rendered .movs gets same filename, error retrieving frame 
  • Expected result: Rendered .mov-File show right values, multiple files gets increasing filenaming

V25.5V25.5V25.3V25.3

Bug exists in Version 25.5 and still in Beta 25.6.0 (74) not in Version 25.3

 

System:

Mac Studio 2023 (M2 Max), OS Sequoia 15.7, Premiere Pro 25.5.0 (13)

Bug Acknowledged
TOPICS
Graphics
182
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Pinned Reply

Adobe Employee , Sep 23, 2025 Sep 23, 2025

HI @Det Scholz -  Thank you for reporting this. I was able to reproduce the issue and have filed a bug report. We’ll update this thread as soon as we have more information to share.

Status Acknowledged
Translate
12 Comments
Adobe Employee ,
Sep 23, 2025 Sep 23, 2025

Hi @Det Scholz -  Thanks for submitting your bug report. We need a few more details to try to help with the issue.

 

Where is your footage stored?

Does the same thing happen if you copy a mogrt to your internal hard drive?

Sorry for the frustration.

Status Needs More Info
Translate
Report
Participant ,
Sep 23, 2025 Sep 23, 2025

Hey @jamieclarke ,

same error when setting scratch-disk to the local document-folder!

Bug is also seen in V25.4.1. So we will roll back to V25.3 to be safe with our graphics.

Translate
Report
Adobe Employee ,
Sep 23, 2025 Sep 23, 2025

Hi @Det Scholz - Render and Replace isn’t determined by the scratch disk, but by the location of your media. Could you try moving your media to your internal hard drive and let us know if the issue persists?

Translate
Report
Participant ,
Sep 23, 2025 Sep 23, 2025

I don't quite understand what you mean. When I import a MOGRT, it is unzipped and imported into the (local) scratch directory.
I have now copied the original MOGRT file to the local disk and imported it into Premiere.
The error occurs here as well. I think, it's not a local / server issue

Translate
Report
Adobe Employee ,
Sep 23, 2025 Sep 23, 2025

Hi @Det Scholz -  Where did you get the mogrt?  Can you email the mogrt to jamiec@adobe.com 

Translate
Report
Adobe Employee ,
Sep 23, 2025 Sep 23, 2025

HI @Det Scholz -  Thank you for reporting this. I was able to reproduce the issue and have filed a bug report. We’ll update this thread as soon as we have more information to share.

Status Acknowledged
Translate
Report
Community Expert ,
Sep 23, 2025 Sep 23, 2025

If you add video effects to a clip and "Render and Replace" with the Include Video Effects box checked, the resulting rendered clip will retain the video effects albeit greyed out with a (Rendered) note next to them. Restoring the unrendered versions will unlock the effects and allow them to be adjusted again.

 

Doing the same process on an AUDIO clip does not have the same results. After Render and Replace the audio effects are stripped out, and resoring the clip does not return the effects to the clip; they are gone.

 

A client has reported this in v24 and I have reproduced the issue in 25.5. Only workaround is to stack the rendered clip in the timeline so that the effects are at least maintained when the clip is returned to it's unrendered state (useful for an audio turnover at least)

Mac Studios (Sonoma and Sequioa), v24.? and v25.5. Audio is embedded in ProRes clips or separate WAV files.

-------------------------------------------------------------------------
JVK | Editor/Designer/Software Instructor. Pr, Ae, Ch, Ps, Ai, Id
Translate
Report
LEGEND ,
Sep 23, 2025 Sep 23, 2025

That's an ouch! Thanks for posting John, I'll try to check tomorrow on PC ...

Translate
Report
Community Expert ,
Sep 23, 2025 Sep 23, 2025

Yes, thanks Neil. Please let me know if you can replicate this.

-------------------------------------------------------------------------
JVK | Editor/Designer/Software Instructor. Pr, Ae, Ch, Ps, Ai, Id
Translate
Report
Adobe Employee ,
Sep 24, 2025 Sep 24, 2025

Hi John,

Thanks for bringing this to our notice. I am able to reproduce this behaviour. I will get it checked by our team.

 

Regards,

Sumeet

Translate
Report
LEGEND ,
Sep 24, 2025 Sep 24, 2025

Okay, this is very very weird.

 

I applied both several things in the ESP and then added a Parametric EQ to the clip ... then did a render & replace to ProRes422 sequence/include effects ... and the effects are all still visible in both the ECP and the ESP ... but the clip plays without any of them actually applied, and is very quiet.

 

Again, select the r&r clip, the ECP and the ESP both show the effects I had applied as-was.

 

BUT ... the waveform on the clip is back to the very low input state, and clearly no audio effects were applied or are being applied now.

 

Even though they show with the clip.

 

RNeilHaugen_0-1758755256884.png

 

Translate
Report
Participant ,
Sep 28, 2025 Sep 28, 2025
LATEST

I have a similar problem here. Every instance of a MOGRT prerendered via "render and replace" results in the same renderfile (same name) hence previously r&r-rendered instances are replaced with the latest rendering. Haven't had this issues about two months ago(?). Good to know, that this seems to be a bug.

Translate
Report