raise the level of the peak in DP

[fafalio]

dear friends, suppose i have recorded a concert at -10 dB as peak.
i want to take the recording and to reach -3dB as maximum peak.
so i need two things.
A) how tell DP to identify the maximum peak in the song and tell me the value
B) take the level identified by digital performer and reach to -3dB

can you tell me the way?

thanks in advance.

Alessandro.

[Kubi]

1. Insert a trim plug
2. Play back the track.
3. Read the peak level and add as many dB as you need with the trim plug's gain knob to reach -3dB

If you then wanted to process the sound file permanently, you could bounce the track.

[Tim]

Normalize, then Trim -3dB.

It would be nice to have a max peak setting in the Normalize function (lke some other apps do).

[Kubi]

Also possible, though the only comment I would make is you may lose some fidelity, since you go from 24bit fixed original recording to 32 bit float for the normalize process, then back to 24bits fixed to write the file, then back to 32bit float to trim -3dB, and back to 24bit fixed to write that to disk. If you use the trim plug the whole way, you stay in 32 bit float for the entire re-leveling process until you commit to the new level as a 24bit file. This issue is admittedly probably below the threshold of relevance, but still worth considering...? I'm a geek, I know...

[Tim]

True, and a good reason to have a max setting in Normalize - making it all in one process ( I would think).

Does Merge do the same 32 to 24 thing?

[Kubi]

I would think so, although since merge usually doesn't involve any major processing outside of a few fades, I usually don't worry about it.

But every time you read audio, process and print, you go 24-32-24, definitely not a lossless process I would think. Would be easy to test - take a complex mix sans the time-based or random processes, but with plenty of subgroups etc. Bounce the whole thing, then print the sub groups etc. bounce the whole thing again, see if they null....

Another interesting question is if there are any reasons to consider the differences between DP processes (merge, destructive fx print, etc.) and MAS processes (bounce, record, etc.) Wouldn't think so, but what do I know?

[Tomrabbit]

It would be nice to have a max peak setting in the Normalize function (lke some other apps do).

+1. Seems long overdue.

[FMiguelez]

But every time you read audio, process and print, you go 24-32-24, definitely not a lossless process I would think. Would be easy to test - take a complex mix sans the time-based or random processes, but with plenty of subgroups etc. Bounce the whole thing, then print the sub groups etc. bounce the whole thing again, see if they null....

Oh, Oh. I tend to be very obsessive. I should NOT be reading these things