Is there a way to tell what your track's peak is?

[TripleM]

I use HS 2002 (still). I looked around last night but couldn't find an answer to this...

Is there a way to determine a track's peak (e.g., -3db, -1db) somewhere in HS? If not, is there a plugin or freeware somewhere that will reliably do it?

Thanks.

 

[minofifa]

in track view, you can see the .wav's peaks and you can compare that to the scale on the y-axis. I guess that's not super accurate but if you maximize the track to fit the whole window, the scale become pretty large so you can get a good idea. Just be sure to choose the appropriate scale.

 

[minofifa]

that may also be tough if there are a lot of peaks... hmm that is interesting. there must be a way though.

 

[something cool]

Hmm... in Sonar, the VU meters in both track view and mixer view keep a running tab of values of the hottest peaks, but I'm gonna guess that HS2002 is more akin to my copy of Pro Tracks (also Cakewalk).

I took a quick look around the program and I didn't see a way to figure out how loud the loudest peak was (though I didn't dig very deep at all, I'll look again when I have more time). The best I could come up with was to go into console view, and under the playback meter options, select "Lock Peaks," which gives you a visual on how hot your loudest peak is. Again, it's not super-accurate, but it will give you a rough estimate, and with this method you can be sure you're estimating the highest peak.

Then again, I'm talking out of my ass if Pro Tracks is nothing like HS

Hope that helps.

 

[guttadaj]

That would be a nice feature to have! I always just set my meters to peak hold and then playback the whole song.

 

[TripleM]

Thanks everyone for the replies.

I noticed the "lock peaks" option on the meters. And I suppose you could drag the left half of the tracks pane way over to the right so it's really wide and add some granularity.

I didn't think of the y-axis thing. I'm guessing it would be about as accurate as the "lock peaks" method.

I was just wondering if there was something "precise." You know, like something that will just spit out a number - "-3.2db on the left, -3.3db on the right." Oh well.