JazzSinger
Max Output Level: -73 dBFS
- Total Posts : 895
- Joined: 2004/07/06 16:30:59
- Status: offline
"Normalize" produces random results after using it a while
I am fixing multiple vocal clips of the same singer from various sessions. To get appropriate basic levels, I am using Process > Apply Effect > Normalize I am applying different normalization levels, depending on the clip. So I am constantly adjusting the normalization amount. The first clips normalize fine. But after a while I start getting random results. To make it work correctly again, I have to click on a few other clips, then return to the one I am normalizing. Time-consuming and another small detail the bakers should look at. Sonar X1d ex 64bit, Win 7.
|
Lynn
Max Output Level: -14 dBFS
- Total Posts : 6117
- Joined: 2003/11/12 18:36:16
- Location: Kansas City, MO
- Status: offline
Re:"Normalize" produces random results after using it a while
2012/04/29 12:48:43
(permalink)
I can see how that would be frustrating. However, have you thought about using volume envelopes instead of normalizing? Envelopes are non-destructive whereas, normalizing is destructive. If you prefer normalizing, I hope you do it on copies of the original signal just in case you want to start over or make changes.
|
BluerecordingStudios
Max Output Level: -72 dBFS
- Total Posts : 916
- Joined: 2005/05/22 07:19:10
- Location: Nitra, SLOVAKIA
- Status: offline
Re:"Normalize" produces random results after using it a while
2012/04/29 13:19:58
(permalink)
You shouldn't normally use normalization...
|
chulaivet1966
Max Output Level: -83 dBFS
- Total Posts : 384
- Joined: 2003/11/09 12:04:25
- Status: offline
Re:"Normalize" produces random results after using it a while
2012/04/29 13:59:50
(permalink)
Personally....I wouldn't use normalize at all unless I had some bad signal levels from old recorded material I was trying to salvage from tape or something similar. As suggested, I would use 'envelopes' instead. This 'normalize' topic has many strong application opinions pro/con. So...I do think it has it's place but not on tracks that could (should?) be tracked again to get it to a comfortable -10/-12 db. I think of 'normalize' as a musical tourniquet to be used as a last resort. That's my take on it....carry on.
|
JazzSinger
Max Output Level: -73 dBFS
- Total Posts : 895
- Joined: 2004/07/06 16:30:59
- Status: offline
Re:"Normalize" produces random results after using it a while
2012/04/29 15:04:52
(permalink)
Envelopes?!? If I read these fora, all I hear is complaints about how broken envelopes are! Besides, I needed more than the additional 6db available the fader offers. Normalization needs to be fixed.
|
chulaivet1966
Max Output Level: -83 dBFS
- Total Posts : 384
- Joined: 2003/11/09 12:04:25
- Status: offline
Re:"Normalize" produces random results after using it a while
2012/04/29 15:18:04
(permalink)
Jazzsinger....I'm still on 5.0PE but does X1 have 'Process/Audio/Gain' in the menu choices? That may be a better alternative even if you have to it 2 times on the same track in 3db or 6db increments. Then the faders will be more applicable. I haven't had envelope problems myself. Just a shot from the hip here...carry on.
|
JazzSinger
Max Output Level: -73 dBFS
- Total Posts : 895
- Joined: 2004/07/06 16:30:59
- Status: offline
Re:"Normalize" produces random results after using it a while
2012/04/29 16:06:45
(permalink)
Yes it does, and in fact I did alternate between normalize and gain, depending on the clip. (some clips had sudden peaks which pushed down the average normalization level) I didn't notice the same effect using Gain, but I didn't use it as much, so I cannot be sure it isn't also affected.
|
chulaivet1966
Max Output Level: -83 dBFS
- Total Posts : 384
- Joined: 2003/11/09 12:04:25
- Status: offline
Re:"Normalize" produces random results after using it a while
2012/04/29 16:13:10
(permalink)
Well...you might tame all the peaks with an envelope, bounce to clip and then utilize the gain process further to get the track to -12 db or so. Success my depend on the original track problems so YMMV. Ha...I'm really not trying to complicate things for you, just trying to help with your audio track dilemma.
|
David
Max Output Level: -86 dBFS
- Total Posts : 231
- Joined: 2003/11/06 11:00:48
- Status: offline
Re:"Normalize" produces random results after using it a while
2012/04/29 16:31:56
(permalink)
If you "have to", normalize to a workable level then use envelopes. much easier , non destructive!
|
Guitarhacker
Max Output Level: 0 dBFS
- Total Posts : 24398
- Joined: 2007/12/07 12:51:18
- Location: NC
- Status: offline
Re:"Normalize" produces random results after using it a while
2012/04/29 20:11:15
(permalink)
You need to understand what normalization does. In a nut shell, it raises the level in a specific track to what ever maximum level of normalization you select. If you set it to 100% it will take the highest peak and amplify it to 100% of 0db. All other levels are amplified accordingly to keep the clip in perspective. If you use this on a complete track the track is fine. All levels are consistent. However, it appears from your OP that you are normalizing clips in a track NOT the entire track..... and that is the reason you are getting inconsistent results. It is not a bug or a baker problem.... it's how you are using the function. In any number of clips, the highest level will vary. for example lets take 2 clips side by side in the track. In the first one, the peak is lets say is -3db, and in the second clip the highest peak is -12db. If you do NOT select them both but instead opt to normalize them one at a time, normalize will only amplify the first clip a very small amount ..... from -3 to 0db is not much..... but the second clip is -12 to 0db, quite a large amplification. NOW.... if after doing the normalization, you play them both back..... the second clip will appear much louder than the first since the normalization to get it to 0db was a much larger amount, and that affects the entire clip making it sound louder. The solution is to select all the clips in a track and normalize them all together not one at a time. The other option is if for example you have a normalized track and discover that you need to punch in a mistake...... now the new clip is lower than the track, and normalizing it alone will NOT bring it to the same level as the surrounding material. The solution to this is relatively easy..... I do this all the time. Simply highlight that ONE clip. Now instead of guessing at the normalization level.... just select the GAIN...and go to the presets... I normally start with +2db... and apply it. Between looking at the wave of the clip and the surrounding clips.... and listening to the before, during and after of the punch in point ..... I can get a good idea if I'm good or if I need to hit 2 more db..... I repeat this until I can not tell that the new clip is at a different level than the surrounding material. I seem to be alone so far in this thread in using normalization. I only use it in tracks where the levels are low and need to come up and I can not get a better clean input signal. I also use it in my wave editor as the final step in finishing a project. I trim the start, trim the end, and normalize it often to 98% of 0db. No one has ever complained that they can tell I used normalization. It is simply another tool that is available and used properly with a good understanding of what it is and what it can do, will allow you to get that final level output to a decent level as long as everything else is in good order in the mix. And no.... using it doesn't put you into contention for the loudness wars. You need compression for that. Add/edit: If while working on a clip, you applied the gain or normalization and it's not right... you can undo it. It becomes destructive editing only when you have gone too far to back up with out undoing all the other changes in between OR... when you shut down the program. I'm not afraid to do destructive editing. I do it all the time. But I am sure I want to keep the changes first. I have rarely regretted making a change permanent. So, I'm not worried by making and saving destructive edits.
post edited by Guitarhacker - 2012/04/29 20:36:03
My website & music: www.herbhartley.com MC4/5/6/X1e.c, on a Custom DAW Focusrite Firewire Saffire Interface BMI/NSAI "Just as the blade chooses the warrior, so too, the song chooses the writer "
|
Lynn
Max Output Level: -14 dBFS
- Total Posts : 6117
- Joined: 2003/11/12 18:36:16
- Location: Kansas City, MO
- Status: offline
Re:"Normalize" produces random results after using it a while
2012/04/29 20:30:05
(permalink)
I agree with Guitarhacker 100 per cent. If you're going to use normalization, his method is the way to do it. Just be wary of big volume jumps. Most of the time, normalizing won't color the sound enough to hear, but it is possible! Some of the limiters that come with Sonar are up to the task of leveling the playing field, as well.
|
Cactus Music
Max Output Level: 0 dBFS
- Total Posts : 8424
- Joined: 2004/02/09 21:34:04
- Status: offline
Re:"Normalize" produces random results after using it a while
2012/04/29 20:45:05
(permalink)
100% what Guitar hacker said, People always misunderstand it and then you get people saying don't use it?? It's a tool and if your read the instructions it is a very useful tool. I don't like Sonars implementation of it. But I've used Wave Lab's Normalization on just about everything I record for the last 12 years with excellent results. The most important part of using the tool is to first know what your dealing with. Sonar does not have the "look for peak Level" so it's a crap shoot.
|
bitflipper
01100010 01101001 01110100 01100110 01101100 01101
- Total Posts : 26036
- Joined: 2006/09/17 11:23:23
- Location: Everett, WA USA
- Status: offline
Re:"Normalize" produces random results after using it a while
2012/04/29 21:08:16
(permalink)
There is nothing inherently wrong with doing destructive gain changes. I do it often, usually after recording a synth via S/PDIF where, because I have no control over the audio levels coming in, the recorded track is sometimes too low. (I use the Process->Gain method, which is functionally identical to Normalize, but without the guarantee of staying within legal limits.) From there, I use the Trim ("Gain" in X1) sliders and volume automation. Which is a long-winded way of saying I agree with everybody else in that normalizing is rarely needed. But that doesn't address the question of why you'd get different results every time you normalize. Here's one possible explanation: When you normalize to adjust the perceived volume, you have to take a guess as to the setting because you don't know in advance what peak value will yield the desired volume level. That's because normalization adjusts peak levels while perceived volume is based on average levels. We are relatively insensitive to peak level changes, so you will usually need to make drastic changes to peak levels before you hear a significant change in loudness. Consequently, you're going to sometimes end up with peaks hitting 0db after normalization. Any subsequent normalizations would have no effect, because SONAR's Normalize function does not allow you to exceed 0db. IOW, you attempt to raise the level but nothing happens. Could this be what you are experiencing?
 All else is in doubt, so this is the truth I cling to. My Stuff
