Fader Response Tuning — How Customer Feedback Shaped the Firmware
Share
Fast fader moves felt like they were lagging behind. The first answer was a custom build for one customer. The second was a setting everyone could use.
Faders and knobs on ParksTool controllers are read several times and averaged. That kills the jitter, which is what you want for slow, precise moves. But the more readings go into the average, the longer the value takes to catch up with your hand.
A customer using one of our fader controllers live pointed this out. Push a fader quickly and the signal felt like it was chasing the fader rather than tracking it.
The first response was a firmware build with less averaging, sent to them directly. The second was turning that into a setting — where to sit between smooth and fast is the player's call, not ours.
Where to change it
Web Configuration Tool, under Global Variables: Potentiometers/Faders smooth filter level. It ships at 9, the smoothest setting. Lower it for speed, raise it for smoothness.
The firmware already does some of this for you
Since firmware 9.7.8, ordinary 7-bit CC is averaged less automatically. One step of the sensor barely moves a 7-bit value, so heavy averaging there only added lag without buying anything.
14-bit CC, NRPN and Pitch Bend use the level exactly as you set it. They need it — one sensor step moves a 14-bit value by 16, so without averaging an untouched knob drifts and sends on its own.
So this setting is mostly felt in the high-resolution modes. If you are running a 9F18K1X — nine faders — in 14-bit and fast moves feel behind, this is the number to lower.
The trade-off
Less averaging means faster, tighter tracking, but more exposure to noise. More averaging means a smoother signal, but a slight lag on rapid movement. Slow mix automation and live performance do not want the same thing.