Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro premiere pro always generating new peak files

  • premiere pro always generating new peak files

    Posted by Stan Weiss on February 21, 2013 at 6:06 pm

    I am running win 7 and prem pro CS6 on both my home and office machines…and I often carry a portable hard drive with my projects and all of the project files…
    and i find that when premiere pro CS6 opens a project it always needs to regenerate the peak files over again…all the time…
    I have checked and all the preferences show that the media scratch discs and and all the media cached files are all contained in my portable hard drive and it is set that way on both of my machines..and on both my computers the drive has the same letter designation….

    Any idea why it loses those peak files and has to always regenerate?
    Some of the longer peak files take a long time to regenerate.

    thanks in advance…
    Stan

    Tim Kolb replied 13 years, 2 months ago 4 Members · 3 Replies
  • 3 Replies
  • Chris Borjis

    February 21, 2013 at 7:20 pm

    I’m annoyed by this as well. I’m on the MAC version.

    I hope they address it in 6.5

  • Jeff Pulera

    February 22, 2013 at 5:54 pm

    Not sure if this would affect you, but I read an interesting post yesterday that suggested that the common problem of files needing to conform every time a project is opened was due to the system clock being different between various machines on the network, and in your case, maybe on the other machine you edit on?

    Therefore the time stamps on files might not make sense on another system, for instance if they are a future time, so Premiere rebuilds/refreshes certain files.

    I think for a Mac network, “NPT” was referenced, some sort of timing indicator in the network? I’m a PC user

    Thanks

    Jeff Pulera
    Safe Harbor Computers

  • Tim Kolb

    February 26, 2013 at 3:26 am

    Interesting, Jeff…

    Typically, a frequent reason for this is the application’s permissions to save its media database on the targeted drive, but in this case everything targeted to the media drive and the same drive letter assignment.

    The system clock is a new one on me, but one of the better hypotheses I’ve heard.

    TimK,
    Director, Consultant
    Kolb Productions,

    Adobe Certified Instructor

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy