Copy link to clipboard
Copied
Hello All
Premiere Pro recenetly updated to 23. version and two errors really frustrating
1. GPU render error all the times..... tried to troublshoot but could not resolve
2. also Mercury Playback engine greyed out, I cannot change ?
I have M1 Mac 2020
please help someone to resolve this issue
Thanks
Copy link to clipboard
Copied
Here's the issue:
The renderer in the Apple Silicon-native version of Premiere Pro is permanently fixed/locked to the "Mercury Playback Engine GPU Acceleration (Metal)" mode, and cannot be changed at all - not even to the software-only mode. Unfortunately, it is also the default behavior in Adobe programs for all Apple Silicon Macs. The only way to force the "software only" rendering mode would be to force Premiere to run in Intel mode (by launching the Adobe Creative Cloud desktop app, and then clicking on the three dots on the Premiere Pro line in the program, and clicking on the "Open (Intel version)" line.
Copy link to clipboard
Copied
Thank you very much for your guidance and do you have an idea how I can solve gpu render issue ?
thanks
FRAZ
Copy link to clipboard
Copied
Which version of macOS are you running? And have you ever updated your Mac's software?
Copy link to clipboard
Copied
Upaded to Ventura 13.1 just a couple days before
Copy link to clipboard
Copied
Did you find any answers? I'm having the same problem
Copy link to clipboard
Copied
Hi joeycooool,
Thanks for the post. Sorry, you are having the same trouble. First, try rolling back to v.23.0. If that is not working, give us details about your media, sequence settings, and any GPU-accelerated effects you use. I think we can help you from there. The M1 is an excellent platform; I have a MacBook Pro with 16 GB RAM. What machine do you have? What are the specs?
Thanks,
Kevin
Copy link to clipboard
Copied
Hi! Thank you for the answer.
I've tried rolling back to v.23.0, reinstall the app, disable effects, change sequences, run the intel version and still nothing. I have the macbook M1 with 16gb ram and I'm using 4k 1920x1080 25fps footage on a sequence that matches, the video is about an hour long.
I've never had a problem before but last week I installed OS Ventura and haven't been able to render it since.
Copy link to clipboard
Copied
Hi, Joey,
Oh, man, I've been in your shoes before. You say, "4K footage" but your sequence settings are HD? What camera did you use to shoot the footage? Format info? I hope we can help and sorry for the hassle.
Thanks,
Kevin
Copy link to clipboard
Copied
Yes. I shot 4K but I'm using a 1080p sequence to take advantage of the extra "zoom" I can get. It was shot with a sony a7iii, AVCH, 4K, 25fps and the file formart is mp4.
Copy link to clipboard
Copied
Hello
Any project that is created in older version of Premiere 2022 is creating problem when opened in 2023 but new project created from scratch in the new version seems ok for now!
Copy link to clipboard
Copied
Hi!
Unfortunatly it was already created from scratch in the 2023 version 😕
Copy link to clipboard
Copied
Did you ever end up figuring out how to resolve the issue? I'm experiencing the same thing right now on an M2 Macbook Pro.
Copy link to clipboard
Copied
Hi! Unfortunately I did not, it just stopped happening. Hope it goes back to normal to you soon!
Copy link to clipboard
Copied
Hi,
Is the 4K footage from your Sony in 10-bit at 4:2:2? If so, try transcoding to any flavor or ProRes. That may solve it.
Thanks,
Kevin
Copy link to clipboard
Copied
Hi @Kevin-Monahan
I'm facing the same issue "This effect requires GPU acceleration" and I'm using the updated version of Pr Pro (V 24.1.0) and I'm using macbook pro M2 chip with 16 gb ram.
Hope you revert soon!
Copy link to clipboard
Copied
Thanks for the message. I think your issue is different than that of the OP. You can work around this error message. You must change the order of the VR video effect in the stack of effects in the Effect Controls tab. More info here: https://community.adobe.com/t5/premiere-pro-discussions/faq-avoiding-warnings-using-vr-effects/m-p/1...
I hope that changing the order of your video effects solves the issue. Please return and let us know how it goes. Sorry for the problem.
Thanks,
Kevin
Copy link to clipboard
Copied
Hello, Mr. Kevin. I'm running an M3 Max with 2TB hard drive and 128MB RAM. I experience continuous force quits required, image below. Most of the footage is 4K, but I am exporting at 420 just to review the project. I have been seeking solutions for days. Same error in Premiere and AME. Always about 85-95% through export. Can you help me please? Ugh... can't attach image. It says: Force Quit Applications (only premiere and finder are open). Your system has run out of application memory. Roughly 227GB premiere or AME and 92.8 MB Finder. Thank you.
Copy link to clipboard
Copied
Hi ST!LL FR@NK,
Thanks for the message. If you are running out of memory, run a test to see if importing your project into a brand new project will help. That is one way people try when a project acts that way. I hope the advice helps.
Thanks,
Kevin
Copy link to clipboard
Copied
Any update on this? Adobe this is terrible customer service. Extremely frustrating that you are aware of this issue and still no resolution.
Copy link to clipboard
Copied
Sorry you are having problems with your Mac. Can you let us know more about your system and workflow? For example, what system do you have? What kind of footage? Are you performing any specific task where you experience problems? Please let us know. I hope the community can assist.
Thanks,
Kevin
Copy link to clipboard
Copied
Kevin, I'm having the same issue in Ppro Beta with effects/transitions applied to a PSD clip.
Brand new MacBook Pro M2, trying to add default effects to clips, and getting render errors. First I've ever seen.
See screenshots for simple brush strokes fx applied to a .psd clip and getting that render error. It works on the video clip. Can I just not do this to PSD clips? Thanks
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Sorry about that, @SkyTygr. Is the same thing occurring in 23.6?
Thanks,
Kevin