|
Guitarhacker
Max Output Level: 0 dBFS
- Total Posts : 24398
- Joined: 2007/12/07 12:51:18
- Location: NC
- Status: offline
Re:"Normalize" produces random results after using it a while
2012/04/29 21:28:33
(permalink)
Dave (Bitflipper) is correct in saying that normalization is a crap shoot because you don't have any real idea of just how much the gain will be increased. It depends on the highest peak in the track or clip. While the part of the track you are looking at in the console view may seem low, there could be a spike further down the time line that will limit the gain applied by normalization. On a track with a relatively consistent and low overall level, the results can be quite dramatic yielding a big volume increase. On another track with the same low level and one spike up to -1 db.... the result will be a track that is almost unchanged even though the majority of the track is low.... that one spike is the measureing stick for normalization. On a track where normalization raises the levels significantly, there are a few options I consider. 1. use envelopes to lower the levels after normalization 2. set the normalization to a level less than 100% normalization. 3. undo the normalization and use gain in +2db increments until I get it where I want.
My website & music: www.herbhartley.com MC4/5/6/X1e.c, on a Custom DAW Focusrite Firewire Saffire Interface BMI/NSAI "Just as the blade chooses the warrior, so too, the song chooses the writer "
|
Cactus Music
Max Output Level: 0 dBFS
- Total Posts : 8424
- Joined: 2004/02/09 21:34:04
- Status: offline
Re:"Normalize" produces random results after using it a while
2012/04/29 22:10:22
(permalink)
Yes exactly, You first LOOK at the wave form or use a "Find Peak" tool and manually eliminate any rouge peaks. It take time to learn how to use Normalizing properly. It is not a magic fix for low volume. Like Guitar hacker is saying one tiny spike and you will be told the highest level in this track is 0 db. Even though it's obviously at a low volume. I just recorded 4 hours of live local Choir concert. There was also guests soloist, folk songs, Piano, Bass,drums everything. I recorded with 2 Shure Choir overheads and a front of stage large diaphragm mike, and a feed from the FOH. My first chore now will be to load each track ( tool copy) into Wave Lab and Edit out peaks and then Normalize. I also use the global RMS level analyzer and make notes so each track is about the same level when I'm done. Then I'll use Sonar to mix the 4 tracks with automation.
|
bitflipper
01100010 01101001 01110100 01100110 01101100 01101
- Total Posts : 26036
- Joined: 2006/09/17 11:23:23
- Location: Everett, WA USA
- Status: offline
Re:"Normalize" produces random results after using it a while
2012/04/29 22:54:02
(permalink)
...and manually eliminate any rouge peaks Yeh, you don't want any rouge peaks. Mauve and fuchsia are OK, though.  Sorry.
 All else is in doubt, so this is the truth I cling to. My Stuff
