Kontrol S2MK3, hotcue pads order

kourampies

After using the S4 for more than a decade, It's extremely annoying for me to have the hotcue order switched compared to the older models.

Is there any way to reverse this from within Traktor (or perhaps the Controller Editor) without making a custom map? (consider this a feature request if the answer is no)

If there is no easy solution, does anyone know of a map ready to use? I haven't done mappings in years, mapping the inputs is extremely easy, but the outputs, with modifiers, brightness etc are a pain.

Sûlherokhh

You could edit the qml files.

These are the sections that would need to be changed: Exchange

'%surface%.pads.1'

with

'%surface%.pads.5',

2 with 6, 3 with 7, 4 with 8.

Depending on which version of Traktor you are using, and if you are using a qml-mod already, you will find the relevant lines in a different file. The one below should be the standard location of the HotCue commands:

Found in the file: 'Resources64\\CSI\Common\HotcuesModule.qml'

    WiresGroup
    {
      enabled: !module.shift

      Wire { from: "%surface%.pads.1";   to: "hotcues.1.trigger" }
      Wire { from: "%surface%.pads.2";   to: "hotcues.2.trigger" }
      Wire { from: "%surface%.pads.3";   to: "hotcues.3.trigger" }
      Wire { from: "%surface%.pads.4";   to: "hotcues.4.trigger" }
      Wire { from: "%surface%.pads.5";   to: "hotcues.5.trigger" }
      Wire { from: "%surface%.pads.6";   to: "hotcues.6.trigger" }
      Wire { from: "%surface%.pads.7";   to: "hotcues.7.trigger" }
      Wire { from: "%surface%.pads.8";   to: "hotcues.8.trigger" }
    }

    WiresGroup
    {
      enabled: module.shift

      Wire { from: "%surface%.pads.1";   to: "hotcues.1.delete" }
      Wire { from: "%surface%.pads.2";   to: "hotcues.2.delete" }
      Wire { from: "%surface%.pads.3";   to: "hotcues.3.delete" }
      Wire { from: "%surface%.pads.4";   to: "hotcues.4.delete" }
      Wire { from: "%surface%.pads.5";   to: "hotcues.5.delete" }
      Wire { from: "%surface%.pads.6";   to: "hotcues.6.delete" }
      Wire { from: "%surface%.pads.7";   to: "hotcues.7.delete" }
      Wire { from: "%surface%.pads.8";   to: "hotcues.8.delete" }
    }

Changed to:

WiresGroup
    {
      enabled: !module.shift

      Wire { from: "%surface%.pads.5";   to: "hotcues.1.trigger" }
      Wire { from: "%surface%.pads.6";   to: "hotcues.2.trigger" }
      Wire { from: "%surface%.pads.7";   to: "hotcues.3.trigger" }
      Wire { from: "%surface%.pads.8";   to: "hotcues.4.trigger" }
      Wire { from: "%surface%.pads.1";   to: "hotcues.5.trigger" }
      Wire { from: "%surface%.pads.2";   to: "hotcues.6.trigger" }
      Wire { from: "%surface%.pads.3";   to: "hotcues.7.trigger" }
      Wire { from: "%surface%.pads.4";   to: "hotcues.8.trigger" }
    }

    WiresGroup
    {
      enabled: module.shift

      Wire { from: "%surface%.pads.5";   to: "hotcues.1.delete" }
      Wire { from: "%surface%.pads.6";   to: "hotcues.2.delete" }
      Wire { from: "%surface%.pads.7";   to: "hotcues.3.delete" }
      Wire { from: "%surface%.pads.8";   to: "hotcues.4.delete" }
      Wire { from: "%surface%.pads.1";   to: "hotcues.5.delete" }
      Wire { from: "%surface%.pads.2";   to: "hotcues.6.delete" }
      Wire { from: "%surface%.pads.3";   to: "hotcues.7.delete" }
      Wire { from: "%surface%.pads.4";   to: "hotcues.8.delete" }
    }

This takes care of HotCue functions and LED feedback.

Use a good coding editor like notpad++.