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
  • 40094 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

Kyle Kramb
Inspiring
April 18, 2025

Beating the dead horse-
 
• Issue - Audio drops out durning playback with dialogue box poping up that reads "Can't Access Audio". 
• Steps to reproduce - make edit. hit play. 
• Expected result - sequence should playdown.
• Actual result -  Audio drops out diurning playback with dialogue box poping up that reads "Can't Access Audio"
• Adobe Premiere Pro version -25.2.1
• Operating system - Mac OS 15.3.2 (24D81) - iMac Pro - 3 GHz 10-Core Intel Xeon W, Radeon Pro Vega 64 16 GB, 128 GB 2666 MHz DDR4
• Video (and Audio) format - All sorts - but one specifically is Apple ProRes 422 Proxy UHD 23.98 with multitrack audio - these are transcodes made in Resolve from R3D RAW. Also happening with Stock footage downloaded from Filmsupply, wave audio files from Marmoset, mp3 files from unknown source (stereo music), and sfx wave files from Snoundsnap.
 
Screenshot from the last hour - and this is me working slow because I am reading a lot of notes and doing a lot of head scratching too.

 

______________As happy as a clam in butter sauce!
Participant
April 18, 2025

Wow, your build is almost exactly as mine, except that I have 64GB of RAM. I'm having the same issue. I came here to start a thread about this and found this one.

Time_Bas
Participating Frequently
April 18, 2025

Same problems here. Running really the latest of greatest computers with al NVME drives.

Participating Frequently
April 17, 2025

Could the Adode team tell us what hardware they are running Primiere Pro on? May we all need more powerful computers to run the latest two versions.

Participating Frequently
April 17, 2025

Tried that. It didn't work

Participating Frequently
April 17, 2025

Nope

tranhoangcalvin
Known Participant
April 17, 2025

OP here.

 

I think I know what's going on. In 25.2, Adobe added the capability of Premiere to analyze all of the media that you're importing into your project so that you can search for assets based on what's in them. This is why you will now get a .prin file generated next to your premiere save file.

 

This suggests that your computer is, in the background, busy computing what is in your assets, and that, I think, is what is slowing down its ability to read the audio file (sounds ridiculous that it would slow down the read of files at all, but this is what I'm experiencing). I went into Preferences, under Media Analysis and Transcription, and deselected "Analyze all imported media to visually search your project"

Participant
April 17, 2025

The error hasn't reappeared for me since downgrading to 25.1 confirming at least on my end that this was a software problem and not an actual hardware issue like the error implies.

Known Participant
April 17, 2025

I am having this same intermittent problem. I'm on a mac studio m1 max, 64gb ram, os 14.6.1 and a mac laptop with the m3 pro chip as well. I'm running PP2025 25.2.1 (build 2). Sometimes it happens more frequently than other times. Usually, I'm able to just stop playback and start again and it will play normally. 

ThioJoe
Community Expert
Community Expert
April 17, 2025
quote

It is wonderful that you have time for experiments. But 99% of people here just need to work and not search for errors. We pay money for the product and we have no time to search for problems, we have deadlines


By @Paul_Gringo 

 

I mean considering it's a bug in the app itself, your options are:

  • Wait and do nothing until Adobe fixes it
  • Use an older version of Premiere
  • If you can't use an older version, try a workaround

 

I'm just offering the 3rd option. And they're not exactly experiments, they literally worked for me to fix it.

 

I'm trying to guage how successful the workarounds are to others with the same problem so I know whether I should suggest it to everyone or not.