Audio Previews folder keeps appearing in the same directory as the project file

[Flavio_St]

Audio Previews folder keeps appearing in the same sirectory as project even though in my project setings the location for them is Documents (the default one). Also in my media chache prefences I have "Save .cfa and .pek media cache files next to original media files when possible unchecked."

This buggy Adobe Premiere Pro Audio Previews folder contains another folder with theprojectname.PRV format but it is empty. At the same time the real Audio Previews folder with the peak files is created in the Documents location.

This is a ver annoying bug, please fix this before launching new features.

Using Premiere Pro 25.1 / Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz 3.60 GHz / Windows 11 Pro
Version 24H2 OS build 26100.2605

[ScottSimmons]

I've seen that same thing with the Audio Previews folder. It's a very annoying thing indeed, especially if your project files are being saved into Cloud Storage.

[Rach McIntire]

Hi @Flavio_St ,

Thanks for submitting your bug report. We’re happy you’ve reached out. Are you using a Production project or a regular project?  It sounds similar to another issue we are tracking which it looks like you already found.  If yours is the same I can escalate it and see what can be done.

Best,
Rach

[Flavio_St]

Thanks. It's a regular project. Happens on mac too. People may have not shouted about it cause it's an empty folder and doesn't really take space but for us, the super tidy people with almost OCD behaviours it's really annoying.

[Flavio_St]

What's the new status? this keeps happening with the latest version.

[Rach McIntire]

No update yet, but we are aware of this behavior.  Thanks for your patience.

[ScottSimmons]

So what can't this get fixed? It's a known issue, well-documented that's been going on for over a year now. Premiere literally ignores where the scratch disk is set. There are many cloud-based workflows where the projects live in a cloud service, and this bug has Premiere writing non-project files into that cloud service. Does Adobe not see how this is a problem?