|
Cactus Music
Max Output Level: 0 dBFS
- Total Posts : 8424
- Joined: 2004/02/09 21:34:04
- Status: offline
Re:"Normalize" produces random results after using it a while
2012/04/30 00:37:51
(permalink)
Not my fualt, there s no spell checker on IE, and you can't use firefox so leave me alone, :) Besides, in wave lab the peaks are kinda purple... well after 4 hours of editing and a "Herb" helping out on the side lines. .
|
THambrecht
Max Output Level: -73 dBFS
- Total Posts : 867
- Joined: 2010/12/10 06:42:03
- Location: Germany
- Status: offline
Re:"Normalize" produces random results after using it a while
2012/04/30 03:22:26
(permalink)
This helps: Normalizing a lot of clips: Insert any effect to the effect-bin. Turn them ** OFF **. APPLY this effect to ALL clips. This command forces Sonar to make a wavefile for each clip. Now normalize the clips, and it works. background: ---- apply trimming does not work right --- Only the apply-effect-command forces SONAR to make single wavefiles for each clip. The appy-trimming-command does not NOT right.
We digitize tapes, vinyl, dat, md ... in broadcast and studio quality for publishers, public institutions and individuals.4 x Intel Quad-CPU, 4GHz Sonar Platinum (Windows 10 - 64Bit) and 14 computers for recording tapes, vinyl ... 4 x RME Fireface 800, 2 x Roland Octa Capture and 4 x Roland Quad Capture, Focusrite .... Studer A80, RP99, EMT948 ... (Germany) http://www.hambrecht.de
|
JazzSinger
Max Output Level: -73 dBFS
- Total Posts : 895
- Joined: 2004/07/06 16:30:59
- Status: offline
Re:"Normalize" produces random results after using it a while
2012/04/30 04:42:03
(permalink)
Guys, guys, I know what Normalization is. This is what is happening (after using the tool for a while): I click on a clip and normalize to, say, -3dB, but resultant normalized peak level is random, nowhere near -3dB. So I click on a few other clips, then return to the same clip, then normalize again without changing any settings, and NOW I get -3dB. And I have to do this for every clip. The Normalize tool is buggy. End of.
post edited by JazzSinger - 2012/04/30 05:50:53
|
Bristol_Jonesey
Max Output Level: 0 dBFS
- Total Posts : 16775
- Joined: 2007/10/08 15:41:17
- Location: Bristol, UK
- Status: offline
Re:"Normalize" produces random results after using it a while
2012/04/30 05:14:56
(permalink)
Don't forget you've got 18dB of gain available via the track trim/gain control.
CbB, Platinum, 64 bit throughoutCustom built i7 3930, 32Gb RAM, 2 x 1Tb Internal HDD, 1 x 1TB system SSD (Win 7), 1 x 500Gb system SSD (Win 10), 2 x 1Tb External HDD's, Dual boot Win 7 & Win 10 64 Bit, Saffire Pro 26, ISA One, Adam P11A,
|
JazzSinger
Max Output Level: -73 dBFS
- Total Posts : 895
- Joined: 2004/07/06 16:30:59
- Status: offline
Re:"Normalize" produces random results after using it a while
2012/04/30 05:53:22
(permalink)
Yes, but the Gain control has issues all of its own: 1. It is ignored if you export a track but is used if you export the entire mix, and 2. I set it to zero by double-clicking, but the actual gain did not change until I later turned it around and returned to zero manually. Took me an evening to figure out what was wrong. It was my realization that the Gain knob is buggy that led me to look for alternatives in the first place.
post edited by JazzSinger - 2012/04/30 06:02:55
|
Bristol_Jonesey
Max Output Level: 0 dBFS
- Total Posts : 16775
- Joined: 2007/10/08 15:41:17
- Location: Bristol, UK
- Status: offline
Re:"Normalize" produces random results after using it a while
2012/04/30 06:54:07
(permalink)
Another option - insert something like the Sonitus EQ in your FX bin - this one has it's own output level control, which I think again goes up to +18dB?
CbB, Platinum, 64 bit throughoutCustom built i7 3930, 32Gb RAM, 2 x 1Tb Internal HDD, 1 x 1TB system SSD (Win 7), 1 x 500Gb system SSD (Win 10), 2 x 1Tb External HDD's, Dual boot Win 7 & Win 10 64 Bit, Saffire Pro 26, ISA One, Adam P11A,
|
pwal
Max Output Level: -46 dBFS
- Total Posts : 2909
- Joined: 2004/08/24 07:15:57
- Status: offline
Re:"Normalize" produces random results after using it a while
2012/04/30 07:34:07
(permalink)
it seems like it's "forgetting" which clip's settings to use for the normalisation - this could be caused if the new gui isn't firing or handling an event that says "i'm the clip"... (not to hijack but i think a lot of the weirder new bugs are caused by the new gui not being "bolted on" properly yet 8-/)
|
JazzSinger
Max Output Level: -73 dBFS
- Total Posts : 895
- Joined: 2004/07/06 16:30:59
- Status: offline
Re:"Normalize" produces random results after using it a while
2012/04/30 07:35:23
(permalink)
What's really needed is something between a normalizer and a limiter. I seem to recall SoundForge or Wavelab had something called RMS normalize as one of its normalization settings. That normalized so it sounded the same to human ears.
post edited by JazzSinger - 2012/04/30 07:59:43
|
pwal
Max Output Level: -46 dBFS
- Total Posts : 2909
- Joined: 2004/08/24 07:15:57
- Status: offline
Re:"Normalize" produces random results after using it a while
2012/04/30 07:57:37
(permalink)
sf10 has a choice of peak or rms normalising, with fades and wet/dry mix - maybe use the batch conversion tool, if you prep all your clips first?
|
JazzSinger
Max Output Level: -73 dBFS
- Total Posts : 895
- Joined: 2004/07/06 16:30:59
- Status: offline
Re:"Normalize" produces random results after using it a while
2012/04/30 08:01:36
(permalink)
Yeah, I may go that way. Just more work, that's all.
|
bitflipper
01100010 01101001 01110100 01100110 01101100 01101
- Total Posts : 26036
- Joined: 2006/09/17 11:23:23
- Location: Everett, WA USA
- Status: offline
Re:"Normalize" produces random results after using it a while
2012/04/30 10:42:14
(permalink)
[The gain slider] is ignored if you export a track but is used if you export the entire mix Easy solution for that one: solo the track and export the "entire mix". I use the Trim/Gain control extensively but have not noticed the other problem, wherein double-clicking the Gain slider appears to return it to zero but doesn't really. I just tested it and was unable to duplicate that behavior. Maybe it's an X1 idiosyncrasy; I'm at 8.5. Meanwhile, I've been sitting here normalizing clips to various values and it's consistently performed exactly as expected. I wonder if maybe you've occasionally had more than one clip selected before normalizing. It's easy enough to do, and you wouldn't notice if the other selected clips/tracks were not visible. I know I've accidentally deleted tracks that way. I still think the problem is unnecessary, because I can't see any reason to normalize a clip more than once. Normalizing to mix seems like extra work for no benefit. What did people do before we started recording music on computers? They weren't normalizing, that's for sure.
 All else is in doubt, so this is the truth I cling to. My Stuff
