More types of FloatModels?

[regulus79]

We have FloatModels for general purpose floats, and TempoSyncKnobModels for models which deal with time. But what if we added more? What about a type of FloatModel dedicated for volume, or one for frequency? That could make it easier to define unique behaviors for those knobs.

For example, I remember someone requesting a feature where a frequency knob could be snapped to the nearest semitone. That would be easier to implement if all frequency models had their own class.

Or for volume, I know we already have something like that where you can "set" whether a float model is for volume or not, but I mean, I feel like it should really be it's own class.

Would this sort of change be useful? Are there any others which might be helpful to have?