Re: Advice on Compressor Effect?
Posted: Sun Sep 26, 2010 1:00 am
I know the original post was a month ago, but I just read it -- as I was thinking about posting a note about how much more useful and effective I think the Compressor effect is in 1.3.12 -- which I've just started using -- than in the older version I'd been using.
Maybe my thoughts as to what I really like about it so far are applicable to your question/comments? Let's see.
By choosing the option to compress based ion PEAKS vs RMS -- which, I assume, is an average-type basis -- I've been able to greatly reduce the spikes and the loudest passages in my recording while raising the softer parts, resulting in a much easier to listen to -- and to hear everything without either constantly adjusting the volume of playback or having parts that are too loud and others that are too soft -- final product.
My own application is taking recordings made from the soundboard for the concerts I produce and turning them into CDs for my personal archives and listening pleasure.
Among the things that cause spikes are:
* Guitarists unplugging while their channel isn't muted
* Bumping a mic
* A shout at a much louder volume than they sing and play at
* Etc.
Thing like those result in a WAV file in which 99% of the program material is at a relative uniform level while 1% -- probably more like 1/10th of 1% -- is spiked to the maximum DB short of distortion.
I used to have to select those spiked parts -- by zooming in close so I could select only the spiked part -- and reduce the selected part by using Amplify with a negative db number. Using Compression on the old version reduced them a BIT, but not nearly as much as they needed to be.
In the new version, by choosing the option of compressing based on PEAKS, the peaks are greatly reduced while the rest of the material is raised in volume/level.
I'm using values of -20db (Threshhold) and 5:1 (Ratio). See if that might work for you.
.
Maybe my thoughts as to what I really like about it so far are applicable to your question/comments? Let's see.
By choosing the option to compress based ion PEAKS vs RMS -- which, I assume, is an average-type basis -- I've been able to greatly reduce the spikes and the loudest passages in my recording while raising the softer parts, resulting in a much easier to listen to -- and to hear everything without either constantly adjusting the volume of playback or having parts that are too loud and others that are too soft -- final product.
My own application is taking recordings made from the soundboard for the concerts I produce and turning them into CDs for my personal archives and listening pleasure.
Among the things that cause spikes are:
* Guitarists unplugging while their channel isn't muted
* Bumping a mic
* A shout at a much louder volume than they sing and play at
* Etc.
Thing like those result in a WAV file in which 99% of the program material is at a relative uniform level while 1% -- probably more like 1/10th of 1% -- is spiked to the maximum DB short of distortion.
I used to have to select those spiked parts -- by zooming in close so I could select only the spiked part -- and reduce the selected part by using Amplify with a negative db number. Using Compression on the old version reduced them a BIT, but not nearly as much as they needed to be.
In the new version, by choosing the option of compressing based on PEAKS, the peaks are greatly reduced while the rest of the material is raised in volume/level.
I'm using values of -20db (Threshhold) and 5:1 (Ratio). See if that might work for you.
.