AE created mogrt files on different Premiere Pro languages
mogrt files created in the german version of AE, have default parameter names in different language of PP.
For example: a slider created in AE [german] with the custom name "Distance", appears in PP [english] with the name "Schieberegler" (german for Slider).
So the whole template is more or less useless for the user.
But my client has editors all over the world that have to use this template.
@Marc Welschinger. The bug reported by Ludwig where Mogrt label names go back to default across app languages should be fixed since 17.0. Can you tell us a little bit more about your issue? As Dacia mentioned below, it should not be too difficult to make expressions work for multi language installations of Pr and Ae. You can hold down the alt/opt-key to pick whip and create your expression with index reference, or you can purchase the third party script ExpressionUniversalizer to run over your project after creation to ensure all expressions work across multiple languages (https://aescripts.com/expressionuniversalizer/).
Marc Welschinger commented
I have almost the same problem as Ludwig. But I created a mogrt file in the English version of AE and my clients use the mogrt in the English AND German versions of Premiere Pro.
It took me many days to create a well working mogrt for my client and now there is this bug. How can I solve this?
If you refer to properties by their matchname or index, instead of their localized name, your expressions will work in any language. You can hold down Alt when you pickwhip so the layer or effect is referenced by its index value (number based on order in the layer stack).
There is also a script available that will do that conversion automatically: https://aescripts.com/expressionuniversalizer/
Because the Dropdown menu is a PsuedoEffect under the hood, its matchname will update every time a change is made to the control so I like to run the Universalizer right before I export the Mogrt.
Karim Niazi commented
Programming languages should be universal. This is literally the only incident of something like this.
Imagine the internet-Protocolls were dependent on their region?
Who could be this stupid. This is absolute malpractice. Make it standard-english or implement a working universalizer (your dropdown menu's suffer from even worse failures as the german "Menü" leads to all sorts of failures even when importing in AE itself).
We’re taking a look at some ways to solve this for a future version, as we've had numerous similar reports from teams working across different geo-locations.
Thanks for your post,