PPro throws error message when importing an AeMoGRT (... "corrupt metadata" ...)
The full error messages reads as follows -
"The Motion Graphics Template has corrupt metadata and cannot be installed".
Is it possible to refresh the metadata in AE?
I have about 200 props in the EGP and will rather not have to rebuild the entire EGP again; especially when there's possibility of another breakdown.
Restarting AE didn't help. Importing the AEP into a blank AEP didn't help. Renaming the Comp didn't help.
A very strong possibility of this metadata mess seems to manifests itself with props in the EGP disappearing. They're still there since trying to re-populate the EGP with the missing prop throws an error stating the prop is already in the EGP. With such issues, closing and re-opening the Comp or EGP helps. However, user should have the ability to refresh/clean the metadata or something that helps to clean up the mess that starts when props disappear from the EGP.
Any assistance will be greatly appreciated.
Hi Dacia, I've been on 18.1 when the corrupted metadata error occurred in PPro, while importing a MoGRT. So, unfortunately the bug doesn't seem to have resolved itself.
Yesterday, the 'missing' props in the EGP issue appeared again. Fortunately, these came back after closing the EGP; populating it with another Essential Comp before reloading the seemingly problematic comp.
Thanks for the insight into the JSON and Expressions Universalizer. On my own initiative, I had resorted to the same workflow you suggested. However, it's not possible to adhere to such a workflow at all times. There will be the dreaded occasion(s) where I have to edit a Dropdown Menu that's been placed into the EGP. I now see that it may be prudent to first remove the DDM from the EGP first; edit the DDM; and then drop it back into the EGP – this seems to be a safer procedure, once the DDM is already in the EGP and the DDM requires an edit.
Please share more details as and when they become available because the 'missing' props issue still persists in 18.1.
When a Mogrt is exported from AE, a JSON file is created with a list of all of the controls and their default values. This is what Premiere Pro uses to create the UI in the Edit menu of the EGP when the AE Mogrt is selected in the timeline.
There were bugs that were causing this data to be inaccurate, and causing crashes in Premiere. Opening the project and re-exporting it out of 18.1 should fix any of these issues. It sounds like it worked for you.
Separately, the Expressions Universilizer changes dropdown menus to a match name for the effect. Dropdown menus are actually Pseudoeffects under the hood and this is why the Universalizer tool identifies them as such. An important thing to know about Pseudoeffects is that their match name changes, every time there is a change to the control itself, i.e. the number of items in the list or the names. A critical best practice is to make sure to run the Universalizer at the very end and after all changes have been made. The match name it generates will no longer be valid if you edit the control after running the script.
I can confirm that the insertion of "Pseudo ..." into a few of my Expressions was caused by the Expression Universalizer script. Do take note that this insertion/replacement only occurs to code referencing DropDownMenus.
Thanks for your reply Dacia. However, my AEP/MoGRT do not have JSON data. I'm also using 18.1.
To rectify my issue, I Saved the AEP anew. Duplicated the Comp. Populated the new/empty EGP. And all seems good and quite stable - but dang! Such a PITA.
Not certain if this is related but at the Slack MDA, I shared the following, on this same AEP -
This line -
para = thisComp.layer("Controller").effect("Bottom Text Paragraph Aligment")(1);
autoerroneously changes into this -
para = thisComp.layer("Controller").effect("Bottom Text Paragraph Aligment")("Pseudo/@@ur6zJKZbSvSGnSN/UNG1SQ");
Only occasionally does an Expression error appear. Has anyone seen this or similar and does someone have an idea what's causing this strange re-writing of Expressions?
So, AE is re-writing my Expression Code. YIKES! And in doing so, messes up the line of code and of course the entire Script. FYI, the line of Code points to a Dropdown Menu.
Any thoughts or insights into this very odd and destabilizing behavior in AE?
We fixed some bugs that had been baking in bad data into the JSONs of AE Mogrts for awhile. As you mentioned, it was related to some of the issues of disappearing controls. In a lot of cases, the mogrts were causing crashes in Premiere.
Simply, re-exporting the Mogrt out of AE version 18.0.1 or later should resolve the issue.
We also have a python script that will open the JSON and fix the bad metadata if that
doesn't work. Can you try re-exporting and seeing if that resolves the issue? I'll email you the script and instructions if that doesn't work.
Sorry for the inconvenience.