Taperssection.com
Gear / Technical Help => Post-Processing, Computer / Streaming / Internet Devices & Related Activity => Topic started by: Scooter on September 13, 2004, 12:26:00 PM
-
I remember some time back, an issue w/ Wavelab and resampling/dithering came up. When you resample/dither with plugins in Wavelab the specs in the lower right hand corner (and the specs after you save the file and look at it in windows for that matter) would reflect the chaged sample rate, but not the changed bit rate. Well I finally got an answer as to why...
"Hi Scott,
a plugin can change the sample rate of a file, but it cannot change the bit depth. It will truncate the last bits by filling these with zeros, but the they're not cut from the file.
This can only be done by WaveLab, for example using the *save as* dialog. Another (time-saving) option would be creating a *specific file* from the render dialog, there you can specify the desired bit depth."
I still think it's annoying >:(, but at least I found out why it's happening. Just thought peeps would want to know about it.
-
This has been bothering me for quite awhile now with WL5's uv22hr dither plugin. With WL4, after you use the dither plugin, the specs change to "16-bit", but with WL5 it remains as "24-bit". I just figured my apogee plugin wasn't working in WL5 and went back to using WL4 for resample/dither. How can we verify the file is a "padded" 16bit file? Use Wave Lab's "bit meter"?
-
How can we verify the file is a "padded" 16bit file? Use Wave Lab's "bit meter"?
yeah, or you can just highlight a section, go analysis, global analysis and on the extra tab, you'll find something called apparent bit resolution. Run the analysis and see what you get. CEP users can do the same analysis - it shows up at the bottom of the summary as actual bit depth
Once you're down to 16 bit actual (in a 24 bit word), you can then truncate down to 16. Personally, with wavelab I've always done it in one step. When you click render, under 'result', select 'create new file, check the box that says 'create specific file', name the file and set the box below to wav 16 bit. Done.
-
Once you're down to 16 bit actual (in a 24 bit word), you can then truncate down to 16. Personally, with wavelab I've always done it in one step. When you click render, under 'result', select 'create new file, check the box that says 'create specific file', name the file and set the box below to wav 16 bit. Done.
I did that, the resulting file still says "24bit" in the description. I even double (and triple) checked that I had that new file set to 16. I'll have to try again, then do the analysis. Right now my computer is dead, so it will have to wait a few days.