Premiere Pro could not find any capable video play modules. Please update your video display drivers

Explorer ,
Jan 15, 2020

Copy link to clipboard

Copied

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.

Hi Larry,

Yeah, I understand the confusion. The posts here are a bit out of order. Short answer is to uninstall the Pegasus Utility. If you can locate a copy of the Pegasus Utility version 4.04.0000.30 or earlier, you should be able to install and use it without hitting the problem. Otherwise, just leave the utility uninstalled. The Promise developers and the Adobe developers are both looking at the problem to try to understand what's occurring when the Pegasus Utility is installed that is thwarting our ability to check the GPU status. It'll take a little time to sort out but I expect that both companies will take steps to avoid something like this from happening again. 

TOPICS
Error or problem

Views

2.1K

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Jan 15, 2020 5
New Here ,
Jan 24, 2020

Copy link to clipboard

Copied

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.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jan 24, 2020 0
Explorer ,
Jan 27, 2020

Copy link to clipboard

Copied

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.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jan 27, 2020 0
Explorer ,
Feb 07, 2020

Copy link to clipboard

Copied

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).

 
So to my mind, it's definitely the Promise Utility that is the issue.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 07, 2020 0
Adobe Employee ,
Jan 27, 2020

Copy link to clipboard

Copied

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.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jan 27, 2020 1
Explorer ,
Jan 27, 2020

Copy link to clipboard

Copied

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.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jan 27, 2020 0
Adobe Community Professional ,
Feb 01, 2020

Copy link to clipboard

Copied

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? 

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 01, 2020 1
Adobe Employee ,
Feb 01, 2020

Copy link to clipboard

Copied

Hi John,

 

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. 

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 01, 2020 1
Adobe Community Professional ,
Feb 01, 2020

Copy link to clipboard

Copied

Great, thanks. Will this be added to https://helpx.adobe.com/premiere-pro/kb/known-issues.html

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 01, 2020 1
Explorer ,
Feb 01, 2020

Copy link to clipboard

Copied

Hi Mitch,

would it possible to get the infos on that workaround? I love complicated!! 🙂
P.M. maybe?
Cheers!

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 01, 2020 0
Explorer ,
Feb 05, 2020

Copy link to clipboard

Copied

Hi Mitch,

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) .... 😉

Thanks!

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 05, 2020 0
Explorer ,
Feb 05, 2020

Copy link to clipboard

Copied

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. 

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 05, 2020 0
Adobe Employee ,
Feb 05, 2020

Copy link to clipboard

Copied

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.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 05, 2020 1
Explorer ,
Feb 05, 2020

Copy link to clipboard

Copied

Why yes, I'm using the R6 Promise RAID.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 05, 2020 0
Explorer ,
Feb 05, 2020

Copy link to clipboard

Copied

As a test, I unmounted my Promise RAID and tried to launch Premiere 2020, but still got the same crash.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 05, 2020 0
Adobe Employee ,
Feb 05, 2020

Copy link to clipboard

Copied

Hi Russell,

 

Unmounting wouldn't do it. Which driver version do you have for the R6?

 

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 05, 2020 0
Community Beginner ,
Feb 05, 2020

Copy link to clipboard

Copied

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?
Bildschirmfoto 2020-02-05 um 23.52.00.pngBildschirmfoto 2020-02-05 um 23.52.54.png

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 05, 2020 0
Adobe Employee ,
Feb 05, 2020

Copy link to clipboard

Copied

It's this bit right here:
Driver.png

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.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 05, 2020 0
New Here ,
Feb 05, 2020

Copy link to clipboard

Copied

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.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 05, 2020 0
Community Beginner ,
Feb 05, 2020

Copy link to clipboard

Copied

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.

Nothing changed.

 

Bildschirmfoto 2020-02-06 um 00.21.03.pngBildschirmfoto 2020-02-06 um 00.22.36.png

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 05, 2020 0
Adobe Employee ,
Feb 05, 2020

Copy link to clipboard

Copied

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.

 

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 05, 2020 1
Explorer ,
Feb 05, 2020

Copy link to clipboard

Copied

Post #1 (sorry I messed up the reply order).

Hi Mitch,

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...

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 05, 2020 0
Explorer ,
Feb 06, 2020

Copy link to clipboard

Copied

Post #2:

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.

 

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 06, 2020 0
Community Beginner ,
Feb 06, 2020

Copy link to clipboard

Copied

There is  a new Promise software 4.04.000.39 and Premiere starts!

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!!

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 06, 2020 0
Explorer ,
Feb 06, 2020

Copy link to clipboard

Copied

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.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 06, 2020 0
Explorer ,
Feb 06, 2020

Copy link to clipboard

Copied

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

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 06, 2020 0
Adobe Employee ,
Feb 06, 2020

Copy link to clipboard

Copied

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!

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 06, 2020 2
Explorer ,
Feb 06, 2020

Copy link to clipboard

Copied

Thanks Mitch!
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 😕
Cheers!

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 06, 2020 0
Community Beginner ,
Feb 06, 2020

Copy link to clipboard

Copied

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*

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 06, 2020 0
Adobe Employee ,
Feb 06, 2020

Copy link to clipboard

Copied

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.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 06, 2020 1
Explorer ,
Feb 07, 2020

Copy link to clipboard

Copied

Thanks for the clarification Mitch!

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 07, 2020 0
Explorer ,
Feb 07, 2020

Copy link to clipboard

Copied

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!  

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 07, 2020 1
Explorer ,
Jan 27, 2020

Copy link to clipboard

Copied

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.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jan 27, 2020 0
Community Beginner ,
Jan 28, 2020

Copy link to clipboard

Copied

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

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jan 28, 2020 0
Adobe Community Professional ,
Jan 31, 2020

Copy link to clipboard

Copied

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. 

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jan 31, 2020 1
Explorer ,
Jan 31, 2020

Copy link to clipboard

Copied

Thanks for the heads-up!!

But I'm not on facebook. Don't intend to join either... now what?

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jan 31, 2020 1
Adobe Community Professional ,
Jan 31, 2020

Copy link to clipboard

Copied

I have already raised this concern with the Adobe staff member in question and I did not receive a response. 

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Jan 31, 2020 1
Explorer ,
Feb 01, 2020

Copy link to clipboard

Copied

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.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 01, 2020 1
Explorer ,
Feb 01, 2020

Copy link to clipboard

Copied

Thanks Russel!
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.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 01, 2020 0
Community Beginner ,
Feb 06, 2020

Copy link to clipboard

Copied

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 Screen Shot 2020-02-06 at 9.11.41 AM.png

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Feb 06, 2020 0