clarification on MOGRT backwards compatibility

Forum|Forum|2 years ago
November 18, 2023
3 replies
1489 views

I make MOGRTs in After Effects for use in Premiere. I sell them on Gumroad and also use them on my own machine running the latest, or one-behind versions of both Pr and Ae.

A customer recently ran into an issue where a MOGRT I made was not able to work on their machine running Premiere 22.2. Error message as follows:

"This Motion Graphics template is not compatible with this versin of Premiere Pro. You must update to the latest version of Premiere Pro in order to use this template."

The user also mentioned they did not have After Effects installed, in case that's relevant.

I don't remember exactly which version I made the MOGRT in, but it was some time in the 2023 cycle of the Adobe Suite. It has always worked on my machine running the 2023 version of Premiere and now in the 24.0.0 version too.

Hoping to get some clarification on why this particular MOGRT has no backwards compatibility with 22.2 and hopefully some best practices to make MOGRTs as evergreen as possible.

Any ideas?

This topic has been closed for replies.

Theresa Rostek

Community Manager

Mogrts have always been forwards compatible, but not backwards compatible.

If the customer is receiving that dialog in Premiere Pro 2022x, then it was made in After Effects 2023x. The customer would need to update their Premiere Pro to 2023 to use it, or you could backsave your After Effects project to 2022 and export out a 2022 version of that mogrt for them.

If a problem still persists after doing this, then there could be an issue with the mogrt itself, please let me know so I can diagnose it.

Cheers,

Theresa

V

videowizard.ioAuthor

Known Participant

Thanks Theresa, backsaving from earlier version of AE seems like the move should it arise in the future.

R Neil Haugen

Legend

jstrawn (as pinged by Ann) or @DaciaSaenz can give the full technical detail.

But ... it's pretty clear the mogrt 'system' has been expanded continuously, since it initially was created in what, 2016 or so? So I would expect older versions might not be able to use newer version products with newer code capabilities.

Everyone's mileage always varies ...