Skip to main content
Participating Frequently
July 18, 2025
Question

Automation Blocks MOGRT UI not updating in Premiere 2025

  • July 18, 2025
  • 3 replies
  • 526 views

The scripts I have created with Automation Blocks are quickly becoming very essential to my companies workflow, so thank you for creating such an amazing tool!!!

 

Most of my development has been in Premiere 2024, and they work flawlessly in that version, but when using in 2025 scripts dealing with updating the text in a mogrt is not working correctly.

The actual graphic in program panel will update according to user input but, the text field in the MOGRT UI will either be blank, or stay what it was previously. If you click into the MOGRT text field, then the on screen graphic will update but not the text field in the UI. Then if you click on the text field, the on screen text with revert to match what's displayed in the UI. 

I have attached a screencap of the issue as well.

 

Things I have done to trouble shoot include:

Exporting a new mogrt with AE 2025, the mogrt I was originally testing with was created in 2024, so I tried out exporting a new one from AE 2025, and I got the same results

Saving a copy of my script from within Automation Blocks 2025, same idea as above thinking there may be version compatibility issues, no success

 

Has anyone encountered this issue/know why this is happening?

Any help is very appreciated!!

3 replies

Participating Frequently
January 27, 2026

@Mathias Moehl  ​@Kevin-Monahan 

This issue persists in both 2025 and 2026. I test it with each new update and have noticed that rather than (from initial post):

The actual graphic in program panel will update according to user input, but the text field in the MOGRT UI will either be blank, or stay what it was previously. 

The info still displays correctly in the Text panel, but the text fields in the Properties Panel revert to the template placeholder info like they are being reset completely. 

Any escalation you can do on your end would be much appreciated!

Mathias Moehl
Community Expert
Community Expert
July 19, 2025

Thanks for reporting, this sounds like a bug in Premiere Pro. I will ask  at Adobe if there is a known issue and a workaround.

In the meantime: If you close and reopen the project (or maybe just the panel) do the wrong values stay in the Properties panel? If yoou render the video, are the values in the Properties panel rendered or the texts which Automation Blocks has set?


Mathias Möhl - Developer of tools like BeatEdit and Automation Blocks for Premiere Pro and After Effects
Mathias Moehl
Community Expert
Community Expert
July 22, 2025

I just got a confirmation from Adobe and they are aware of the issue:

"We're reasonably sure that the problem is in application UI updating in response to the API call, and not within the API itself..."
So it is not an issue. with Automation Blocks or the Pr scripting engine, but with the Premiere Pro UI. 

Mathias Möhl - Developer of tools like BeatEdit and Automation Blocks for Premiere Pro and After Effects
Participating Frequently
July 22, 2025

I figured it had to be on Adobe's end. Thank you for looking into this. I'm very happy to know it's not an issue with AB or my scripts!!

 

To answer previous question's, it will render out with the correct values if the properties panel is not touched. I tested out closing/reopring the panel as well as the project, and for both, the fields in property panel were empty.

 

PS sorry for the late reply!! Do you think this is something they will actually address within the next update? This is literally the last thing stopping my team from moving to 2025

Kevin-Monahan
Community Manager
Community Manager
July 19, 2025

Hi Ailia,

Thanks for your post and for tagging it appropriately. I hope that an Adobe Expert will drop by soon with assistance. Thanks for your patience.

 

Take Care,

Kevin

 

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
Participating Frequently
September 17, 2025

Hello, I am checking in to see if there is any update on this? It still has not been fixed with the most recent update of premiere 2025