mark4man
MoonMix Studios
kinda wondering...
what happens when one dithers a (legal) 32-Bit FP file all the way down to 16-Bit w/ their favorite dither box ??
reason I ask is...I'd been used to (like everyone else, I suppose) bouncing out of the DAW (SONAR) at 32-Bit FP...then brick walling to legal in the mastering rig (WaveLab) while rendering to 24-Bit at the same time...then, dithering (UV22HR) & rendering to 16-Bit ftom 24.
[i had been doing this 'cause I assumed (& had heard) that A) the quantization error from 32 > 24 is miniscule & well below the audible range & B) it's a legal file after limiting anyway so I may as well render to 24...why waste bits.]
I did one today whereby I kept the file size/format at 32-Bit FP during the brick wall phase...(so that it was also 32-Bit FP after limiting)...& then dithered all the way down to 16 from 32 as the final stage. It sounded audibly way better (in comparing both methods) to the old method (24 > 16).
most notable was a more accurate reproduction of transients (snare, cymbal crashes, et al.) [i had used elephant 2 on clip for the limiting phase].
guess I'll keep this new (new to me, that is) method...but I'm wondering what's goin on technically w/ it ?
thanks,
mark4man
MoonMix Studios
ADK Pro Audio Core 2 | Intel DP35DP MoBo/Chipset | Intel Q6600 Quad Core CPU | 4 GB SuperTalent DDR2-800 CL5 RAM | Seagate 160 GB SATA II Primary HD | Western Digital 320 GB SATA II Audio HD | Lynx Aurora8 ~ AES16 | Universal Audio UAD-1 | SONAR PE 7.0.2 | Cubase LE | WaveLab 5.0.1b | NI Komplete5
what happens when one dithers a (legal) 32-Bit FP file all the way down to 16-Bit w/ their favorite dither box ??
reason I ask is...I'd been used to (like everyone else, I suppose) bouncing out of the DAW (SONAR) at 32-Bit FP...then brick walling to legal in the mastering rig (WaveLab) while rendering to 24-Bit at the same time...then, dithering (UV22HR) & rendering to 16-Bit ftom 24.
[i had been doing this 'cause I assumed (& had heard) that A) the quantization error from 32 > 24 is miniscule & well below the audible range & B) it's a legal file after limiting anyway so I may as well render to 24...why waste bits.]
I did one today whereby I kept the file size/format at 32-Bit FP during the brick wall phase...(so that it was also 32-Bit FP after limiting)...& then dithered all the way down to 16 from 32 as the final stage. It sounded audibly way better (in comparing both methods) to the old method (24 > 16).
most notable was a more accurate reproduction of transients (snare, cymbal crashes, et al.) [i had used elephant 2 on clip for the limiting phase].
guess I'll keep this new (new to me, that is) method...but I'm wondering what's goin on technically w/ it ?
thanks,
mark4man
MoonMix Studios
ADK Pro Audio Core 2 | Intel DP35DP MoBo/Chipset | Intel Q6600 Quad Core CPU | 4 GB SuperTalent DDR2-800 CL5 RAM | Seagate 160 GB SATA II Primary HD | Western Digital 320 GB SATA II Audio HD | Lynx Aurora8 ~ AES16 | Universal Audio UAD-1 | SONAR PE 7.0.2 | Cubase LE | WaveLab 5.0.1b | NI Komplete5