|
Cactus Music
Max Output Level: 0 dBFS
- Total Posts : 8424
- Joined: 2004/02/09 21:34:04
- Status: offline
Re:"Normalize" produces random results after using it a while
2012/04/30 12:12:41
(permalink)
What did people do before we started recording music on computers? They weren't normalizing, that's for sure. ----------------------------------We turned the gain up on that tape return and watched our metering. Inserted a compressor of it had Violet peaks. ( Rouge )
|
pwal
Max Output Level: -46 dBFS
- Total Posts : 2909
- Joined: 2004/08/24 07:15:57
- Status: offline
Re:"Normalize" produces random results after using it a while
2012/04/30 12:59:30
(permalink)
wadr, it's not a technique question, it's regarding an issue with the normalise function behaving weirdly
|
DeeringAmps
Max Output Level: -49 dBFS
- Total Posts : 2614
- Joined: 2005/10/03 10:29:25
- Location: Seattle area
- Status: offline
Re:"Normalize" produces random results after using it a while
2012/04/30 13:09:54
(permalink)
I did duplicate the GAIN issue, but it seems "spotty". You know, INTERMITTENT, the toughest to document. I've been with Cake since CakePro 3.0, and so firmly BELIEVE its flawless, that I usually blow threads like this off. ASSuming that the OP is doing something wrong. BUT, I'm trying to "rescue" a couple of tracks from '73, working only with mono tracks and I'm NOT getting in the 2-track bounce what I "hear" during playback. Been using the Gain knob so that's part of it? AND Off topic here, but the default pan law "0Db sin/cos constant power" DOES NOT give me a 2-track mix that is the same as playback. But that's off topic, I'll post details in another thread... Tom
Tom Deering Tascam FW-1884 User Resources Page Firewire "Legacy" Tutorial, Service Manual, Schematic, and Service Bulletins Win10x64 StudioCat Pro Studio Coffee Lake 8086k 32gb RAM  RME UFX (Audio) Tascam FW-1884 (Control) in Win 10x64 Pro
|