WaveLab Montage Level Changes - Gearslutz.com

Gearslutz.com

All Advertisers
Go Back   Gearslutz.com > The Forums > Mastering forum


WaveLab Montage Level Changes

New Reply New Reply Thread Tools Search this Thread
Old 20th June 2009   #1
Gear maniac
 
Djembe's Avatar
 
Joined: Jun 2006
Location: Sydney Australia
Posts: 209

Thread Starter
WaveLab Montage Level Changes

When compiling a master to burn from a WaveLab Montage, any changes to a track's overall level, result in it being converted back to 32bit.
Does this mean that dithering has to be done AFTER compiling the montage, or is there a way of changeing relative levels without changing the bit depth?
Djembe is offline   Reply With Quote
Old 20th June 2009   #2
Gear maniac
 
nine99nine's Avatar
 
Joined: Jan 2007
Location: Cleveland, OH
Posts: 252

Send a message via AIM to nine99nine
Yes, any processing whether you change volume, create a fade, or eq/compress/limit will increase the wordlength of the file. Dithering should always be the last step in your process as your montage is burned into a CD or Rendered into an image.

If you don't believe me, then beleive Bob Katz! Straight from his website www.Digido.com:
"To be very exact, all digital gain reductions (and most other non-trivial DSP operations) require a certain amount of dither if the signal is to be truncated to a shorter wordlength (there is only one correct minimum amount of dither). If the signal is going to be transmitted or broadcast at its original wordlength, then redithering will not be necessary. For example, I start with a 20 bit recording, and I drop the gain by 4.5 dB. This becomes a long word (48 bits or more) within the DSP (for more information on this, see the dither article). Internally, in the processor, this long word should be dithered up to 24 bits. Then you receive it at 24 bits. If you can use or transmit these 24 bits, then so much the better. Otherwise, when you reduce the word to 16 for storage or transmission, you will have to dither."
__________________
-"mr. junior mastering engineer!"
nine99nine is offline   Reply With Quote
Old 20th June 2009   #3
Gear maniac
 
Djembe's Avatar
 
Joined: Jun 2006
Location: Sydney Australia
Posts: 209

Thread Starter
Thank you for your reply.

I normally do my limiting and dithering in one step with an L2 plug-in.
If I am compiling a whole album though, I should do the processing and limiting of the individual tracks first, save them, then compile them into a montage, apply level changes, THEN dither the whole montage before burning.
Is this correct?
Djembe is offline   Reply With Quote
Old 20th June 2009   #4
Lives for gear
 
24-96 Mastering's Avatar
 
Joined: May 2008
Location: Karlsruhe, Germany
Posts: 2,747

Verified Member
Quote:
Originally Posted by Djembe View Post
Thank you for your reply.

I normally do my limiting and dithering in one step with an L2 plug-in.
If I am compiling a whole album though, I should do the processing and limiting of the individual tracks first, save them, then compile them into a montage, apply level changes, THEN dither the whole montage before burning.
Is this correct?
Why make it so complicated? Just assemble your montage with the unlimited audio (pre L2), then apply limiter + dithering via the master section, on load out.

The only reason to apply limiting before level adjustment would be if you _wanted_ to intentionally limit more than necessary for level, essentially having different out ceilings for different tracks... i.e. if heavier brickwall limiting than necessary is part of the sound aesthetic of a song. That happens, but it's surprisingly rare here. And even that you can facilitate (as well as using different limiter plugins) by loading different instances of your limiting plugin into different montage tracks.

Anyway, having the unlimited audio in the assembly montage gives you another advantage: If the client calls and says they want the master a touch louder (or a touch lower in level), your session recall takes roughly 1 minute.
__________________
.
Robin Schmidt @ 24-96 Mastering
www.24-96.comfacebook
24-96 Mastering is offline   Reply With Quote
Old 21st June 2009   #5
Gear maniac
 
Djembe's Avatar
 
Joined: Jun 2006
Location: Sydney Australia
Posts: 209

Thread Starter
Excuse my ignorance here, but is that the way it's normally done?
That is, setting the limiter levels for the whole album in one go.
I have always done it track by track.
For example a track that has only occasional peaks may need more limiting than one that is constant.
Also if a soft acoustic track's level needs to be lowered quite a bit and then you are applying your global limiting value, it may not have any limiting at all.
Djembe is offline   Reply With Quote
Old 21st June 2009   #6
Lives for gear
 
24-96 Mastering's Avatar
 
Joined: May 2008
Location: Karlsruhe, Germany
Posts: 2,747

Verified Member
Quote:
Originally Posted by Djembe View Post
Excuse my ignorance here, but is that the way it's normally done?
That is, setting the limiter levels for the whole album in one go.
I have always done it track by track.
Well, I run the limiting while making sound decisions track by track, but take it off before committing each track (i.e. running through analog or rendering), so that I can have the actual destructive process rendered separately (in the assembly EDL via master section, track FX or even clip FX). For one thing, that means that I never introduce more damage than is actually needed on a given song, for another thing, it means that revisions are significantly faster, as many changes then don't require recalling / rerunning the original track from scratch.

Some do it like this, some do it differently. There isn't really only one way of doing it.

Quote:
For example a track that has only occasional peaks may need more limiting than one that is constant.
I think you're misunderstanding.

All that you're doing, when levelling post the limiting is essentially changing your ceiling / max output of the limiter. If you level a track down after having limited it (any track, whether it only has occasional peaks or not), it just means that you *could have* used less limiting.
If that unnecessary amount of limiting is part of the intentional sound, then great. If not, you have unintentionally wasted headroom, negatively affecting sound quality because you made a wrong guess about the target track level.

I.e. if you're limiting before levelling (that is assuming you're going to do some levelling), you're NOT making decisions based on how much limiting each track needs, but on how much you're thinking it's going to need.

Quote:
Also if a soft acoustic track's level needs to be lowered quite a bit and then you are applying your global limiting value, it may not have any limiting at all.
Indeed. Isn't it great?

And again, you can, of course, have separate limting values (or even different methods of generating loudness not global, but set per track, if you do want different processing for different tracks.
24-96 Mastering is offline   Reply With Quote
New Reply New Reply Submit Thread to Facebook Facebook  Submit Thread to Twitter Twitter  Submit Thread to LinkedIn LinkedIn 



Thread Tools Search this Thread
Search this Thread:

Advanced Search

Similar Threads
Thread Thread starter Forum Replies Last Post
Standard Audio - Level-Or (Level-Loc based Comp for 500 Series) imacgreg Product Alerts older than 2 months 91 22nd August 2010 04:08 AM
wavelab level spektor Music computers 0 11th January 2009 09:15 AM
Audio CD montage software! Ciozzi Low End Theory 1 12th May 2008 10:56 AM
Clarification on what travels best on long cable lines, line level or mic level. esumsea Remote Possibilities in Acoustic Music & Location Recording 5 16th February 2007 08:58 PM
WaveLab montage question Slogun Music computers 4 13th February 2006 05:29 PM


All times are GMT +1. The time now is 10:08 AM.

Home - Search Forum - Contact Us - Terms Of Use - Advertise on Gearslutz - All Advertisers - Archive - Top
 
 
Powered by vBulletin®
Gearslutz.com LTD - UK Company Number 7597610.
Registered Office - 35 Ballards Lane, London, N3 1XW.
Hosted by Nimbus Hosting.

SEO by vBSEO ©2010, Crawlability, Inc.