@Texxiliator I think this is due to the plugin making incorrect use of the logarithmic flag.

See also #293.

Logarithmic is perfectly OK here. All these intervals are one octave and sound the same musically:

• 100 - 200 Hz
• 1000 - 2000 Hz
• 10000 - 20000 Hz

That doesn't mean someone might need more precise control in the upper part of the range, but I believe that'd be less common.

Imo the situation often with lmms dials, are that nothing or all comes 'out' within a very short span. The issue here, is that f.i. a filter pass can be quite difficult to automate. perhaps a 1.2.x could introduce something like an 'expander' in dials context menu, making the 'functional' span fit better inside the full span of the dial.

Well, there are "Set linear"/"Set logarithmic" in context menus. If you don't like log scale, you may set that to linear.

perhaps a 1.2.x could introduce something like an 'expander' in dials context menu

<off-topic>
You might know, but 1.2 is on a feature freeze. New features are targeted to master branch.
If we do something known as "rolling release", however, you may use new features before 1.3 rc.
</off-topic>

Logarithmic response is what I'd expect to find on a filter cutoff control. In the example given has the correct control in my opinion.

PS. The resonance control on the filter above seem to be inverted.

Can this one to be closed? I can't see a bug here.

Not sure if this was what was meant originally, but whilst the scale on the dial is logarithmic, as makes sense for frequency, the mouse control isn't. Both the scroll wheel and dragging on the dial change the value by the same absolute amount no matter where the dial currently is, with the effect that it moves a lot faster for lower values as the logarithm increases more quickly there.

OK. We can look a bit closer at this. Reopening.