Here's a very basic question - I'm almost embarrassed to ask, but I do
need to get this right. I'm considering a change to how I store
frequency data. Right now I'm storing the number directly as a float,
so 440.5 Hz is 440.5 in storage.
This is for pitch, so it's more important for me to favor precision in
the lower range. For a variety of reasons, it would also be more
convenient and interesting to use the range from 0. to 1.
Question One: Does changing the range change the *relative* precision?
In other words, am I better off with the [0. ... 22500.] range or the
[0. ... 1.] range if I want a minimum of audible floating point
inaccuracy? Is this even an issue, perceptually? Should I use [-1. ...
1.] with the assumption that MSP's floats are all signed anyway?
Question Two: Is there an optimum transformation / scaling to apply to
the frequency data in order to favor audible pitch correctness (ie
greater precision as pitch decreases)? Does that even make sense?
Thank for any feedback on this!