Sample Rates - help on choosing the appropriate sample rate to work with
Bit depth defines the number of bits used to carry the data in each sample of audio.
The bit depth chosen for recording limits the dynamic range of the recording. (Other factors in the audio chain may also limit this, so more bits often will not produce a better recording.)
- CD audio (.cda) uses 16 bits for good dynamic range and very low noise
- Cassettes and players vary, but are in the region of 8 bit resolution, often less.
Effects on file size and CPU use
Bit depth (sometimes called also resolution) affects file size. All other things being equal, a 32 bit file is twice the size of a 16 bit file, and an 8 bit file half the size of a 16 bit one.
Bit resolution also affects CPU use. Recording a 32 bit stream takes a lot more work than recording 16 bits.
How Many Bits To Use?
If there will be no adjustment of gain after recording and no effects applied, the recording bit depth can be the same or 1 bit more than the audio source bit depth without losing quality.
8 bit resolution is good for most recording of medium and low quality sources, such as:
- Medium quality:
- FM radio
- Low quality:
- AM radio
- 8 track
- Telephone audio
- Reel to reel at 3.75ips or slower
- Pocket recorders at live events
If medium quality sources are to be manipulated before saving the recording, it may be preferable to record in 16 bit to avoid any possible quality loss during application of effects. This does not apply to simple editing, and does not apply to low quality sources, whose resolution is below 8 bit.
Audacity 1.2 does not support 8 bit recording, 16 bit is the nearest option. It is possible to export projects in an 8 bit format, though Audacity defaults to exporting as 16 bit.
16 bit matches audio CDs, and is thus suited where the better dynamic range and S/N ratio of CD quality audio is required. 16 bit is a good general purpose high quality setting. 16 bit recording is suitable for vinyl records.
24 bit recording may be used for signals that will be manipulated but still need to maintain the full 16 bit quality of CD audio. 24 bit is good for mastering. If you're merely listening to thousands of pounds of expertly chosen high end audio kit, and not doing large amounts of editing, there may be no real reason to exceed 24 bit depth.
32 bit recording "might" be argued as taking things to extremes. Although 32 bit recording can in theory have better technical specs than less bits, it is not often such great bit depth is needed. General purpose recording does not need 32 bit depth for the same reason clothing sizes do not come in increments of 1/1000th of an inch.
Finding audio sources capable of providing signals with better dynamic range than than 24 bit resolution is a demanding task. A 32 bit data stream records 65,000 times the dynamic range of 16 bit CD audio. In real world applications, a lot of those bits will be normally recording nothing but very low level background noise. Also bear in mind that in many cases you will exporting to a 16 bit format (there are not many computer media players that support playing 32 bit files, and if you are burning to a standard audio CD, that format is by definition 16 bit).
But if you want the highest standards (for example, operate a recording studio), expect to do a large amount of manipulation of the data before export, and have audio source equipment with an extremely low noise floor, 32 bit recording (which is the default setting in Audacity) will give the best possible quality and avoid the bit depth having any effect on the sound even after heavy manipulation of the audio.
Much of the reason for this is that Audacity uses "float" format for 32 bit recording instead of fixed integer format. Normalised floating point values are quicker and easier to process on computers than fixed integer values and allow greater dynamic range to be retained even after editing. This is because intermediate signals during audio processing can have very variable values. If they all get truncated to a fixed integer format, you can't boost them back up to full scale without losing resolution (i.e. without the data becoming less representative of the original than it was before). With floating point, rounding errors during intermediate processing are negligible.
The (theoretically audible) advantage of this is that 32-bit floating point format has no noise floor. For example, with fixed integer data, applying a compressor effect to lower the peaks by 9 dB and separately amplifying back up would cost 9dB (or more than 2 bits) of signal to noise ratio (SNR). If done with floating point data, the SNR of the peaks remains as good as before (except that the quiet passages are 9dB louder and so 9dB noisier due to the noise they had in the first place).
The advantage of using 32 bit float to work with holds even if you have to export to a 16 bit format. Using Dither on the will improve the sound quality of the exported file so there are only minimal (probably non-audible) effects of downsampling from 32 bit to 16 bit.