Characters in mogrt randomly display or render badly - now a useless workflow

Hi @Alain D.,

The ticket is still open for investigation.

Theresa

Hi,

@Theresa Rostek , is this bug fixed in the 25.2 Release? I just looked at the fixed bugs list and I did not see it in there...

TIA,

Alain

Hi @Alain D.,

Thanks for the thorough report and trying a few different things! I'm glad the bug seems to have resolved in the meantime for you, however the update is that there is a ticket is filed with the devs to investigate a fix that will truly take care of the problem. Thanks for your patience, I'll update this post when I have more information.

Cheers,
Theresa

Hi @Theresa Rostek ,

[UPDATED]

FYI - finally got to test this out again on a new project AND with a new mogrt done by a colleague. The interesting bit here is that this colleague had recycled the expression driving the font for each layer based on a language drop down that triggered this bug last year. Once in this new AE comp though, it turns out that for this mogrt (and AE Comp) there is no drop down selector and no "Controls" layer where this was set-up initially. So, in essence, the expression reports an error and reverts to font settings that were set on the layer directly...

I followed your workaround steps:
- I had the comp so I re-opened it in AE, disabled the Multi-Frame Rendering option

- Re-exported the mogrt

- Imported the mogrt in Premiere 

- As it was a first time, I did not have to ALT+Replace the mogrt in the sequence

At first everything seemed ok, but then after an update to the edit, I noticed the problem was now spreading like a virus. So maybe the Multi-Frame Rendering is part of the problem, but there is certainly another item in the equation that is triggering this.

And of course, as a problem never comes alone, the ALT+Replace (or unlink / link .aegraphic) does not work, so I have to rebuild everything from an updated mogrt where the expressions have been removed. [I'll do a few renders before celebrating].

[UPDATE]: I've done quite a few renders since this reply and I confirm all is well. But we'll truly celebrate when this bug is taken care of so that we can have our workflow operational again 😕😕

Any updates on your end?

Best,

Alain

Oh, ok! I'm glad I asked... 
And I just learned about this Alt+Replace trick on mogrts... Thanks.

Hey @Alain D. 

You'll need to change the Preference in AE, re-export the mogrt, alt-replace the mogrt in the Premiere Pro timeline, then render to AME see if the issue persists.

Theresa

Hi Theresa, thanks for the update. I'll report back when I can give that a shot (which won't happen this week). So, just to make sure I understand this workaround, one must ensure that the last time AE was fired up, that Preference setting was disabled, and that will now apply to any Premiere or AME render processing a mogrt?

Alain

Hi @Alain D. 

Sorry that updating this thread got lost in my notifications. There is a ticket open to investigate the fix.

While I was unable to get a reliable repro with your files so I can't test this myself. As a workaround, please try disabling Multi-Frame Rendering (After Effects Preferences > Memory & Performance) and exporting and see if the issue resolves for you.

Thanks,

Theresa

So FWIW, @Theresa Rostek , I confirm that after striping the mogrt from it's 4-font dropdown selection capability (which translates into making 4 individual mogrt, each hard coded to a single font), all has been well... but has of course caused havoc in our workflow. This is a serious showstopper for us and is yet one more experience of "let's think 4 or 5 times before engaging in such a workflow"...

Any update on the findings or possible fix?

Have received files and have begun investigating.

Thanks!
Theresa