Participating Frequently
January 24, 2023
Question
Premiere 15.2 through 15.4 unusable with large projects on Mac Pro (2019) Big Sur
- January 24, 2023
- 23 replies
- 2394 views
After having no issues with 15.2 on small projects, Premiere became completely unusable after about a month of working on a feature film. It really seemed like an access error, as I'd get errors like "Unable to access resource 'S_ErrorXl_N_D@2x' (type svg)," "Error Retrieving frame XXXX at time XX," and "Unable to access resource 'CursorDataID-19 (type xml)." The errors came with frozen or black video, I could still hear audio, and it usually fixed itself after about 10-20 seconds. I also couldn't export anything no matter which renderer I used. I thought it had something to do with Canon MXFs, since those have always been problematic for Premiere, but I got the same errors on ProRes 422, HQ and 4444 clips as well. The issues happened about once a day at first, and gradually increased to once every minute. At that point we shut down editorial until we figured this out.
This is a very specific issue, because openning the same projects (part of a large Premiere Production) with the same media storage on iMacs or iMac Pros on Big Sur or Catalina worked just fine. This made me think it was a hardware issue with my system. I have a Mac Pro (2019): 16-core on Big Sur 11.4 (I had to upgrade because PrPro 15.2 caused regular kernel failure with Catalina, and upgrading to Big Sur fixed those issues), 128 GB ram, Radeon Pro Vega II 32 GB graphics. We troubleshot everything from uninstalling every bit of software and drivers I could think of, including all Adobe apps, physically uninstalling my second GPU, switching media storage from a Raid to a single spinning disk (still external), and nothing made any difference. The last step of troubleshooting I tried was to downgrade Premiere to 15.1, and suddenly everything worked great (except for rendering with GPU acceleration, but switching to Software Only gets the job done).
In conclusion, something was introduced in 15.2 that causes read errors on large projects on a Mac Pro, and the issue persists with 15.4, but goes away when downgrading to 15.1. Thank you, Adobe, for allowing me to open projects in previous dot-versions, otherwise I would be in a very tight spot right now.
This is a very specific issue, because openning the same projects (part of a large Premiere Production) with the same media storage on iMacs or iMac Pros on Big Sur or Catalina worked just fine. This made me think it was a hardware issue with my system. I have a Mac Pro (2019): 16-core on Big Sur 11.4 (I had to upgrade because PrPro 15.2 caused regular kernel failure with Catalina, and upgrading to Big Sur fixed those issues), 128 GB ram, Radeon Pro Vega II 32 GB graphics. We troubleshot everything from uninstalling every bit of software and drivers I could think of, including all Adobe apps, physically uninstalling my second GPU, switching media storage from a Raid to a single spinning disk (still external), and nothing made any difference. The last step of troubleshooting I tried was to downgrade Premiere to 15.1, and suddenly everything worked great (except for rendering with GPU acceleration, but switching to Software Only gets the job done).
In conclusion, something was introduced in 15.2 that causes read errors on large projects on a Mac Pro, and the issue persists with 15.4, but goes away when downgrading to 15.1. Thank you, Adobe, for allowing me to open projects in previous dot-versions, otherwise I would be in a very tight spot right now.
AdChoices