Cutoffs are modeled as integer sliders and convert to frequencies with formulae like 440 * 2 ^ ( n / 12 ) implying n=0 is A4 -> 440 hz.
So when we show frequencies in the filter cutoff tooltips we could show the nearest note. So you would see something like
"281.2hz (~C#4)"
and then can tune your filters on frequency or on note.
Low priority obviously but would have answered a question that @esaruoho asked me on slack.
Oooh I just noticed unit conversion.h already has get_notename
This one seems fairly straightforward. If I were to attempt a change anything to watch out for? Iām away from the code so canāt check right now.
Is the work here essentially taking current frequency from the slider, doing unit conversion on it and then concatenating the strings in the slider ādragsā label display?
Thatās correct and the formatting is done in thebparamrter for ct-frequency. Thereās a pitch to note function too somewhere
Note if we make this change it will now echo into surge-rack also; so need to be a teensy bit careful
Could it be possible to make it so that the spacing is constant when changing frequency? Right now whether there is a "#" symbol in front of a note or not makes the whole frequency's horizontal position jittery when changing the cutoff value and it makes it hard to read:

Easy
Oh darn it. Not so easy. Since we don't use a monospace font the # kerns wider than ' ' so it still bounces even when I put a space in. Will ponder.
My rough plan is to have the tool top contain a hard tab (\t) and have the infowindow widget do something smart with that. Or maybe special case the () to put a constant space around them. Something gross and hacky like that in the UI paint method basically is the only way to get it to align properly.
In the end I did the right thing rather than a gross hack. Any parameter can now advertise an alternate text for itself which isn't in the DAW string but is displayed in the info window. I put the pitch and the wavetable position there. Here's some gifs.

