Skip to main content
Participant
December 29, 2019
Question

2019 Mac Pro 7,1 w/ Vega II - CRASHING Premiere (update drivers??)

  • December 29, 2019
  • 4 replies
  • 2807 views

I'm getting this message every time I try to open 2020 Adobe Premiere Pro on my New Mac Pro 2019:
"Premier Pro could not find any capable video play modules. Please update your video display drivers and start again."  
Specs:

2019 Mac Pro: 16-core, Vega II solo, 192gb ram (OWC)

10.15.2 MacOS Catalina

Restarts don't help. Any ideas here or anyone else experiencing this issue?

I need this addressed ASAP as I cannot get premiere to open on my brand new machine. 

This article does not address the issue with the Mac Pro 2019. 

 Error "Premiere Pro could not find any capable video play modules" | Startup 
(but I'm the admin with permissions. I'm not sure what they mean by renaming folders)

This topic has been closed for replies.

4 replies

Known Participant
February 7, 2020

Have exactly the same issue. New Mac Pro with Vega II.

Every second(!) time I try to start Premiere it crashes prompting this massage: "Premier Pro could not find any capable video play modules. Please update your video display drivers and start again."  

 

Adobe can you hear us?

 

Participant
February 18, 2020

Silimar machine. Same issue(s):

 

i.) SLOW START-UPS

ii.) CRASHES

iii.) "Premier Pro could not find any capable video play modules. Please update your video display drivers and start again."

 

Applicable applications: AE, PP and Media Encoder

 

By chance, are any of you having these issues with a Pegasus HD (or the software from PP)?  I have a R4i PP MPX Module installed and heard that it may be the cause. 

chockolate
Participating Frequently
February 18, 2020

Hi cjpmsp, according to Adobe it is a Pegaus Drive  issue but I faced this same issue on a clean install with only Adobe CC 2020 installed and detailed it here actually:

https://community.adobe.com/t5/premiere-pro/premier-pro-2020-after-effects-media-encoder-audition-issues-with-macos-catalina/td-p/10823494

 

Believe it's an issue with Catalina and Aodbe CC but still worth it to try the fix from Adobe on this!

Inspiring
January 3, 2020

I have a similar new MacPro, and I did a clean install  of everything except my User documents that I migrated with Migration Assistant.  So far, I've concluded that Catalina and Pr 2020 aren't ready for pro use.  I suggest you use 2019 and stay away from 2020 until it's been debugged.  There are posts here on downgrading Pr projects, or just do a web search for "premiere project downgrade."

Inspiring
January 16, 2020
devotive
Participating Frequently
January 3, 2020

I'm having the same issues with the same exact specs.  Any solutions?

devotive
Participating Frequently
January 3, 2020

I wanted to post an update for anyone having the same issues with these specs. 

In a rush to get my machine running against tight deadlines I did a bunch of stuff that so far has gotten my Premiere to get up and running:

- Disabled my second monitor, running on a single monitor
- Manually reset permissions on all adobe app and app support folders in library, made every user available able to "read and write"

- Used Digital Rebellion's app and trashed all preferences and ran every single possible fix to fix permissions everywhere
- Sacrificed my first born to the vengeful tech gods
- Restarted three times

So far I seem to be stable for at least this one working session.  I'll update if it anything else happens. 

kwinzelerAuthor
Participant
January 6, 2020

Is your machine still working with this solution? Do you think it's related to the second monitor being plugged in?

chockolate
Participating Frequently
December 29, 2019

Hi Kwinzeler, definitely not an issue with the new Mac Pro or Macbook Pro 16".

 

Did a detailed troubleshooting over the last few days and shared it here.

https://community.adobe.com/t5/premiere-pro/premier-pro-2020-after-effects-media-encoder-audition-issues-with-macos-catalina/td-p/10823494

 

It's not just PP but its accompanying video audio software as well. Hope someone from Adobe addresses this asap.