I figured I've got some technology here, so I might as well learn how to use it to speed up the process. It's just that these excessive spikes are causing the rest of the recording to be rather quiet. I remember someone in a previous discussion suggesting that the full dynamics of the voice are needed in the spoken word and to an extent, I would tend to agree. On first blush, it doesn't sound bad but it's hard to tell if this would suit the discerning ear or the equipment it's likely to be played back on. So far I've got as far as applying the default setting and what I end up with is a very mechanical looking waveform. Of course, I'm not aiming to remove all of the variance in the waveform to undynamic blandness but some form of conformity of the peaks is what I understand as the job of a limiter and this is what I want, only to a less aggressive degree. It could actually mean the difference in turnaround for my business, if you add all the minutes I spend manually editing. Now I've just discovered that I can apply a limiter algorithm to the waveform which saves a lot of manual work. I DO listen more than I look at waveforms on the screen and the question surrounds what I should be aiming for in audible terms. I've learned to associate what I see with what I hear in a reasonably accurate manner. Then, when normalisation takes place, I get a louder recording overall.īefore anyone says 'Stop looking and listen.' let me say that the visual waveform is my indicator of what's going on, before I hear it. So I do often find myself manually attentuating some of the naughty spikes.

When I record my speech into the audio logger, despite my experience with voice work, there are always some inevitable peaks which cause a limitation to the normalisation algorithm, in that the waveform won't normalise anywhere past 0dB (which is the whole idea of normalisation, right?). In trying to speed up my game here, I decided to experiment with a limiter algorithm and wonder if I'm wise to use it.

How to use fruity limiter