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

andyR10
Known Participant
April 16, 2025

I can also report that since I first experienced this issue and posted about it in this thread, I have not seen it again. I've been able to work on multiple projects.

tranhoangcalvin
Known Participant
April 16, 2025

OP here:

 

I first downgraded to Premiere 25.1 and this particular error stopped showing up.

However, I can't say if this is exactly the cause and effect, but since I was in the middle of a project, the downgrade, I believe, resulted in a project file completely corrupting. Since I save a new version every day, I was able to go back and continue from a previous save file, but it eventually happened again.

 

I have since upgraded to 25.2.1 -- the audio error sometimes shows up if I'm opening a new project or opening a project for the first time on this version, but not as frequently and randomly as it was on 25.2. Also, after editing for a little bit, the error doesn't seem to continue and it doesn't seem to affect the actual export at the end of the day.

 

This is still BS and I want Adobe to know I will be learning Davinci Resolve as a safety measure with how the past 4 years of instability has been. You are lucky that I paid for the year upfront.

Participant
April 16, 2025

I have projects due like 99% of your users. Seeing how it's 4/15 and this issue still isn't fixed is bs.  I downgraded to 25.1 and will stay there so I don't get fired. Appreciate the big effort on Adobe's part to get this major bug fixed

Participant
April 16, 2025

same problem here

Participating Frequently
April 15, 2025

Yes, this is a software problem. Adobe manages to break something with every new version because the program Now it's a patch pile, the company knows this very well. Constantly breaking something, they don't get any efficient results from this code pile, freezing and delaying on the timeline They solved the problem but the result is the same again. Now I will say goodbye to this program after this project. We cannot do our job because of trying to solve the problems.

Participant
April 15, 2025

Same here. Every project. Audio can be wav or mp3 or linear PCM in ProRes footage, doesn't make any difference. Using attached SSDs over USB-C on an M3 Macbook Pro. This is a new issue with this version of Premiere.

Participant
April 15, 2025

that's me 10 minutes ago before reading this. Mine would play for a couple of seconds and then that thing pops up, audio gone. It's at random places too. 

Participating Frequently
April 15, 2025

Seeing this behavior as well. 

Participant
April 15, 2025

I'm having the same issue on my Nitro V15 (Acer)

Participating Frequently
April 14, 2025

I'm having the same issue as many others over the past couple weeks with choppy audio and the "can't render audio" issue

kglad
Community Expert
Community Expert
April 14, 2025

in the future, to find the best place to post your message, use the list here, https://community.adobe.com/

p.s. i don't think the adobe website, and forums in particular, are easy to navigate, so don't spend a lot of time searching that forum list. do your best and we'll move the post (like this one has already been moved) if it helps you get responses.



<"moved from using the community">