Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

Premier Pro Beta Bug v25.3.0.019 (2025-03-15) Rendering + Can't Access Audio Storage + hard crash

Community Beginner ,
Mar 16, 2025 Mar 16, 2025

Hello, I've been using the Beta's on PPro for a while with no issues, but this latest update 3/15/2025 and the one right before it were painful.

*On the latest update, I was simply trying to grab "still shots," so I wasn't even editing. I had 3 clips and took some stills, but the last clip would not play (it was a black screen where the video should be, with no audio). Please see the 1st screenshot of the error attached - it said "The audio for C0359.MP4 can't be read quickly enough from storage. Please check your storage and try again." I could not get it to work at all.

 

*Directly prior to this latest update, I was editing a short video that was about 2 mins long on 3/12/2025. It took soooooo long because each ripple delete or sound change or basically anything I did, a box would pop up "rendering" with a circle that would keep spinning at 0%, I kept waiting and then cancelling, but then realized if I waited long enough it woud go from 0% to 100% at the very end of the wait. The wait varied depending on how complex the action, but it would last anywhere from a few seconds to 30 or even over a minute (I didn't time it, this is just an estimate). These "rendering" pop-ups froze the screen and certainly added up, and the video edit took me like 3X as much time. I would have to wait for the render every single time.

*The program also shut down my whole computer during this same video edit on the 12th (I also have a screenshot attached of that). I bought this computer in August of 2024, so it's quite a new computer, and I have a habit of shutting everything down and emptying the trash before editing any videos because I heard it would make editing faster. 

That's just three of the bugs I found by using Premiere Pro Beta two times.

 

Q: I'd love to roll back the beta to before this started happening. Is that possible? Will I lose the ability to edit files, or will I have issues if I do that? OR is this a known issue that will be fixed quickly? I actually upgraded from a 2017 MB Pro with an Intel chip because I wanted more bandwidth for video editing, and that is also why I also paid extra for the upgraded memory and storage and chip.

 

Here is my system info:

Mac Mini M2 Pro (2023) - bought Aug 2024 from Apple, brand new

Chip M2PRO

MacOS Sequoia 15.3.2

Storage 1.77 TB available of 2 TB (upgrade)

16 GB Unified Memory 

Total Number of Cores: 10 (6 performance and 4 efficiency)

 

Bug Unresolved
TOPICS
Bug , Crash , Error , Feedback , Performance , Question
473
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
3 Comments
Participant ,
Jun 22, 2025 Jun 22, 2025

It says unresolved but I wanted to make sure if that was so. I posted the below on the 20th. Maybe apropos to your issue?

Heads-up: M3 Max Crashes with Premiere Pro under macOS 15.5 (Sequoia)

I've confirmed system-level GPU crashes when using Premiere Pro on macOS 15.5 (Sequoia) with an M3 Max MacBook Pro.

During scrubbing, timeline exports, or Metal stress tests, my system flashes red and reboots without warning or error dialog.

Here’s what I tested (June 17–19):
- :white_heavy_check_mark: CPU and memory stress tests = no crash
- :white_heavy_check_mark: Same drives/projects on Intel iMac = stable
- :cross_mark: M3 Max crashes under GPU load only (WindowServer, AGXMetalG15X-M1, QuartzCore in logs)

THIS ISN’T A PREMIERE BUG — the fault appears to lie in macOS Sequoia’s Metal/QuartzCore stack on Apple Silicon (M2/M3).

I’ve built a ZIP package with full crash logs, diagnostic scripts, and test configs. If others are experiencing this, I encourage comparing logs or referencing my report for escalation.

Premiere Pro: 25.4 (Beta, Build 54)
Chip: Apple M3 Max – 128GB RAM – 4TB internal
Drives: G-Raid, WD Black (ACSIS enclosure, TEAMGROUP 8TB (ACASIS enclosures)
Config: Tested both via Thunderbolt hubs and direct USB-C ports

Translate
Report
Community Beginner ,
Jun 23, 2025 Jun 23, 2025
  • Funny you mention. I've been keeping a google doc of all my crash reports ever since I bought the new Mac and have called Apple service a million times to no avail. Next step is to bring it in which I really do not want to do esp if it's an issue with all M2 M3. When I used the prior version of Premiere Beta it didn't happen with Premiere, but it did happen sporadically ever since I purchased it, even when I am not using the computer (I'll come back and it will have turned off and when I turn it back on it says you're computer shutdown in error or something like that. So, I think you're right but I also had new issues with that
Translate
Report
Participant ,
Jun 24, 2025 Jun 24, 2025
LATEST

Have you recently updated to Sequoia? If you want me to take a look through the crash logs and see if I see anything I'll be happy to. I use ChatGPT mini-40 to do this (with the caveat that does get things wrong at times). If you do then make sure you delete personal info and any serial #s.  The decisive factor for me was that under the exact same circumstances, same external drives media projects and PP  version and builds on an Intel iMac there have been no crashes. 

Translate
Report