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

I too am having this issue despite over 200gb available. 

i have 128gb ram computer and im getting this error too.

It worked perfectly for me! And better, my Premiere is no longer laggy! Thanks 🙂

@jamieclarke I think it might be failing to decode video files that have a small amount of corruption. It's certainly not every file. I have two copies of the same video file that I copied from my memory card - and I've had issues in the past of it not copying exactly correctly (the video plays, but premiere gives occasional frame error messages, and the hash of the copied file doesn't match the on on the card) and I've had to copy the file a second time. That happened this time and the 'bad' video copy causes the problem and the 'good' one does not. If I run it through FFMPEG with debug logging, for the 'bad' copy (which causes the issues in premiere), there are errors like this:

[h264 @ 0000020d0e43c700] Changing field mode (3 -> 3) between slices is not allowed
[h264 @ 0000020d0e43c700] decode_slice_header error
[h264 @ 0000020d0e43df00] Frame num change from 4 to 5
[h264 @ 0000020d0e43df00] decode_slice_header error
[h264 @ 0000020d0e43df00] Frame num change from 4 to 6

If anyone wants to check if their video file has any corruption even if it plays, you can use this ffmpeg command. I would be curious if it reveals a pattern. If the error.log file it outputs is empty, there isn't any issues.

ffmpeg -v error -i whatever_video.mp4 -f null - 2>error.log

I was able to get Premiere Pro to at least import the bad file by using this FFMPEG command to remux the video (just repackages it without re-encoding), which didn't fix the underlying stream corruption, but apparently fixed enough of the header stuff where Premiere imported it without causing the problem.

ffmpeg -i input.mp4 -c copy output.mp4

The output video still shows errors when doing the other ffmpeg error log command, but there are fewer and they are different. So it might be worth a try if you don't have access to a 'good' copy of the video.

-------------- Original Post Below -----------------

Reposting my reply from another similar thread, but same issue here.  Never had this problem before. After importing a video file, my CPU spins up to like 70% and just sits there. My waveform looks like it processed a tiny amount then stopped:

The first time I opened the project and tried to add the file, it said the storage wasn't fast enough or something similar. I cleared the cache and re-imported it as a different name. It spun up the CPU for like 5 minutes then it stopped, but the waveform never generated.

In ProcMon it looked like it was slamming some temporary audio file the whole time. 

System specs:

Premiere Pro Version: 25.2.1 (Build 2)
Windows Version: Windows 11 Pro for Workstations 24H2 (Build 26100.3476)

System Hardware:
CPU: Intel 13900KS
GPU: Nvidia 5090 FE
GPU Driver Version: 572.83
RAM: 128GB
Storage: NVMe SSD - Optane 905P 1.5TB

Confirming same issues in 25.2 and higher -- All sorts of failing to read errors not just in premiere but extending to my Maxon/RedGiant plug-in and in After Effects 25.2 as well. If you try to reinstall, it doesn't fix the error. I even tried to manually delete the plugins to reinstall and messed up my Red Giant stuff further. Wish I had know it was an adobe issue before doing this.

I'm having the same issue on my Macbook M1 pro. 

The file i created is not even compatible with older versions of Premiere pro so i'm literally just stuck with an unedited video. 

I imported some video files in mp4 format and some jpeg pics. It was working fine until i added one last video (also mp4). After that, it just kept getting worse and now the video won't playback at all even after re-opening the application. It's very frustrating being a paying customer to have to face this issue. 

mine too

I'm having the same issue..I use premiere for work so i hope they can fix this bug quickly.

Some computer specs:

Ryzen 9 5950x

Asus RTX 3060

RAM 80GB 3200MHZ

SSD 980 PRO 1TB

Proxies, regular mp3 files - this message keeps popping up on my machine too after the last updates. 
And there's some other weird timeline jumps and what not. Never had this issue before. 
Desktop computer with plenty of power. All Samsung EVO SSD's and M2 drives so I doubt it's hardware related. 

Same problem as everyone else here. Pretty poor show, Adobe.