zmix wrote on Tue, 17 June 2008 01:20 |
Can you please provide some more information or possibly a link to qualifty this claim?
|
Here is some more links for you...
http://www.gearslutz.com/board/music-computers/154664-wavebu rner-effing-up-my-tracks.html
http://www.gearslutz.com/board/mastering-forum/154669-wavebu rner-problems.html
http://www.gearslutz.com/board/mastering-forum/195415-more-w aveburner-tests.html
Be patient & makes sure you read through the threads & do the tests yourself before deciding that they are invalid.
Quote: |
Gearslutz? Are you pulling my leg?
The first relevant quote I found in that thread was this:
Quote: | Even 1.5.2 will only burn bit accurate discs from 16 bit source files with no processing. __________________
|
Obviously this was posted by someone who does not understand the following basic facts:
1: You cannot burn a red book audio CD at a greater bit depth than 16, so any file with a greater bit depth than 16 bits will be truncated and dithered.
This process will not allow the original higher bit depth file to be extracted from the stored 16 bit file.
So, yes, NOT bit accurate, but hardly unique to Waveburner.
2: Any signal processing, even a level change will alter the original data.... Again,
EDIT: Further idiocy in that *gearslutz* thread has resulted in the unsubstanciated claim that Waveburner truncates to 15 bits... If you truncate and - dither - a 24 bit file you will NOT get a null when compared to a 24 bit file or even a 24 bit file truncated to 16 bits.
Dither needs to toggle the LSB to be effective, therefor only the upper 15 bits will null against the original 24 bit file or the truncated to 16 bit file.
Verdict?
NOT A BUG
|
Respectfully you don't know what you're talking about. Please try this test on your copy of Waveburner (any OSX version has this same problem even the latest version 1.5.2). This bug does not exist in the OS9 version of WaveBurner so it's only in the OSX version, the following test validates all these claims...
1. Take a 16bit file convert it to 24bits with any application other than WaveBurner. Yes this will add an extra 8bits of padded zeros, stay with me...
2. Add this newly created 24bit file into WaveBurner &
without doing any fades, volume changes, processing or adding any dither options (dither turned off in WB prefs) bounce this region to hard disk & select 16bit as the word length.
3. Take this newly created 16bit bounce & line it up with the original 16bit file in the DAW of your choice (Pro Tools, Logic etc.) make sure they are lined up to sync accurately & flip the phase on one of the files & listen to the result (check the peak meters to see the results as well).
In all my tests (these were extensive!)
Any 24bit to 16bit processing, bouncing or burning in WaveBurner (without dither!) resulted in a cancellation of only -90.3 against the original 16bit file. The same tests done with other applications such as WaveEditor, SampleManager & Pro Tools resulted in complete cancellation down to infinity.
Ok so it may not be dropping a bit but, the results are conclusive that WaveBurner is not bit for bit accurate when handling 24bit files & converting them to 16bit.
Do the tests as we all have done & you will see for yourself.
Matt