Taperssection.com

Gear / Technical Help => Post-Processing, Computer / Streaming / Internet Devices & Related Activity => Topic started by: it-goes-to-eleven on August 07, 2005, 10:15:11 AM

Title: Wavelab problems processing 24/96 to 16/44
Post by: it-goes-to-eleven on August 07, 2005, 10:15:11 AM

Yesterday I tried to process my first 722 show from 24/96.  I did a batch conversion in Wavelab to 24/44.1.  Then I did a UV22HR dither on those files (batch mode) to 24/44.1.  It was only later that I discovered that the levels had been raised significantly and a bunch of clipping introduced.

Any idea where I went wrong?

I'm just about to pop over to the win box to see whether it was the conversion or the dither that ganked the levels.

Title: Re: Wavelab problems processing 24/96 to 16/44
Post by: F.O.Bean on August 07, 2005, 10:39:46 AM

resample THEN save and then try to dither to closely see what was going on, it there3 is clipping introduced in the first saved files of the resampling, then thats the culprit

weird tho?

maybe you had some effects set that you didnt notice and they took effect when you hit render ???

Title: Re: Wavelab problems processing 24/96 to 16/44
Post by: dklein on August 07, 2005, 07:59:34 PM

Sounds like there may have been some bad truncation in there.  You'd get that effect if you tossed out the 8 most significant bits from a 24 bit signal.  All of a sudden everything would be '8 bits louder' and any signal over the 16th bit on the original 24 bit would hit 0 and clip.

good truncation (if that's possible) involves tossing the 8 least significant bits.  Volume level stays the same but the low level detail is lost.

Any chance you have your temp files set to 16 bit or your saved file from the batch conversion was at 16 bits?

-edit- just remembered the bit meter built into wavelab - turn that baby on and play your 24/44.1 file - does it ever go to 24?