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

SAME HERE

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

@gordonw50483927  @lightstone1992 @Paul2971790848zl @ashlayw 

Can you try using ffmpeg to see if the video file has any corruption? I have a particular video file that got corrupted when copying it off my SD card the first time. Then I have a 'good' copy of the same exact file. The corrupted one caused this issue same with the latest version of Premiere only, and the "good" copy of the file has no issues.

To check if a 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 aren't any issues.

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

Possible workaround 1, if the command above reveals file corruption:

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.

I highly suspect the problem is down to an apparently new video engine/converter mentioned in the update: "Completely rewritten support for MKV (H.264/AAC) files to improve compatibility and performance"

--------

I also found that I was getting issues with Premiere using at on of CPU when loading media, and even more-so with the bad file. The high CPU usage at least seems to becaused by the new settings under Preferences > Media Analysis & Transcription. Disabling "Analyze all imported media to visually search your projects" and "Automatically transcribe clips", so you can try disabling those.

--------

Potential workaround 2 to try, for some issues  (like I couldn't get it to generate a waveform in the timeline) - We're basically going to use an old version of Premiere to just create the metadata files for the video clips:

1. Without a project open,  go to Preferences > Media Cache >  Enable "Save .cfa and .pek media cache files next to original media".
2. In the same menu next to "Remove media cache files" click "Delete", then select "Delete all media cache files" (this one is apparently only available if no project is open).
3.  It will restart Premiere. DO NOT open any projects, just close Premiere Pro 2025
4. Launch a previous version of Premiere Pro such as 2024 from last year - DO NOT open any projects yet 
5. Go immediately to Preferences > Media Cache > again Enable "Save .cfa and .pek media cache files next to original media" and hit OK. (You shouldn't have to delete the Media Cache files again since I believe they're shared)
6. Create a blank new project and import any clips that were causing problems, or just any clips you'll need. Let it create the .pek files, and any other metadata files, that should now appear next to the corresponding media files.

7. After Premiere Pro 2024 finishes generating the files, close it and re-open your project in Premiere Pro 2025.

Just to add, I am a YouTube content creator and this is having a HUGE negative impact on my workflow. I cannot proceed because audio is not reliable...

Also having this issue...my audio is on very high speed NVME M.2 so speed is NOT an issue...when will this be fixed?

Just updated and i have this issue. When will this be resolved?

My suggestion to the team at Adobe:
(1) Re-name 25.1 as 25.3 and roll it out
(2) Issue an explanation and an apology
(3) Refund all active users of Premiere Pro a month's subscription

I'm with you! This is having a very negative effect on my work and putting me in really awkward situations of trying to blame software for missing deadlines. Which is a great way to kill someone's carreer. This reminds me of when Final Cut went from 7 to X and left a whole industry stranded. Which is how Adobe rose the the prominence it currently enjoys. I can't imagine they have much more of a runway on fixing this before this story gains traction and they lose a million customers. 
I also think that there's something more than meets the eye going on. The CPU usage I'm seeing when using Premiere is astronomical — which tells me they are trying to teach Firefly on MY TIME, with MY WORK, and MY MONEY. 

I also got this error message in one of my projects even though the disk is a fast SSD

Add me the list. Downgrading to 25.1 as we speak.