In Reply to: RE: How hard should I strive to get maximum signal? posted by tom.dennehy on March 26, 2012 at 04:34:49:
Thanks for the example. This is just one example where audio software may "silently" trash the quality of one's recording. This problem is not unique to Audacity, there were similar problems with earlier versions of Soundforge.
There is no guarantee that any editing feature will not mangle the sound quality. Even more subtle than reducing 24 bits down to 16 are effects like converting to/from 24 bit integer and floating point. Here the conversion from floating point back to integer may add dither noise at an "inaudible" level of -135 dBfs. Unfortunately, under some conditions and on some systems this change of +1 or -1 in individual 24 bit samples may result in an audible difference. One has to trust one's tools to be an artisan, but the rule should be "trust but verify". Verification includes technical measurements (e.g. null tests, spectrum analysis, etc.) and careful listening tests, not casual 30 second A - B comparisons.
Other fun exercises one can play is to use the editing features to deliberately trash a recording in a subtle way and see how much trashing it takes before you hear it. Such things include failure to add dither, moderate amounts of clipping, suboptimal filtering for sample rate conversions, etc.
Tony Lauck
"Diversity is the law of nature; no two entities in this universe are uniform." - P.R. Sarkar
This post is made possible by the generous support of people like you and our sponsors:
Follow Ups
- Trust but Verify - Tony Lauck 08:03:16 03/26/12 (0)