There are real differences between 16 bit and 24 bit files, just as there are real differences between uncompressed and mp3. As with the differences between wav and mp3, 16 bit vs 24 bit is often difficult to identify by listening.Test signals are one thing, but has anyone found any 24 bit music recording that can be successfully identified via ABX testing against a properly resample to 16 bit version of same?
Do you happen to have ABX logs available?
I can submit samples dithered with POW-r, UV22, Waves L1, L2, L3 and perhaps others if desirable. The two former algorithms retain 19 to 20 bits of resolution according to Bob Katz.
[...] but I would appreciate it if somebody would try apply Sebastian's noise shaped dither from the end of this thread [...]
>java -jar requant.jar SprightlyHandelclip.wav SprightlyHandelclip_b16_d17_slameath48.wav 16 -d1.7 -firstname.lastname@example.org
As I am playing with SebastianG's filter in lossyWAV and this thread pertains to bit-reduction, I tried SprightlyHandel with lossyWAV........... and it crashed with an FMT chunk error. Apparently, the posted WAV has 2 bytes appended to the FMT chunk. So, I amended lossyWAV to take this into account and successfully processed the WAV file (lossyWAV -3 -shaping 1.000, average bits removed: 6.97) and then encoded it with FLAC -5 - the result is attached.
The more I look into dithering, the easier I find it to accept that the process if done optimally will not lead to audible distortion.
Quote from: MLXXX on 22 March, 2008, 10:30:16 AMThe more I look into dithering, the easier I find it to accept that the process if done optimally will not lead to audible distortion.The process if done optimally will not lead to ANY distortion, audible or otherwise. It will lead to an increase in the noise floor - but I think it's important, if pedantic, to make a distinction between THD and THD+N.