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

    Show previous replies
    Theresa Rostek
    Community Manager
    Theresa RostekCommunity Manager
    Community Manager
    April 3, 2025

    Hi @Alain D.,

     

    The ticket is still open for investigation.

     

    Theresa

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

    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

    Theresa Rostek
    Community Manager
    Theresa RostekCommunity Manager
    Community Manager
    March 21, 2025

    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

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

      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

      A
      Alain D.Author
      Known Participant
      February 26, 2025

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

      Theresa Rostek
      Community Manager
      Theresa RostekCommunity Manager
      Community Manager
      February 26, 2025

      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

      Motion Graphics, Premiere Pro
      A
      Alain D.Author
      Known Participant
      February 26, 2025

      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

      Theresa Rostek
      Community Manager
      Theresa RostekCommunity Manager
      Community Manager
      February 25, 2025

      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

      Motion Graphics, Premiere Pro
        A
        Alain D.Author
        Known Participant
        February 24, 2025

        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?

        Theresa Rostek
        Community Manager
        Theresa RostekCommunity Manager
        Community Manager
        January 28, 2025

        Have received files and have begun investigating.

        Thanks!
        Theresa

        Motion Graphics, Premiere Pro
          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