|
| quote: | Originally posted by kitphillips
I see... So its OK to have 24 bit as long as its not floating point, because floating point needs to be a power of 2 because of the design of the processor? |
from my understanding, it needs to be a multiple of the CPUs word length, otherwise it is just a waste. the word length is the amount of bits that can be moved in one chunk. eg. one 32bit float is two words... a 24bit float would be 1.5 words. 4 bits would be wasted, so there's no reason to do this; 32bits would have the same overhead, but obviously offers more precision.
| quote: | Originally posted by kitphillips
Why don't they use 16 bit floating point? And what benefit does floating point have in audio terms? |
in a fixed point number, the decimal position is fixed. in a floating point number, the decimal position can be anywhere. the benefit of floating point numbers is that they can express a far greater range of numbers, as the decimal place shifts. the benefit of this to audio is that each sample can have a greater range of values. therefore, it is more accurate than using a fixed point number. the dynamic range of 24bit fixed is something like ~130db, whereas 32bit float is 150db+.
in order to allow the decimal point to float, we have to use some bits to store where it is. for example, a 32bit float number uses 1 bit for the sign, 8 bits for the decimal position and 23 bits for the actual digits themselves. i assume the reason that 16bit float isn't used is because the overhead of storing the decimal position and the extra cpu load of working with floating numbers outweighs the benefit, over a more simple fixed number.
|