Known Participant

Question

CS6 - Generating Peak Files every time I open the same project?

Forum|Forum|13 years ago
June 5, 2012
9 replies
26785 views

CS6 wants to generate peak files every time I open the same project. I had a similar problem once with CS5, and when I unchecked the box telling the applicatio to save media files near their originals it went awat. But this box is still unchecked, and yet PP keeps wasting time and processing with this task. How can I get the program to recognize the Peak Files it has already created?

This topic has been closed for replies.

M

marshalllee16

Participant

Hey All !

I haven't seen anything on this thread for a LONG TIME. I'm cutting on a loaded iMac and using Premeire CC. From the time stamp of Nov 2014 and i'm running into this lame Generating Peak File issue. Cutting Canon C500 and C300 footage so MXF media. Every time I open up my project it needs to Generate Peak Files all over again. Has anyone from ADOBE responded to this mess ?

Thanks

Marshall

D

Diego F L

Participant

Where do you have your cache locations set to?

Moergestel_TV

Participant

Hi All

I am a new CS6 user (used older version until recently). The generating-peak-files-every time-you-open-a-new-project bug is a serious one for me.

Is this bug finally solved? In which version?

Specifics are: very simple files (SD, PAL 50fps). It strikes me that this bug has not been solved upon the first user complaint, because in CS3 or PPro 2.0 this has always worked fine.

Btw: we are working with W7. Is that perhaps a part of the problem?

E

excited_Genie16B8

Legend

(SD, PAL 50fps)

That's something of a contradiction. SD had only one frame rate, 25i, or 25 interlaced frames per second. 50 fps didn't show up until the advent of HD.

Moergestel_TV

Participant

Hi Jim

You are right, it should be SD, PAL 25i. I am still wondering however if the Generating-Peak-Files-Every-Time-... bug has been solved by now.

W

WBoswell

Inspiring

Same problem with PP CS6 trial after latest update. The link provided above to report it doesn't work anymore.

jstrawn

Legend

Folks, please just list your media spec out like this:

File format: MPEG Movie

Codec: MPEG-1/2 Video (mpgv)

Resolution & Interlace vs Progressive: 1440 x 1080 (1080i), 25fps

video files were captured with Premiere CS6 from a HDV tape

D

Diego F L

Participant

File format: QuickTime MOV

Codec: ProRes (Proxy)

Resolution & Interlace vs Progressive: 1920 x 1080 (1080p), 23.976fps

video files were transcoded via Final Cut Pro Log and Transfer from tapeless media that was transferred to a shared network drive

jstrawn

Legend

I filed a bug on this against CS6. I remmeber it well because it was the #1 pain point for my own workflow projects. But it's media-specific so it hasn't been fixed for everyone. The media I was using to get the bug was 720p motion jpegs inside an mov wrapper. (system file info shows Codecs: Photo - JPEG, Linear PCM) The only workarounf is to transcode to something different.

In order to escalate the bug, what I need from each person is to know what kind of media you can repro it wth 100%. The main info I need is:

File format

Codec

Resolution & Interlace vs Progressive (720p, 1080i, etc)

josephs51576386

Participating Frequently

Good to hear that. I havent ran into the problem in quite awhile, but oddly enough all I did to fix it was I ended up doing a reinstall of CS6 (then updated the software) and the problem went away. The media I was experincing the issue with was BMD's MJPEG codec. So apparently it is indeed media specific. We actually experinced the issue with very similar media.

The media it occurred with for me was

1920x1080i (uff) using the BMD MPJEG codec inside a .AVI cotainer.

I can't reproduce the problem anymore though, sorry. Basically when it was occuring simply opening a project caused it to occur. Even though it had already loaded the files several times before.

jstrawn

Legend

@ ComputerNovice: Thanks for the info. It is helpful and I added it to the exisitng bug report. I'm glad it went for you, but what I was encoutnering definately did not go away after re-install, which i would have done daily back in the CS6 dev timeframe.

@ Bugzke: Thank you as well. it is really helpful to have al the specifics listed out liek that so i can jsut paste it right into the bug.

B

Bugzke

Participant

same problem here, anyone found a solution?

J

jnichols9999

Participant

The ability to control peak file generation was added as an Audio preference in version 6.0.1

See http://blogs.adobe.com/premiereprotraining/2012/05/premiere-pro-cs6-6-0-1-update-bug-fixes-and-improved-opencl-performance.html

S

StevedocmakerAuthor

Known Participant

Thanks, that seems to be a step in the right direction. This seems to help, but introduces new problems. Firstly, premiere still wants to conform every file in the project each time it's opened. Less of a time suck than before, but still a time suck. Second, audio tracks do not import completely, they just drop off to nothing, which makes the program essentially useless.

Do I get anything for beta-testing this?

josephs51576386

Participating Frequently

It didn't fix my problem either, it just continues conforming things over and over even after I disable it...

R

rlmilton

Participating Frequently

I have the same issue... Mac with SSD and space is a premium... not only does it conform and generate peak files multiple times which is time consuming... it also significantly increases the amount of SSD space being consumed and that is costly...

conleec

Participant

I'm a complete PP newbie, so I'm not sure if I'm having the same thing: everytime I open my project it says something along the lines of "conforming clip X of X" at the bottom. I currently have over 8,000 clips so it takes quite a while to complete. I just assumed this is normal behaviour for PP, so I didn't bring it up until seeing this thread. Is it not supposed to do that?

Chris Conlee

Mac Pro (4,1)

OS X 10.7.4

24Gb RAM

GTX 285 (latest)

Matrox Mini Max (3.1)

PP 6.0.1

R

rlmilton

Participating Frequently

In past versions of Premiere, I would only see this happen upon first ingest of the media. After that, it would never occur again unless your cache was deleted.

josephs51576386

Participating Frequently

This is actually a issue I have noticed a few times as well while using the Premiere cs6 trial. Hopefully adobe will be able to address this issue or at least explain how to fix it. Because I never had this problem with cs4-cs5.5