Participating Frequently

Crash after adding MOGRT from libraries panel to timeline [PP V25 ARM64]

Forum|Forum|1 year ago
October 26, 2024
3 replies
497 views

Hi,

I was thrilled to see that I could finally install the latest version of Premiere Pro on my ARM64 laptop, where untill now I could only run an older version. It's still not native, but at least I can now open projects that were made on regular X64 machines running the latest version of Premiere Pro.

However, I encountered the following bug: everytime when I want to add a MOGRT from the libraries panel to my sequence, Premiere will crash the moment I start playback or moving around the timeline. Tried to restart several times, tried it in different projects, still the same.

I used to add graphics from the library part of the Essential Graphics panel, however, my libraries don't seem to load there. I suspect it is replaced by the new libraries panel, but I can't use the MOGRTS right now.

This topic has been closed for replies.

P

Precious_Twinkle5DFEAuthor

Participating Frequently

Hi,

I installed both the Premiere Pro 25.1 update as the 25.2 bèta version. I was hoping to see that this issue would be resolved, but unfortunately it's not. I need the graphic templates in almost all of my projects, so basicly I can't use Premiere Pro on my ARM laptop to edit at all. Even the default Premiere Pro graphics will cause instant crash at playback.

Since the bug is still there in the new version, when can we expect a solution for this very basic feature to work?

Kind regards,

P

Precious_Twinkle5DFEAuthor

Participating Frequently

Hi Jamie,

Thanks for your reply. I understand the libraries are not avaiable from the Essential Graphics Panel, that is what I already concluded. However, I do see the libraries from the (new I think?) libraries panel. I can even add the MOGRT file from there to my timeline. But then, Premiere crashes. If it's the same underlying bug, perhaps it's good to clarify this on the system requirements page you included in your reply.

Is there any insight on when this bug will be fixed?