I have an issue. When I do automation with my nanoKontrol, Ardour seem to, some time, lost my fader ; and to recover it, I have to pass at the same spot as Ardour.
Let me explain.
If I want to do a FadeOut to 0dBfs to -40dBfs, some time the Ardour’s fader stop at -20 or -34 (no matter for the value, is an exemple), but I continue my FadeOut with my nanoKontrol ; the value between my physical fader and the Ardour fader are no longer coherents.
So, to continue my automation, I have to move my physical fader to -20 (or the value where the Ardour fader stop) and ardour find again my nanoKontrol and I can continue my automation.
I have this issue on my Linux. And prepare a kind of TV set with one Windows 11, and this problem continue.
This is normal for non-motorized control surfaces.
You can tweak things in Preferences > Control Surfaces > Generic MIDI > Edit
If motorized is disabled, Ardour ignores all control events from the hardware until the control-surface knob/fader position is close to the internal parameter-value. The “smoothing” control allows to configure this, a small value prevents discontinuities (the parameter cannot jump large distances when you move the knob). The larger the value, the easier it is to rapidly change the control.
I have one of these devices and have always experienced this. Never used it in Windows to compare, hehheh. It makes sense after reading the explanation, and should be the default behaviour. I’ll look into tweaking the settings as suggested.