Skip to main content
cheeky71
Participating Frequently
June 26, 2016
Answered

Premiere Pro CC 2015.3 constantly generating Peak Files endlessly - how can stop this ?

  • June 26, 2016
  • 21 replies
  • 42353 views

Hi there

I noticed this morning when i was bringing in footage to the source monitor there was no audio  but VLC player shows audio on the video - and then i realised Premiere pro was going into some loop generating Peak files and when it got to the one in the source monitor only then did the waveform show up - this is really quite frustrating - as I want to be able to work on footages in a timely manner - How can I sort this out - I am using an Apple Mac El Capitan - I got about 20 bins in my project file - with sequences and MXF files. I tried to look for the cache files but i can't seem to see these - could they be hidden? Any advice would be most welcome.

Many thanks,

Jay

    This topic has been closed for replies.
    Correct answer excited_Genie16B8

    This is actually normal behavior.  After importing, wait a bit before you begin work.

    21 replies

    Melodic_art1674
    Participating Frequently
    July 6, 2018

    Actually, no... there is a work around and it's not found in preferences. That doesn't work and it's why everyone is so frustrated.

    You have to do a Cmd/Ctrl+F12 to open a console menu.

    If it comes up empty, click where it says "console" and change it to "Debug Database View"

    Scroll down to "SuppressPeakFileGenerator", click the box to make it true

    No more Peak Files Generated.

    You're welcome.

    Melodic_art1674
    Participating Frequently
    July 18, 2023

    Bonjour mina-san,

    it's Kendahke1...

    updating this for Premiere pro 2023 for Mac.  Everything else stay the same for PC

     

    Hold down the Command/Function key/F12 to open the console

    If it comes up empty, click where it says "console" and change it to "Debug Database View"

     

    Scroll down to "SuppressPeakFileGenerator", click the box to make it true

     

    No more Peak Files Generated.

     

    You're very welcome.

    Time is money and wasting time on peak files while Adobe is playing the "nut role" is costly.  Reclaim your time!!!!

     

    K-

    Participant
    April 19, 2017

    Seem like adobe dont no what to do with this problem...

    Dear Adobe.... u doing a video like triller or same video for DEMO to intruduce ur product , i think u just using maybe 50gb or let say 100gb of footage... but we the user are dealing like 1TB - 3TB OF FOOTAGE. GENERATE PEAK OR LOADING FOOTAGE FOR 10 - 24 HOURS ARE STUPID.

    ** PS....  GB IS GIGABYTE ... TB IS TERRABYTE and for ur info TERRABYE ARE BIGGER THAN GIGABYTE @

    albertoc98597148
    Participant
    November 16, 2016

    Hi everyone,

    I have been having this peak files issue forever and it has made some of the projects just unworkable, to the point I had to export a full feature length docu to Avid and finish it there, wasting days of work in filters. The problem seems to be random and had seemed to go away for a few months until I had it yesterday reoccurring. My edit machine became unresponsive and I couldn't edit. Knowing that I already had the issue before I went to the cache folder and surely Premiere was creating THOUSANDS of peak files. I've been already through the "opening new project-importing" already, going back to an older version of Premiere and it didn't help, so I used the opportunity of no pressure for once to try something new: I just changed the cache folder to an external drive, deleted all pek files and reopened the project. It is working fine now and stable. I'm not saying that would fix every problem with peak files generation that you have, but it is easy and fixed mine. My guess is, as we work on a NAS (on Mac) and gather footage from different sources, the permissions are messed up. I still think this system of peak generation is crap and Adobe should do something about it, but hey, we know how it works.

    Hope it was helpful to anyone.

    Alberto

    Participant
    December 11, 2016

    I am also having this problem on PP2017. On every project I open it is making the peak files again. Luckily i have found a solution, I looked at the new release of FCPx and it works for me now. So i will run out the last 5 months of my Adobe contract whilst editing on FCPx. Great solution Adobe

    Oh I forgot to mention that I am writing this entry whilst waiting for PP to open up and get ready for the last 45 minutes. Admittedly it crashed a couple of times but it all adds up.

    One of the test I did to convince myself that going to FCPx worked for me was to see how long it took to get ready to edit on a job. So i took the same rushes and loaded them into both progammes, let them do whatever they had to do to get ready, and then restarted. PP took 23 minuets to get ready to edit, FCPx was 17 seconds.

    Still making peak files . . . . . . .

    Participant
    December 13, 2016

    My solution to this problem has been to deselect Automatic Audio Waveform Generation in Audio Preferences. No generating anymore.

    Known Participant
    November 6, 2016

    Yep, that's true. You can have many versions installed, and they live well with each other. But, for sure, Adobe should take more care about bug free experience. Right now Premiere is advanced enough for almost any editing task. Stability, speed and ergonomics should become a priority.

    Participating Frequently
    November 7, 2016

    Where is that advanced options tab in creative cloud desktop app? How can I install 2017 as new program, not the update? I know I can install previous version of Premiere Pro from "previous versions" menu (i have CS6 because of Encore which i need to burn DVDs/BDs) but I didnt know that I don't must update my current 2015.3 version to 2017 and can just install 2017 next to 2015.3 and use both. How can I do that?

    This will be good solution to install new versions and not afraid of bugs in it - if there will by any, I will still can use my last good working version.

    Legend
    November 8, 2016

    How can I install 2017 as new program, not the update?

    2017 will only install as a "new program", that's not a choice.

    The Advanced Options will allow you to keep the old versions installed (or not) and to keep your old settings (or not).

    Whether or not you keep old versions installed will have no effect on how 2017 runs, because it is installed as a new, separate program, not an "update".

    When you begin the install process, you'll see it at the bottom of the dialog.

    Known Participant
    November 5, 2016

    I guess they have fixed it in 2017 release?

    Participating Frequently
    November 6, 2016

    I'm afraid to check it out... Really One update - while playback audio was dropping out (mute) many times. Second update - sharpen filter doesn't work, clips with it are black. God bless I found out that my black clips where black because of sharpen filter, I was in the end of making video from wedding, doing it from beginning would be not funny.. Third update - endless generating peak files.

    I hope my premiere pro will never update automatically, because I don't want to have new problem in the middle of work. I DO NOT recommend performing an upgrade in the course of project development.

    If anyone do the update please write if that bug (endless generating peak files) is fixed now. Good luck folks!

    Bill Gehrke
    Inspiring
    November 6, 2016

    Why not try it your self, you can have as many versions as you want.  When you download look for the Advanced Options and select not to upgrade your current version just install the new one and it leaves your current version completely intact.  I  have four versions on this laptop for experimenting.

    November 4, 2016

    Ok, so I found an decent solution for who wants to try it , first of all close the current sesion of Adobe Premiere, then go to the location of the endlessly peaking file , take the file move it into a new folder and open Premiere again and it should ask to locate the file again , then it should work just fine. Hope this helps , have a great day !

    Participating Frequently
    November 4, 2016

    undefeatted it will take very long time to move every problematic file to another folder, everytime start PP again, wait for next file with problems, move it, restart, and again and again and again.... You can move all files and locate all in one click, but it they will cutted on timeline there will still be a problem to generate peaks. I tried to locate files in new folder earlier but it doesnt help. Just copy your entire project, open it, delete everything from timeline and move every file from libary to timeline again - they will have full lenght and will be not cutted, save it. Close copied project, open again - peak files will generate fine with no problems, you can go for coffe and dont care about all process. After peaks are generated close copied project and open the right one with your complex timeline, peaks will load fine, there will be no need to make them again.

    This is fastest way for today. Enjoy it.

    Inspiring
    November 4, 2016

    OMG people can't be serious. I would rather cut my finger with paper and then repeatedly pour salt into it. How about "Fix the problem, Adobe!" Everyone hates it and the workaround is horrible. I went back to Final Cut Pro.

    Participant
    October 24, 2016

    When I saw this thread marked "Answered" I rejoiced and began reading every response. However, the only 'answers' seemed to be extensive workarounds, not truly addressing the problem, and seemed only to work for a handful of folks.

    Currently I'm working on a 90+ minute feature, and I have had to wait 20+ minutes while Premiere endlessly generates it's peak files. And this has been a per-session problem... happening multiple times in a day, every time I quit premiere and come back... it goes back into it's Peak File generation mode, and another 20+ minutes lost waiting on it do do it's 'thang."

    Now, I'm no Premiere Expert, I've only been working on it full time for 10-months, but I'm a 20+ year veteran editor, and no stranger to non-linear editing.  And I have to say, this mode of media managing on the part of Premiere (to quote my 4th grade nephew) "Sucks The Root."  (well said, nephew!)

    After leaving this discussion thread feeling very disappointed, I continued my Google search results and stumbled up with THIS link.  (Thank you Hive-mind!)

    5 hidden features in Adobe Premiere CS6 - Blog - Digital Rebellion

    Suppress peak file generation


    Peak files allow Premiere to cache waveform information so that it doesn't need to be regenerated every time the project opens.

      I have so far done two tests, and both has totally put the kibosh on that damnable peak file generation thang.

    Hope this works for you too.

    -I believe my work is done here.

    Cheers!

    ((edited to add additional spelling errors))

    Melodic_art1674
    Participating Frequently
    October 16, 2017

    5 hidden features in Adobe Premiere CS6 - Blog - Digital Rebellion

    Suppress peak file generation


    Peak files allow Premiere to cache waveform information so that it doesn't need to be regenerated every time the project opens.

      I have so far done two tests, and both has totally put the kibosh on that damnable peak file generation thang.

    Hope this works for you too.

    -I believe my work is done here.

    Cheers!

    Thank you

    Thank you

    Thank you

    Thank you!!!

    I remembered doing this for 2014, but had forgotten I needed to go into here to change that setting.

    Participating Frequently
    October 20, 2016

    Hello! I'll share my solution for that problem I also had (endless generating peak file). I'm wedding videographer and often I'm moving my project from laptop to dekstop and vice versa. I saw that files placed on timeline with full lenght was ok, problem was with files cutted many times. For example - I have music soundtrack under whole movie and it is not cutted - PP will generate peak file of it without any problems. When I have any video files with audio on my timeline but they are cutted many times, PP will start to make peak file of its audio but it is doing it endlessly. So I tried that solution:

    - close PP

    - copy project

    - open that copied project in PP (PP will start generating peak files and, as usual, will do it endlessly, don't care about it, dont wait for end, just go to next steps)

    - delete all files from timeline

    - select all files in libary and drag them to timeline (this will place all files into timeline with full lenght, no cutted files = no problems)

    - save project and exit PP

    - open copied project once again - now PP will create all needed peak files and it will do it fine because they all are not cutted

    - wait until PP ends creating peak files, save project and exit

    - now open original project with your complex timeline - peak files will be done and you will be able to work

    I tried it once just few minutes ago and it works for me. Hope it will work for you too, and for me in next project....
    PS. Sorry for my english

    Known Participant
    October 20, 2016

    I have experienced this bug also with 4-channel MXF files! I hope it gets fixed soon...

    streamingindie
    Participating Frequently
    September 30, 2016

    This really is a problem. I have been waiting for hours for this one file to generate peaks. It seemed to work a great deal faster with the audio only files but the peaks in the 4K video are taking forever. Has anyone tried changing the scratch disk to a different drive to see if the read write to the same disk is slowing it down? Or come up with a faster way?

    streamingindie
    Participating Frequently
    October 1, 2016

    This had no effect. I have never had this problem before with PP. Been using it for years. Maybe I should go back to CS5...

    Can someone from Adobe please at least come on and Say you are working on this issue?

    September 24, 2016

    I am having the exact same problem and it's driving me crazy.  How is this not fixed yet?