I've even selected "Create one file per clip" in the "Save As" dialog when
saving a project. Does this literally creat an audio file for each of my
voice clips? Or does it put all my voice parts in one? I'm confused!
_____
From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Bill
Sent: Monday, November 16, 2015 4:51 PM
To: ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] Re: Normalize Command In Sonar
Hi,
Use Un-under the Edit menu do and try again. This time reduce the value to
a negative number and see if results improve. Change the value in the DB
edit field or by using the related Slider.
You have probably read the following but, for the benefit of anyone who has
not read it, here's the text from the relevant section of the CakeTalking
8.8 tutorial:
.
36F. The Normalize Dialog.
1. As stated earlier, if you have pasted or nudged a clip to another
position in the project, you might find that there is a gross miss-match of
audio levels. To correct that, you can increase or decrease the level of one
of the clips. The Normalize dialog is a convenient place to do that.
2. To open the Normalize dialog, select the area of the audio that you wish
to change, and open the Process menu. At the top of the menu is, Audio.
RIGHT ARROW to open the Audio sub menu, and ARROW to Normalize, and press
ENTER. The normalize dialog will open.
3. In the Normalize dialog, you can select presets from the Preset menu, and
then press the Audition button to hear the result. Or you can make your own
setting by using the slider, or the edit field. The Gain dialog can process
both stereo and mono tracks.
4. You can make your settings in either the DB edit field, or with the
Slider. The slider reads percentages, and the edit field reads DB levels. If
you set the slider to 100%, then the edit field will display 0 DB. Note that
0 DB, is the maximum level. So, the loudest part of the existing audio, will
be put at 0 DB, and everything else in the selection will move up
proportionately.
5. The other available settings, are in the minus DB range. This does not
necessarily mean that you will be cutting the level of your audio to those
specific negative settings. It just means the loudest part of the audio will
be set to that level, and everything else will be moved up or down
proportionately. For instance if the loudest part of your audio is at minus
4 DB, and you make a setting of minus 3 DB, then everything will be
increased by 1 DB. On the other hand, if the loudest part of the audio is at
minus 2 DB, and you make a setting of minus 3 DB, then everything will be
decreased by 1 DB.
4. Once you've Okayed the dialog, back up a little and playback. If you're
not satisfied, undo, and try again. Note that the Normalize dialog applies a
destructive edit. So to change what you've applied, you have to undo either
with CONTROL+Z, or use the Undo History.
----- END OF LESSON -----
.
From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Annabelle Susan Morison
Sent: Monday, November 16, 2015 7:30 PM
To: ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] Normalize Command In Sonar
Hi, it's Annabelle.
When I tried the normalize command in Sonar on a single audio track,
unfortunately it turns all the rest of the audio tracks up way loud, so it
sounds like the speakers could be blown. Is there something I'm doing wrong?
Maybe there's a better way to normalize just certain parts of a track.
Specifically I'm working on a voice track, where I've put several clips of
my voice from different takes into one track. However, I want to normalize
only the ones that are quieter than the rest of the audio. I want all my
voice clips to blend in with the audio, and I'm not sure how to go about
that other than rerecording my voice, which won't sound the same as these
clips, which are "the best of the best" takes. I want to work with the
volume trim command, but even I can't figure out how to normalize with that.
The quieter parts seem normalized when I put the trim at 4.8, then the parts
that are louder than the quiet ones are fine when the trim is back to 0.0.
