Skip to main content
tranhoangcalvin
Known Participant
April 2, 2025

P: Audio "can't be read quickly enough" from storage

  • April 2, 2025
  • 197 replies
  • 39888 views

Just started getting this error window today while working on a very simple project that only has a couple After Effects motion graphics clips, and three tracks of audio: VO, music, and light SFX:

 

Event Details:

Can't access audio

the audio for _____.wav can't be read quickly enough from storage. Please check your storage and try again.

 

Build:

Windows 11 Pro 26100.3624

12th Gen Intel i7-12700K 3.60 GHz

32 GB of RAM

NVIDIA GeForce RTX 3060 

 

The local C drive is an NVME SSD, but the file in question is stored on a Synology NAS with IronWolf HDDs. Both the computer and the NAS were built from new parts this year.

 

Premiere: 25.2, installed this week.

 

The same error happened on a second computer (same build, also connect to the NAS).

197 replies

Participant
April 8, 2025

Seems to be the case for most users here. Just encountered it for the first time myself. Guess I'm rolling mine back, too.

Participant
April 8, 2025

Heyy, been experiencing the same bug. It just showed up when I updated to 25.2, two days ago. It's somewhat randomly appears on a certain clip and it keeps on popping for some reason and it also does affect the playback as it will on the certain clip. Is there a way this to updated without waiting for the official release of the new version? or a downgrading is the only option?

(It's not a new project I've edited but rather a existing one which I started working on before the update)

Inspiring
April 8, 2025

I'm also having this audio error, but also other more serious lagging, and I'm wondering could they be related. Has anyone else experienced this, when editing 4k 50 fps footage:

  • After pressing play, the video and sound stutters for 2-4 seconds and the playhead jumps back and forth.
  • If there are red or yellow sections on the timeline, even any green (rendered) section has the stuttering issue.
  • If there is any reverse speed clip on the timeline, the stuttering issue appears about 12 seconds before the reversed clip, even if the clips before the reversed one are green/rendered (as if Premiere is trying to read the reversed clip in the background and then messing up the playback).

 

The only workaround so far is to render the whole timeline after every single change you make, which obviously makes the editing a very slow process.

 

My system:

  • Asus ProArt P16 laptop
  • 64GB RAM
  • AMD Ryzen AI 9 HX 370
  • RTX 4070 (laptop)
  • Windows 11 Pro 10.0.26100 Build 26100

Participating Frequently
April 8, 2025

Both Beta and 25.2 get the same warning.

The very small file being read is in MacBook internal storage. No way it's slow. It's definitely a bug.

Participating Frequently
April 7, 2025

Just chiming in here as well, saying I've also been experiencing this since 25.2. Even todays' 25.2.1 update didn't fix it. 

Participating Frequently
April 7, 2025

Happy to send you a file but need to know how. Could send you a Google Drive link if you tell me where to send it.

Participant
April 7, 2025

Sound 

Known Participant
April 7, 2025

ok now i have this message about file that i voiceover in this program premiere pro 2025.2

andyR10
Known Participant
April 7, 2025

I just saw this error message for the first time in my life. Was working on the project last week and everything was fine, but updated to the latest release this morning and now this is happening.

Participant
April 7, 2025

not really a fix but a work around i found - go to Edit - Prefrences - Audio Hardware and change default input to no input. then go back to your project and delete any footage with this error, including off the timeline and also the project panel on the side. then save your project, close premiere and reload, then go back into the project and import the footage again, and the bug will be gone for the footage. if you need to use inputs again in premiere (voiceovers etc) you can change it back once you import the footage. its a very annoying bug and this is the only think that has worked for me, also you will have to do this for any new project you start, as the bug presists to the next project! Hope this can help someone!