-
Generating Peak Audio Files – A Fix Found
So, I started a new project in Adobe premiere, and suddenly, as everyone has probably experienced, I noticed that my project was generating these audio peak files every time I opened my project. This was a first for me. I spent about an entire day reading every single blog, I could find on the subject, and read about how people’s projects were “out of control” re- and re- and re-generating these files every time the project opened. It’s bad enough the indexing seems to be an on-going battle, waiting for that, but I did take a few blogs suggestions, and tried everything. Nothing worked. So then, I tried a combination of things, nothing, then suddenly, something happened, and now, no peak files being generated! It was the order in which I did the assessment and the order of steps, as follows:
1.) First, go into your problem project, and delete ALL of the Media Cache and Media Cache Files. (Many blogs tell you that this is a CS4 bug, which it may be, or a corrupted file thing, or a check or un-check the box in Prefs where you click on the Save your media reference files in with your original media, this will clutter you drive, so I was not going to do that, leave all Prefs as is.)
2.) Second, open a “New Project”, and reset up your scratch files so that all the project files go to the place where you need them to go. In this case, I need to be mobile, so I set it the external drive.
(Even if your drive is “already” set to where you left it from the previous project, click it to the desktop, then click back to the place where you want. This just makes your computer think and ensures that things are “refreshed”, in a sense, this is all you’re doing.)
3.) Third, open the new project. It opens.
4.) Open your problematic project “from within” this “New Project”.
5.) Premiere rebuilds the peak file directory, let it run. What it’s doing to refreshing and completely rebuilding the directory.
6.) When it is done, “Save” and “Close” Premiere.
7.) Re-open Premiere, and look down at the bottom, after the media has loaded and the indexing is done, will will either see no peak files being generated, or you may see one or two, but for me it was like 2 seconds for the 2-3 peak files to generate. I caught a glimpse of what peak files there were, wrote the file numbers down, and went into the media drive, and identified them as healthy clean files. But there were 2-3 files that were still generating every time, so, I deleted the media from the Premiere project, and re-imported the three files. Saved, closed, and re-opened the Premiere Pro project, and now, it looks like only one peak file is generating, after multiple repeated steps of removing this file from the project and reimporting, the peak file takes a half second to generate, so it’s like there so peak files at all that are generating.
I don’t know if this will work for you, but it appears that I went from tons of files generating to almost none. Now, every time I open the project, there’s a split second glimpse of one file generating in a second, but it’s not a bother now. I’ll let that one peak file slide, if that’s what it takes, I’m ok with this weirdness, as long as it’s one file, and it takes a half second to regenerate, who cares, right?
Let me know if this worked or did not work for you.
Thanks everyone,
Tom Laughlin
Producer/Editor
Digital Chop House
Salt Lake City, Utah -
3 Replies
-
First of all, thank you for being one of those people who takes the time to research an issue then share your findings with the community. I can’t tell you how much I appreciate that. This is really good advice and I am sure our tech support department appreciates the assist as well. 😉
Second, it looks like you are using Premiere Pro CS6 or earlier. Another option would be to upgrade to Premiere Pro CC. I spent a lot of time working with our developers on the issue of regenerating PEK files and I feel pretty confident you will find the experience to be much improved.
Tom Nord
Quality Engineer
Adobe Media Encoder -
Thanks for posting a work around.
I’ve been very lucky to never have this problem.
I always set the cache files for a temp folder on my disk array
and all other files to the project file folder.The indexing will always re-occur if you move a project from one disk/array/workstation
to another, but if you go back to a disk/array/workstation it had previously been
on it won’t index again. -
This worked when nothing else did, thanks Tom!
Reply to this Discussion! Login or Sign Up