Yesterday, I was editing fine in Adobe 2020 without any issues. Now, when I try to launch the program, it says, "Premiere Pro could not find any capable video play modules. Please update your video display drivers and start again." If I restart my computer, sometimes, the program will launch fine and I can edit. But most of the time, I get this error. And, it all started this morning without any recent updates that I'm aware of. And, when it closes out, my Mac OS says, "Adobe Premiere Pro" has crashed. Not sure what's happening. There was no change to my hardware.
I've been having this same issue on my brand new 2019 Mac Pro as well. Super frustrating. I have found that if I reboot my machine and then open Premiere right away, it'll work. If I close up Premiere though and try to open, she'll stop working. Basically I have to reboot like 3 times a day. Another issue I've noticed is that occasionally Encoder will stop using the GPU to render (it greys out) and will use Software encoding instead...again, until you reboot. %^#$^!
Really hoping Adobe gets this sorted out for all of us.
Yes, that was also happening to me. I could reboot and immediatley launch Premiere. Then, when I would forget and quit, it wouldn't launch any more. Today, however, it will not start up at all any more. Just crashes on launch.
No problem. Just to add: on restart after PU removed completely (unsurprisingly) I can confirm that PP2020 and AE2020 and Prelude 2020 all launch fine (and very quickly too, I might add).
Try creating a Root User account and then logging into your system as Root - https://support.apple.com/en-us/HT204012
If you're able to work without errors in Root User mode, then the problem has something to do with user permissions. If you're getting the same error when logged in as Root, then it's not a permissions issue. Don't forget to disable Root User account after trying this test.
I enabled Root User and tried to launch the program, and it still gives me the display error. So, it's not a permissions issue.
Hey Mitch, could you get with the dev who found the workaround on Facebook (MC) and figure out if it's something that we can roll out here on the forums?
Way ahead of you, but it's not a user friendly workaround. It involves some complicated fidgeting that requires someone that knows what they're doing to administer. We're working with Apple on a patch.
would it possible to get the infos on that workaround? I love complicated!! 🙂
any news on this topic? Is there an ETA for a fix?
Will there be a fix for Mojave too? As stated I'm on OS X 10.14.6 an the problem exists there too.
Media Encoder and After Effects are also affected.
Again: I'm willing to try to apply the workaround myself. I know my way around the terminal, launchctl, lldb (if need be) .... 😉
Same here. I'm in a bind with my production company. I've got a client project that was created in 14.0.1 and now I can't open it. Could really use that temp fix as well.
We're still digging into it but there's still things left to discover. Does anyone here with this problem have a Promise RAID? May be related, may be a red herring, but worth asking.
Why yes, I'm using the R6 Promise RAID.
As a test, I unmounted my Promise RAID and tried to launch Premiere 2020, but still got the same crash.
Unmounting wouldn't do it. Which driver version do you have for the R6?
Me too. Promise Pegasus2 R6 RAID, attached with a Apple Thunderbolt 3 to Tunderbolt 2 Adapter via Elgato Thunderbolt 3 Dock Pro.
No soecial driver installed? How do I know?
It's this bit right here:
I've been looking on the Promise site for an earlier driver version, but haven't found it yet. Again, so far this is just speculation, but there is some evidence that with driver version 4.04.0000.30 this issue doesn't occur. Too early to jump to conclusions, but if someone here can help us verify/deny this it would be great.
I too am using a Promise Pegasus R4i and am experiencing the problem. The machine in question is at work. I will have to check the driver version tomorrow.
Just to keep you up to date, I just got a new Version for Promise Utility and the Firmware.
Premiere ran once after reboot, but not again.
Thanks. The current working theory is that the OLD version of the drivers avoid the issue (version 4.04.0000.30) and the the NEW drivers are somehow involded in the problem.If you are able to locate and install the Promise Utility version 4.04.0000.30 and retest, that would help point the way.
Post #1 (sorry I messed up the reply order).
Promise Pegasus3 R4 here with Utility version 4.04.0000.37.
I just did a fresh restart, tried launching PR and got the crash.
As a first step I quit the PromiseUtilityDaemon (which is in the StartUp items) via the Activity Monitor. That didn't do the trick quite yet.
Second step I unloaded com.promise.BGPMain_R.plist with
"sudo launchctl unload /Library/LaunchDaemons/com.promise.BGPMain_R.plist" -- et voilà !!
PR, AE and Media Encoder all start without complaints and WITH GPU/Metal acceleration 🙂
Very nice catch there guys !!!
I'll try to roll back the Promise Utility next...
I just rolled the Pegasus3 Series Utility back to to version 4.02.0000.21 (release date according to Promise was 2019.01.07) as I couldn't find 4.04.0000.30 – looks like they took it offline for some reason.
The next newer version is 4.04.000.37 (support for macOS 10.15.1) which is causing the issue.
Now with version 4.02.0000.21 installed I did a reboot and PR, AE and Media Encoder start again without problems.
Still I'm noticing some very weird behavior regarding GPU usage. The performance is very bad compared to PR2019. I'll try to do a screengrab later... now I have to work.
There is a new Promise software 4.04.000.39 and
edit: Premiere starts, when i disable the LaunchDaemon Andreas decribes in the post before!
Its working with Premiere 14.0.1
But still no video output on the blackmagic ultrastudio 4k (fcpx do it)
so, some improvement.
edit 2: the problem with no video output, only audio output can be resolved with installing the blackmaagic drivers or plugins AFTER installing Premiere (i read that in a forum - i will test that tomorrow). It seems, that using the newest Utility from Promise (4.04.000.39) its working!!
Did some testing. There's both the Promise firmware (resides in the RAID system) and the Promise Utility software (running on the Mac).
I first ran the firmware updater, and it updated to 5.04.000.61, but Premiere still wouldn't open. So, I downgraded my firmware to V5.02.0000.98 (SR 1.2), and Premiere still wouldn't open. So, the problem is not related to the firmware.
For the Promise Utility software, I was running the most recent version, which I think was 4.04.0000.37. I downgraded to 4.00.0000.09, and now Premiere 14.0.1 is opening super fast and without issues.
So, it's definitely the Promise Utility causing the issue.
My co-worker and I have identical 2013 MacPros and Promise Pegasus2 RAIDs. I was getting the error message when trying to open CC2020 apps, he wasn't.
We just checked and, sure enough, he's on Version 4.02.0000.21 of the Promise utility, I'm on 4.04.0000.39
And.... it looks like we have a winner! I've started a conversation with Promise about this. Thanks to everyone here that helped us chase this down!
I'd be nice to get feedback HERE about your conversations with Promise.
Just so it doesn't get lost in the netsplit 😉
On a sidenote: is there a way to choose which GPU PR is gonna use in a dual- or more-than-one- GPU setup? I just noticed this today (blame on me) :s
PR uses exactly one of the dual D500s – the one that also takes care of everything else 😕
Ayup, I'm on 4.04.0000.39 and I too can confirm the deliciously reproduceable issue. Huzzah, grats Adobe peeps. You beat the 2019-nCoV researchers. *Flex*
You can set an e-GPU to be preferred, but not an internal GPU. I'd need to check with our development team to be sure, but I believe we select the GPU that your primary display is connected to as the preferred GPU. Premiere Pro will only use 1 GPU for real time transitions and effects, but will use multiple GPU for exports.
Thanks for the clarification Mitch!
I was also having the same 'could not find any capable video modules' error with Premiere Pro 2020 on MacOS Catalina 15.2 and 15.3. I also have Pegasus Raid devices and had the 4.04.0000.37 version of the Promise Utility installed. I uninstalled the PU and updated to version 4.04.0000.39 and did the unload the PUDeamon command in terminal and the 2020 video suite product now seem to be working fine.
You guys are awesome and have made my day! Hurrah!
Interesting how a raid server utility can cause an inability to recognise a GPU though!
Good news, and bad news. Good news is that I can back up one small version to 14.0, and the problem goes away. So, something in 14.0.1 is broken regarding this issue.
Bad news is that all of the projects I created in 14.0.1 (latest version) will not open in 14.0. I get the error saying, "Project was created in a newer version of Premiere.) It was 0.1! That's not a new version.
Anyways, something is seriously broken in 14.0.1. I'll try to stick with 14.0 for now. Hopefully, they'll figure it out soon.
For me installing 14.0.0 again didn't make a change.
Macbook Pro 2019 16" with AMD Radeon Pro 5500M 8 GB
macOS Catalina 10.15.2
An Adobe staff member in the facebook group "Adobe Premiere Pro Editors on Facebook" has a workaround for this and will apply it if you post in that group.
Thanks for the heads-up!!
But I'm not on facebook. Don't intend to join either... now what?
I have already raised this concern with the Adobe staff member in question and I did not receive a response.
Just got on FB and found the post. There's a fix but it's still only a temp fix that adobe can do. No real solution at this point. Here's the posted solution:
SOLUTION: I had the pleasure of working with reps from the engineering/qc team at their invitation, who took a deep dive into this issue on my machine and was able to in 24 hours provide a work around solution. Watching them work to diagnose the issue kinda blew me away, incidentally, where I got to see first hand how Adobe tackles these issues, a decidedly different experience than what you get when you call support. There's a caveat or two, and they will be looking deeper into the root cause. It has to do with a process at launch getting stuck a load in loop.
I wouldn't call that a "solution"... but hey.. at least it's being looked at 😉
I really hope they can provide a permanent fix soon.
Hi - Just to add that I am having the same issues, and I too have the 2012 trash can MacPro with a Promise Pegasus running version 4.04