Skip to main content
A
Alain D.
Known Participant
January 24, 2025

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

  • January 24, 2025
  • 27 replies
  • 1807 views

We developped this very useful mogrt in AE-CC2024 that gave us a pretty slick workflow, but since mid 2024, it's become useless because of the randomness of the problem. I've seen many posts on the web reporting similar problems in mogrt workflows even before CC2024, with no clear fixes. It's an AE comp, exported as a mogrt, that enables the treatment of text captions in 4 languages (English, Chinese, Japanese and Korean). It also provides color highlighting controls for 5 groups of characters and with the flip of a switch, re-scales/re-positions it all to fit in tall format. It worked fine for a few 2024.xx versions until it suddenly started showing the following problems in the native wide format:

  • Characters will randomly show as "Regular" even though the font "under the hood" is MyFont-Bold.ttf
  • The problem may not appear on-screen, but will be in the exported copy (via AME or PrPro exports)
  • Quit/relaunch, you have different characters that now show the problem
  • CC2025 shows the same issues; CC2025 is actually even worse from a workflow perspective as you can't "TAB" from one field to another. All the numerical fields that are used to determine the start/end positions to specify a specific color fill are not "detected" by the "TAB" key. You must mouse/pen-click it to access the numerical field.

 

What's been done:

  • All fonts are .ttf, always were, so no change there
  • The system has been completely wiped for the CC2025 install. Everything reinstalled from scratch, Windows 11 + all Adobe apps, vanilla install
  • Re-opened the CC2024 mogrt into AE CC2025, re-exported it as a mogrt

 

System's details:

  • Windows 11 Pro for WS Version 10.0.26100 Build 26100
  • 2x Intel(R) Xeon(R) Gold 6136 CPU @ 3.00GHz, 2993 Mhz, 12 Core(s), 24 Logical Processor(s)
  • 192 GB Memory
  • Graphics: NVidia GeForce RTX 4070 Ti, driver 566.36 (December 10)

 

Many hours have been spent developping and tweaking the functionnality of this mogrt, currently rebuilding from scratch is not an option, especially without knowing what triggers the problem and not knowing how/when it could make its way back... 

 

Thanks for any input...

    27 replies

    Theresa Rostek
    Community Manager
    Theresa RostekCommunity Manager
    Community Manager
    May 12, 2025

    That's really good to know, and when you can get to testing the original file, it's much appreciated.

    Motion Graphics, Premiere Pro
    A
    Alain D.Author
    Known Participant
    May 12, 2025

    Agreed, but this new project is based off new mogrts that were designed off the same setFont mechanics in the AE comp... But yeah, sure, I have like a half dozen of old projects that were generating the problem. This may only happen towards Friday though. 

    Theresa Rostek
    Community Manager
    Theresa RostekCommunity Manager
    Community Manager
    May 12, 2025

    🤞

     

    Though, it looks like the issue might have been with setFont, which your original project is using.

     

    So when you're able (and thank you so much for the testing you've already done), testing the project you had sent originally to see if the issue reproduces or not can show us if we're on the right track.

     

    Thanks again!
    Theresa

     

    Motion Graphics, Premiere Pro
    A
    Alain D.Author
    Known Participant
    May 12, 2025

    Update: a tiny bit of hope. I just want to say that I did a partial test using the Beta version on Friday (May 9) with the new mogrt components that have been on the backburner since January now because of this bug... I was able to quickly replicate the workflow, e.g. build an English version, then duplicate it and generate the Chinese version. I then exported the 2 as a foreground export (not via AME). Nothing showed up abnormal in the viewport while I worked and the exports were fine.

    I say "partial" because everything was rebuilt by hand and in a much slower process because I could not see my 2025 hotkeys, and being limited in the spare time I had, that's what I could handle with so much mouse clicking 😉

    After the fact, I realized that I did not test the tab fix! I guess I got into the habit of working around it...

    Theresa Rostek
    Community Manager
    Theresa RostekCommunity Manager
    Community Manager
    May 8, 2025

    Updating status

    Motion Graphics, Premiere Pro
    Theresa Rostek
    Community Manager
    Theresa RostekCommunity Manager
    Community Manager
    May 8, 2025

    Hi @Alain D.,

     

    You can run beta and release versions side by side. You can make a copy of your project to make sure nothing happens to your original, or just be sure to not save when quitting the app.

     

    Also, tabbing behavior has been fixed in the beta. 

     

    Theresa

    Motion Graphics, Premiere Pro
      A
      Alain D.Author
      Known Participant
      May 8, 2025

      Hi Teresa, thanks for following up. I'm a little late to reply because I had just stopped looking at this thread after a few days without any response.

       

      I never dipped my toes in the beta version of Premiere. I assume one must duplicate projects and run them in parallel, between the released and beta versions?

       

      Have a good one,

       

      Alain

      Theresa Rostek
      Community Manager
      Theresa RostekCommunity Manager
      Community Manager
      May 5, 2025

      Hi @Alain D.,

       

      I am sorry for the prolonged frustration while the fix was being worked on.

       

      There is a speculative fix available in the beta (as in, I can't reproduce the issue, so I can't prove the fix is successful), could you give it a try and let us know if it's working as you expect?

       

      Thanks,

      Theresa

      Motion Graphics, Premiere Pro
      A
      Alain D.Author
      Known Participant
      April 25, 2025

      Hi @Theresa Rostek ,

       

      Sorry for poking this thread again but this bug is still alive and terribly intrusive in our workflow. A lot more than the audio drop out bug/warning that's caused a stir in recent weeks.

      So it appears that our earlier mitigation measures are just not enough. With CC2025.2, I now regularly see improperly displayed fonts in the viewport, but the renders are typically fine. But not this week: I had a timeline that was A-OK in the viewport, but once rendered, one character was missing. Which is difficult to catch when you're QC'ing a Korean version output...

      We JUST CAN'T RELY on the mogrt/aegraphic workflow path anymore. And the proposed work around is terribly crippling for us, but now it's also not 100% guaranteed to fix all instances of the problem. We have new design elements that we've pushed back for implementation because they involve language/font dropdowns in the mogrts.

      Tell me this is a priority, please. Can we bump this up a notch?

      A
      Alain D.Author
      Known Participant
      April 3, 2025

      Oh dear... All right, thanks for getting back.

      Best,

       

      Alain

       

      Show more replies
      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices