How to find the average peak of your track?

[d-track]

ok then i got it. thanks.-
i just didnt notice because 24 bit noise floor is inaudible to me.
and i thought that live normalizes that way realtime as firt find the highest peak then adjust the master volume to it,not like for example soundforge does.

[bgelber]

this doesn't solve my problem. can someone clarify, IS there a way to QUICKLY find the peak? i don't want to play through a 2 hr mix just to find it. is there an info panel somewhere, or maybe it's a function on Audacity or another program like that?

[TomViolenz]

this doesn't solve my problem. can someone clarify, IS there a way to QUICKLY find the peak? i don't want to play through a 2 hr mix just to find it. is there an info panel somewhere, or maybe it's a function on Audacity or another program like that?

No there isn't. And I honestly find it weird that people in this thread seem to be satisfied with just seeing the peak level:
a.) after the whole thing has played through, and
b.) just as a single value not telling you at what time it happened and how many other times it went over zero.

I mean, how hard can it be to at least write the meter reading that Live is doing into an automation envelope in Arrangement, so that you see what part had what volume?!
This way you could easily decide, if it's an important often occuring thing, you solve with a compressor, or if you just need to turn the volume of one track down at a specific time for a non-essential element. Thus avoiding the use of a compressor.

Any free tools to do this?! I'm thinking maybe Macrobats SidechainRack could be used for this. Assign a macro to the measured level and then record the movement of that macro into Arrangement. I think I'll try that

EDIT: (this solves complaint b.)) I tried it and it works. The only caveat is that it gives values on the automation envelope in Arrangement as a value between 0-127. But it should be easy to find out what corresponds to what dB. You can have one of them on each track and the Master and then compare in Arrangement all of them on top of each other to see what happens at what time and which track is likely the offender! Clyphx just never ceases to amaze me in how useful it is!
I also suggest when doing this to choose the least agressive break point thining in the Options.txt, so that you have a very detailed reading. Wonder why I never thought of doing this before. Thanks for bringing up this thread, to get me to think about this