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

[tranhoangcalvin]

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).

[Martin.Lorenzo.C10]

I think "the pinned post" is the one referring to the posting etiquette, does not address any solution at all.
Since it is obviously happening in both Windows and Mac platforms, and a ton of media formats, i guess it is not relevant.
[cid:canal_10_logo_7a013807-f29c-45cb-ad34-716e3e7c0cdc.jpg]

[cid:barrita-separadora_65c5e5ca-ddae-495a-98dd-602fb033198d.png]

Martín Lorenzo
[personal info deleted by mod]

[jonathanbecker]

Yes, the issue is still present in 25.2.3, the audio drops out. Though now there's no error notification in the corner, it just happens. 

[hakankadioglu]

[Edited by moderator]

[gordonw50483927]

As stated by others, the issue still occurs but now the audio just drops out without the accompanying error message.  Please update us on this. It is now entering the 2nd month of this impacting my workflow. I am a YouTube content creator and subscriber and pay monthly for this software. I pay for it to work 🙂

[Stan Jones]

@GigowattFilm,

Your post is helpful to me in understanding your issue - and what you see after the error message is gone. I would call it audio dropouts that occur reliably but not every time.

For anyone, is it always pressing the space bar? Or do clicking the play button in the Program Monitor?

Are you Windows or Mac? Do you also experience any issues with exports (some users did)?

I am Win 10, and, despite paying attention and trying to get an issue, I did not get the error messages nor audio dropouts.

Stan

[gordonw50483927]

Hi Stan,

If it assists you, I will be working again tonight and can create a small video of this occurring. I can also try to write up a more step by step bug account. Thanks for reaching out!

Gordon

[Stan Jones]

@gordonw50483927,

Yes, please.

Stan

[GigowattFilm]

I'm using windows 10 on every machines.

I did as of 25.2.3 encountered some problems in exporting. The files are calculated till the end in AME but are truncated on the resulting file. I did the old software only trick to workaround the problem.

[Adolfo H.]

Hi there, this is Adolfo from Adobe. We're aware of the issue and are looking into it. It would be great if anyone is willing to share their project with me, as it could help us investigate further. We'll keep you updated in this thread as soon as we have more information.

[magnificent_laughter1646]

Hallo, ich habe das gleiche Problem. Zuerst wurde mir die Fehlermeldung angezeigt, der Ton in Premiere Pro aber normal abgespielt. Jedoch wurde beim Videoexport der Ton falsch oder gar nicht ausgegeben. Jetzt ist die Fehlermeldung weg, der Videoexport ist aber trotzdem noch falsch. Den Ton hört man nur stellenweise.

Vielen Dank.

[batmae]

Ran into this today and installing the previous version didn't appeal to me yet so I instead took it to Audition, edited my sound there then exported for Premiere. I inherited this timeline and the prev editor had over 50 layers of sfx. Hope this workaround works for you too until it gets fixed.

[logan_5994]

I'm having the issue of not being able to see the screen, not the whole screen, but the screen where it allows you to view the footage you're editing. I've tried reopening the app, and restarting my pc. Yet both failed. I don't know what to do or what is wrong with it. I'm going to keep trying to fix it, but if anyone has any solutions, please tell me them.

[MPEO]

I am getting the same error with any audio in my timeline, and it's really annoying. 

[CBryantNYC]

I'm getting the same error, never used to happen and I've had no hardware changes in the past 3 years.

Running v25.2.0

Custom build PC

6 core Intel i7-5820K CPU

64GB RAM

Running off a LaCie external drive with USB 3.0 cable

[Andrew251801670jel]

Does anyone know if 25.2.3 works correctly? I am still using 25.1.0 (build 73) and apart from occassional audio drop-outs during playback in the time-line, it functions. Exports seem to be fine.

[martint78499082]

Hi, I tried to upgrade to 25.2.3 and the sound still doesn't work :(. Had to roll-back to 25.1.0, which works. It's starting to be a little annoying, it 4 updates and sound still doesn't work on any newer version 😞 . I am starting to be a little worried about the project compatibility 😛 .
I am running Premiere on fairly strong desktop and laptop.

The laptop configuration:
AMD Ryzen 7 7435HS 3.10 GHz

32.0 GB
NVidia 4070

Are the devs looking to it? Any info regarding the fix?

[Colin Connolly]

Still having this problem!

[jonathanbecker]

