So I've been thinking a bit about bits, trying to understand what more bits do.
I compare it to taking pictures. It's similar, in that when I take a picture, I am taking a "slice" out of the continuous flow of reality. If I make my slice 1/100 of a second, then I am capturing .01 of a second. Now, if my camera can take 5 pictures a second, I have captured 5% of the second, losing 95%. But that's ok, and most of the time, if I had a choice, I would prefer even shorter slices of reality, such as 1/1000 of a second or 1/2000, since that would freeze motion better.
Now, for bits. If I have a CD that is encoded at 44,100 bits per second, that means it is taking 44,100 samples per second. How "small" is each slice? I know in the case of a camera, the film or sensor is actually exposed to light for that whole 1/100 of a second. But in the case of the CD, how small are each of those 44,100 samples? I would think that they are much, much smaller. HOW MUCH OF THE SECOND HAS BEEN CAPTURED by the 44,100 sampling mechanism?
I would think very little. I mean, one can capture at double that, and at 192,000 without breaking a sweat nowdays. I guess one can even capture at 1 million now, or soon. Does that not mean that our 44,100 has captured very, very little, and we are just guessing (with greater or lesser accuracy, depending on the complexity of the composite waveform at each frequency) at the remainder of the wave?
And then, on top of that piece of miniscule information capture and much guessing, we now encode at 320? We have lost even more.
Does LAME understand that it is encoding off of a CD, most of the time? Are its algorithms different for that situation than when it is encoding, say, off an analog input? If not, aren't there artifacts caused by the interaction between the choppy 44,100 and the subsequent (even at 320) compression?
