Goddard
John
Goddard
John
"This is probably a good place to ask this question. I did my first-ever sampling last weekend, and ended up using Audition to do the task. I recorded them 44.1KHz mono (drums), but Audition defaulted to a 32-bit float on saves so I just used that. Is that 32-bit buying anything at all, or just wasting space on me?"
For recording yes its wasting space. Keep in mind that your converters are incapable of recording anything above 24 bits. So the file that was created is 24 bits plus a lot of padding. This adds nothing useful to the recording at all.
Now for processing it a very different story. However, I am of the opinion that the file on disk doesn't need to be greater than 24 bits even after processing. I am sure I am alone in this view.
No, the 32-bit floating-point file data saved by Audition isn't padded, it's just being represented in floating-point format (and using all of those 32 bits for its data) rather than in the fixed-point/integer 24-bit format as was output by the ADC. If it were being saved as 32-bit integer data instead, then yes, it would include padding.
Perhaps Noel (if he's still around) would care to confirm whether/when Sonar converts to integer format for disk storage (as WAV files iirc).
Where is the audio that is filling those extra bits coming from? My understanding is that floating point will reduce rounding errors if the file has been processed and with a 32 bit FP audio engine used. Otherwise it will be exactly what the converter created.
Your understanding is incorrect/incomplete:
http://en.wikipedia.org/wiki/Single-precision_floating-point_format
Sorry I'm not following you. If the recorded data/audio is only 24 bits how can converting it into 32 bits add further data? It will not become audio with any more detail or precision. It is limited to the 24 bits that the A/D converter produced. If it is processed it is possible that the resulting audio will have greater precision due to an internal 32 bit FP audio engine but it will be inaudible.
It really should be similar to recording at 16 bits and then converting the 16 bit file to 24 bits. You gain nothing except a patted file with the original 16 and a bunch of zeros filling out the rest of the file. Its like having a container that you fill up. No interpolation occurs simply because the file is bigger.