peak file problem

[dobro]

I'm having a problem with peak files. Or lack of them, actually.

When you enable the peak file feature, you can load a massive mix in about a second - it's really fast - but if you don't enable the peak file feature, it takes forever to load a large mix, one track at a time.

Okay, so I've always got the peak file feature enabled.

But sometimes, for some reason I can't figure out, Cool Edit saves a session and doesn't give some of the tracks pk files. I would like to know why that is, so that I can avoid it if possible.

But what's *really* driving me crazy is my complete lack of success at getting peak files attached to the wav files that lack pk files. I've tried everything I can think of: I've cloned the track and saved it; cloned the track and changed something and saved it; imported the track from a folder outside the session; changed the cloned track in terms of bitdepth; and lots of other things that I'm too frustrated to try to remember. It's like the original wav file without the pk file has got some kind of voodoo on it that absolutely refuses to have a pk file attached to it or a copy of it, ever.

Anybody know anything about this? I'm tired of waiting half a minute or more for big mixes to load.

 

[SuicideNote]

.pk files aren't available for 24-bit recordings. Unless you record in 16 bit you are SOL and will have to deal with the fucking 40 minute load times.

I assumed that you use 24-bit settings.

 

[SuicideNote]

Wow, I missed that 1/2 a minute nonsense. You must have a Pentium 4^12. Simple 8 track, 5 minute songs take 25 minutes or so for me.

 

[dobro]

".pk files aren't available for 24-bit recordings. Unless you record in 16 bit you are SOL and will have to deal with the fucking 40 minute load times."

Bullshit. I have dozens of sessions done in 24-bit, all of which have peak files attached. It's just the occasional instance of Cool Edit not creating the peak file for a particular track in a session where the other tracks have all got their peak files.

 

[MadAudio]

It's just the occasional instance of Cool Edit not creating the peak file for a particular track in a session where the other tracks have all got their peak files.

I'm not familiar with Cool Edit, but Vegas has a function to rebuild peaks. Maybe you have something similar?

 

[SuicideNote]

".pk files aren't available for 24-bit recordings. Unless you record in 16 bit you are SOL and will have to deal with the fucking 40 minute load times."

Bullshit. I have dozens of sessions done in 24-bit, all of which have peak files attached. It's just the occasional instance of Cool Edit not creating the peak file for a particular track in a session where the other tracks have all got their peak files.

No you are wrong, you should check out the official Adobe support forums if you don't believe me. I leared of this after upgrading my recording interface.

 

[SuicideNote]

You'll probably need to creat an account to view this link, so I'll post the content here.
http://www.adobeforums.com/cgi-bin/webx?13@328.K1M3fYahuff.6@.3bbb8946/5

Inconsistent Peak File (PK) generation

UrbanVoyeur - 09:47pm Jul 28, 2005 Pacific

I like the peak files because they speed up load times, but it seems
that they are not consistently generated on my system. I have the option
turned on, and I am working in 16 upped to 32 bit files. It seems to
happen most often with 32 bit files. 16's almost always generate a pk.

Also, 24 bit files (24 as 32 bit, direct from the recorder) almost never
generate pk files.

Any ideas? (I already searched the knowledge base, faqs and forums)

--

J

www.urbanvoyeur.com

| Back to Topic List | Bookmark | Subscribe
To start a NEW discussion click on the Back to Topic List link and select Add Topic.
If you are in an archive forum please go up to the main topic list (archives are read only).

Messages
8 messages. Displaying 5 through 8.
First Previous Next Last Show All Messages

SteveG - 12:11pm Jul 29, 05 PST (#5 of 8)

Well, then it shouldn't be happening. Anybody else ever experienced this?
| Bookmark back to top
Ozpeter - 4:24pm Jul 29, 05 PST (#6 of 8)

I think if the files are very short .pk files are not created, but in that scenario it doesn't matter.
| Bookmark back to top
zemlin - 6:18am Jul 31, 05 PST (#7 of 8)

In my experience, PK files are only saved with 16-bit and 32-bit WAV files. I record with a different app that creates 24-bit files. I need to convert those to 32 bit before Audition will save PK files.

Somewhere long ago I had an OFFICIAL reply saying that was how it worked, but I don't know when or on what forum that was.
| Bookmark back to top
SteveG - 7:01am Jul 31, 05 PST (#8 of 8) Edited: 31-Jul-2005 at 08:10am

Somewhere long ago I had an OFFICIAL reply saying that was how it worked, but I don't know when or on what forum that was.

The details I posted are from an official reply - and are exactly as you posted. Synt MD said this on the 'original' forum, and it's still there in the AudioMasters archive of it (as long as you don't try to use IE to locate it, that is...) it goes:

Cool edit will only create peak files for the 32-bit 16.8 float /16-bit wave formats because these are native to CE. It will always re-scan straight 24-bit files.

---Syntrillium, M.D.

and this was extended to incorporate the 'new' native format.

 

[dobro]

Oh alright.

"Cool edit will only create peak files for the 32-bit 16.8 float /16-bit wave formats because these are native to CE"

That's correct. Cool Edit records and mixes in 32-bit floating point. Which is what *all* sessions are naturally in until you dither them down to CD quality at the end. So - all my sessions are done in 32-bit floating point (Cool users usually call it 24-bit, cuz that's what the rest of the world recognizes, but actually it's the 32-bit floating point thing.). But occasionally, when I save a session, although most of the tracks have pk files attached, one or two sometimes don't have a pk file attached to it. I don't know why it does this.

MadAudio - I'll check out that 'pk rebuilding function' you mentioned, but if Cool had it, I think I would have heard about it by now.