MOGRTs Stop Loading at 15%

[ChrisKirbyWTNH]

Hi. I'm working in Adobe Premiere v23.6 on a Windows machine and MOGRTs from the Essential Graphics panel won't load anymore. They all get stuck at 15% regardless of whether they're the stock ones that come pre-installed with Premiere, or ones I built myself in After Effects. After some reserach, I found this was a problem several years ago, but I can't find any fixes for the most recent version of Premiere. Any suggestions?

[DaciaSaenz]

Hi @ChrisKirbyWTNH, 

That is super frustrating. Would you mind checking a few things for me? 

• Does it happen in 22.6?
• Does it happen in the latest Premiere Pro Beta?
• Do you have After Effects installed? 
  • If so what version? 
• Can you please share a screenshot of your scratch disk settings? 
• Do you have enough memory on disk? 
• Can you open the Console (CTRL + F12) and select "Console View" from the Hamburger Menu of that panel?
  • Next apply a Mogrt to the timeline and look for something that says "MOTION-GRAPHICS-TEMPLATE" 
  • Please take a screenshot of what it says after that statement and send to me as well. 

Thanks so much! I hope we can get you back on track soon. 

[ChrisKirbyWTNH]

I re-installed v22.6.4 and the mogrts work correctly.

I have not tried installing the latest Premiere Pro Beta - I'm on v23.6.

I have AE and Media Encoder  v 23.6 installed.

I have 250GB of space on my scratch disc.

Screenshot of Media Cache location attached.

Screenshot of GetAVICodecs error message attached.

Screenshot of video card message attached.

Console View screenshot attached.

[DaciaSaenz]

Thanks the low-level exception looks very interesting. That might be of interest ...

Let me ask devs about that and in the meantime, let me clarify some of the info that I'm looking for that didn't get answered: 

What version of AE is installed on your system?

When you add the Mogrt to the timeline, do you ever see a message in the Console that looks like this? 

The scratch disk settings I'm asking for are in your Project Settings and look something like this: (this is the Mac version)

Windows OS has a very frustrating limitation of 250 characters per file path. The Mogrt cannot be unzipped to be used in the project if the Mogrt scratch disk folder is nested in a series of folders that would push the unzipped mogrt file path to more than 250 characters. 

Have you tried updating your Drivers? 

Can you try to install the latest Beta and see if the issue also repro's there? You can download from Creative Cloud Desktop app and it won't interfere with any of your other installs of Premiere Pro. 

Can you add any other footage to the timeline? 

[DaciaSaenz]

@ChrisKirbyWTNH , 

From devs regarding the low-level exception

"That means that AE is having a problem with some Windows codec they have installed." 

In this case AELib which is a tiny inception version of AE inside of PR that renders AE Mogrts is not ok with one of those codes and is failing to launch / stalling the opening of the AE Mogrt. 

Here is a community thread about the same low-level exception blocking renders more generally. Sounds like a Logitech camera codec can cause this issue. Can you try removing that and see if that helps?
https://community.adobe.com/t5/premiere-pro-discussions/low-level-exception-ff-vfw-dll-get-avi-codec... 
I found this 

[ChrisKirbyWTNH]

Good morning.

I have AE v23.6 installed.

I do not get any error message in the Console window when trying to add a mogrt to the timeline.

I can add video to the timeline without error.

The mogrt does not exceed 250 characters.

Scratch disc setting attached.

I will have to get IT involved to ask about drivers and Logitech cameras. I do have a Logitech webcam attached, but as far as I know, it was plug-and-play - no driver necessary. However, I unplugged the webcam today to see if it made any difference, and I still got the same errors.

[DaciaSaenz]

Hi @ChrisKirbyWTNH , 

Thanks for the additional info. I don't think unplugging the webcam is enough. The issue is in whatever Logitech Codec is installed + 23.6 having a conflict 😞 

If this works on your system in 22.6 and not 23.6 with the same codecs installed then surely there is a bug here. But it would be great to confirm if your mogrts get back to functional in 23.6 without that codec. In the meantime, I'll see if I can get my system in a similar state to reproduce the error. 

Thanks so much,

Dacia 

[ChrisKirbyWTNH]

I deleted the 2 ff_vfw.dll codecs I found. The low-level GetAVICodec error message went away, but mogrts will won't load into timeline.

[DaciaSaenz]

😭

whale...dang. we can rule that out. 

ok.. can you please send me your mogrts so I can try on my end? 

Dm me a link to WeTransfer or Dropbox or whatever you prefer if they are proprietary. 

Can you also send me a screen recording of what is happening when you try and add a Mogrt to the sequence so I can see if I pick up on anything we might be missing?

Thanks,

[ChrisKirbyWTNH]

It's happening when I try using a mogrt I made, but it's also happening to all of the mogrts that ship with Premiere. I would gladly send you the mogrt I built, but I don't know how to DM you. Can you see my Nexstar email on your end - you can open a direct line of conversation there if you'd like. Thank you - I appreciate you troubleshooting this with me.

[ChrisKirbyWTNH]

Hello again. Our IT guy reinstalled the NVIDIA drivers today and it looks like mogrts are working again. They were weird at first, but then seemed to smooth out, so I'm cautiously optomistic that the driver was the culprit and things should go back to normal now??? Finger's crossed. I'll reply again if anything changes. 

[DaciaSaenz]

YAY!!! this is great news!!!! 

Those driver updates can either help or hurt sometimes but I'm happy to hear that you're back on track. 

That's so weird though. Usually a graphics card issue would lead to render problems like a black frame in the Program Monitor and not blocking the unpacking / adding a of the mogrt to the timeline. 🤔

How interesting!!! This is why I love computers. These robots are always keeping me on my toes! 

Please let me know if anything else comes up and thanks for your help in troubleshooting! Crossing my fingers too! 

Cheers,

[DaciaSaenz · Accepted solution]

Updating NVIDIA drivers resolved the issue.