Possibility to configure Kontrol hardware tempo faders

jacques

Ok so I will now put this here and hope that it get some attention, since I originally posted it here https://community.native-instruments.com/discussion/1412/can-we-get-a-switch-to-turn-off-tempo-fader-deadzones and I cannot understand why there isn't a ton of people having this issue. Maybe manual beatmatching is not a thing anymore? ;)

It comes down to this: The Kontrol S2 mk3 has a dead zone in the middle of the tempo faders which is very annoying and cannot be configured. After doing tests with relative mode I found out that this dead zone is indeed communicated from the hardware since the fader movement in the software always stopped when crossing the mid point of the hardware. I am using the term dead zone here but it's actually more like a "around the middle there is a sensitivity curve" kind of zone that is just not working well with manual beat matching.

It would be nice to be able to configure the hardware tempo faders so they are absolutely linear and don't have a dead zone, just like... well, any other tempo fader I have used the last decade, apart from those of maybe ancient turntables.

I don't know if this is also true for the S3 and S4 tempo faders but being able to configure the behavior of the faders in Traktor would be really welcome.

EDIT: Just to make this clear... It is not about a bug, it's not about the sensitivity of the faders in general, it is just about being able to configure that there is no sensitivity curve around the mid point of the tempo faders. I think even though the faders of the S2 are rather small, they are absolutely precise. I can beat match with the small faders in +-6% mode easily and very accurately. It's just that when being around the hardware fader mid point and I know that the match point is there, it's actually so inconvenient to beat match that I rather use sync in these scenarios. There are good reasons to use sync but this isn't one.

Kaiwan_NI

Thanks a lot for submitting this idea. Unfortunately it didn't receive enough votes over the allotted time. We're closing the post.

Note that our ideas section doesn't reflect the Traktor team's backlog. Even if this idea hasn't been brought up to the team at this time, that doesn't mean it'll never be implemented in the future.

For more info about how your feedback reaches NI, please have a look here.