Hey everyone, here's an important update on my end that I hope helps others. 

I’ve been running into an issue with Premiere where audio from certain clips just drops out completely — the waveforms show up, but there’s no playback, and the only way to get it back is to close and reopen Premiere. On previous Premiere versions I got error notifications, but now nothing. After a lot of testing, I figured out that many of the problem files were 44.1kHz — usually voiceover recordings. Once I converted those to 48kHz WAVs, the issue went away. This seems to be a known bug, but still not fixed in the latest version. Just sharing in case it helps others or if Adobe wants another data point.

[brunolgaudencio]

I am currently using version 25.2.3 but I have been having this issue since Premiere 24. Its becoming impossible to edit anything longer than 5 seconds on the software - which is hard when you are editing an entire feature film. After this 5 second limitd all audio is cut out and I have to playback again.

The only thing this recent update did was to stop warning about the problem with the message "Can't access audio. The audio for _____.wav can't be read quickly enough from storage. Please check your storage and try again." - almost as to hide this issue.

I tried everything possible: messing with all preferences on Premiere, changing the video and audio files to an NVME SSD, creating proxies of everything, reimporting everything, creating a new blank project, trying to edit on 4 DIFFERENT COMPUTERS to see if anything is fixed and NOTHING!

How can an editing software that costs $69.99/month be unable to play video and audio at the same time? It disgusts me! Other editing softwares I used never had this problem with the same kind of files - which in this case is ANY FILE. Premiere has become an outdated software long ago.

I am having no other option than completely change my workflow to Davinci, and maybe this is for the better...

[hakankadioglu]

brunolgaudencio, I understand you so well. I'm editing a feature-length film, and this program is a complete problem machine. I regret using this program, and as soon as the project is finished, I will never use it again because they don't solve the problems. Whatever they are doing, no one understands it yet. The program has gotten worse with each passing day. I will switch to DaVinci at the first opportunity.

[GigowattFilm]

@brunolgaudencio 

Hello

I have the audio dropout problem but it is absolutely not as bad as yours.

My problem is that the audio is cutting 1 sec after pressing the space bar, but just for 1 second, then it plays fine.

So I'm wondering what is your audio configuration. Do you have an external sound card? Are you using MME or ASIO configuration?  What kind of footage is the worst for this problem?

Can you provide for a link with an exemple footage so that I can test it with my machine?

[David Flor]

I've been using Adobe Premier Pro version 25.2.3. This error has been repeating itself several times. My computer's configuration is: 1 TB NVME file storage for the operating system and applications, 1 TB NVME dedicated for video editing, SSD for video preview, and SSD for audio preview. It's repeating itself not only with MXF files, but also with WAV and MP3 files. I was advised here in the Adobe Community to try the beta version of Adobe Premier Pro, and I'm using version 25.4.0. But the error persists. I spoke with an Adobe customer service agent, and they told me the solution is to go back to a previous version of Adobe Premier Pro, when it didn't give this error. So why pay for a service that tells you to go back to an old version? I've been a Premier Pro user since its first version. I'm beginning to understand why many have switched to DaVinci Resolve.

[PolkaFever]

Hi @tranhoangcalvin ,
Your assumption about the behind the scene indexing, .prin file and turning of analysis, did it make any difference?

[PolkaFever]

Hi @Adolfo H. , @IanB_360 & @jamieclarke 

There has been a few updates now and we still struggle with this problem. I'm on 25.4.0 Beta (build 50). And "can't access audio" is still present.
As metioned by a few this is software not files or hardware issue. Premiere is having problems with a lot of files (Wav, mp4, mp3, proxies, Mov etc.). Big or small projects or sequences. Even small pure 1 minute audio projects have these audio access issues.
I'll be happy to share a project and contribute to find a solution, because we have deadlines and work arounds also takes time. It look like things have hit a standstill on your end? I find it wierd that 25.1.0 works. If that is the case you should be able to narrow down what you changed when you moved to 25.2, right.

Regards

Polkafever

OS:Win 11 Enterprise v23H2, 22631.5335

PC: Dell Precision 5860 Tower

PROSESSOR:Intel(R) Xeon(R) w7-2495X 2.50 GHz

RAM:192 GB

[Tom_edit]

This issue definitely wasn't brought about by 25.1, they just started actually showing an error after that. Prior to that version audio would simply drop out instead. I know for a fact it's been happening for at least the last year or two.