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

Cool! Sounds like a good test. 🙂

@Theresa Rostek , hi. FWIW, here's a potential trigger factor for the bug...

After sending you my fonts and mogrt, I spent another couple of hours trying all kinds of things. The first thing I did was to swap the 3 Asian fonts with standard ones. Something like Arial Narrow Bold, Avenir Next Bold and BebasNeue Medium Bold if I recall.

Test the EG panel mechanics in AE, all is well, so I export the mogrt. The problem showed up immediately in Premiere when I switched the font to Avenir. Swing back to AE and I noticed that Avenir font had that square brackets and "/Type 1" suffix? Turns out the "-Bold" variant of the font I was calling was not installed on the computer. So I used a variant that was installed, lost the brackets, re-exported the mogrt and all was well in Premiere.

So, just throwing out a theory: could one "bad" font make the whole mogrt process derail? Also, note that the English and Korean associated fonts have almost never failed in the process, but the Chinese and Japanese ones are pretty much affected by the bug 95% of the time.

Cheers,

Alain

Thanks @Theresa Rostek !
DM sent.

Regards,

Alain

Hi @Alain D.,

Thanks for your report and sorry you're running into issues! I've seen several reports and have run into this one myself inconsistently and I'd love to be able to understand it better so we can fix it.

Are you able to share the mogrt with me? (Please DM me a link from Google Drive/Dropbox/Hightail/etc to it) Also, if you can provide a link to where I can download/license the problematic font will be helpful as well.

Thanks,

Theresa

@AnnikaKoenig , @Jarle Leirpoll 

I read up Annika's answer as suggested by Stan. I don't think that article is related to my problem as, on my end, it's only individual characters here and there that go bonkers. The expression-driven fonts tied to my language drop down in the mogrt are bold, and non-bolded, random characters show up here and there. I should probably state as well that it's typically on Asian fonts, although I've seen it on standard fonts too.

General workflow is this:

• Build my English version duplicating the mogrt as many times as needed, enter / treat the copy as needed. The defaulted language is English on a non-Asian font.
• Duplicate the sequence to make the Japanese version for example. Toggle the language drop down in each mogrt to "Japanese", which under the hood loads up the proper font.
• Enter / tweak the copy as needed.
• Rince & repeat for the other 2 Asian languages.

This used to be done and over with at this point, but not anymore.

Again, I'm no AE-expressions expert, I tip-toed into it for this mogrt, but this set-up was working and suddenly broke. That being said, I'm not too savvy on the expression terminology, so Annika's cue on referring to "index" rather than "parameters" in the written expressions was worth a check on my side.

Everything I wrote was "picked whipped" so that the expressions wrote themselves up for the greater part. Annika, can you clarify what you mean by referring to "Parameters"? On my end, my expressions were referring to actual layer names instead of their index numbers; I changed the few instances that I had, but this did not make a difference, same bug/outcome.

The problem shows up in Premiere, but the same workflow directly in AE appears A-OK - at least visually, I did not import my timeline in AE to work it up from there. And then even if the Premiere viewer looks ok, the rendered output may show the problem.

Wasted another full day debugging this... My next step is to try the same workflow, but just with standard fonts (non-Asian). See if that makes a difference.

Pic attached to show the issue + mogrt panel

Thanks --Alain

Thanks @Stan Jones ! I appreciate the input. (and thanks for the TAB confirmation).

I'll admit I live in a bilingual country (French/English), but apart from having 2 Windows keyboard mappings (English US and French Canada), everything has always been installed in English, from Windows, Microsoft, etc., all the way into all Adobe apps. So I'm not quite sure how index vs parameter in my expressions would matter? I mean, assuming using the parameters approach is a no-no in expressions to safeguard against language issues when the mogrt gets used on another box, I still don't get why I would be affected by it since all Adobe apps have always been installed in their native English versions?

I'm no expressions guru either, so I'll have to read up on index vs parameters. I hacked my way in expresssions territory watching YouTube stuff, so I'm not quite sure what I did. I recall there was array stuff for some, but I'd have to dig back into it. But I can certify this worked A-1 up until mid/late 2024.

Alain

@Alain D.,

Check this for one area to cover:

https://community.adobe.com/t5/premiere-pro-discussions/sequence-problem-with-premiere-amp-amp-media-encoder/m-p/15091920#M549164

@AnnikaKoenig @Jarle Leirpoll 

The TAB issue is in a bug report.

Stan