X1MK3: Community Performance MOD (qml coding)

I'll have a look at it and compare it to my baseline (Aleix's SupremeMod beatcounter, adjust slightly by me for accuracy).

Yes, but i won't do it for either mod. The first mod has a toggle to switch off mixer layout entirely. The second mod doesn't have the mixer layout at all. Pressing a button once or twice when setting up to go where you want the layout to go shouldn't be too much work. :)

Open the file '…\qml\CSI\X1MK3\X1MK3FXSection.qml'

Close to the top is a property descriptor that stores the current layer state and what the default state (value) is. It looks like this:

MappingPropertyDescriptor {
  id: layerProp
  path: module.propertiesPath + ".fx_section_layer"
  type: MappingPropertyDescriptor.Integer
  value: FXSectionLayer.fx_primary
  …
}

Change this part … :

value: FXSectionLayer.fx_primary

… to this:

value: FXSectionLayer.mixer

Mapping states like this (indicated by the full name of the path containing the word 'state') always reset to their default value when reloading the mapping or restarting Traktor.

Here is an alternative approach.

This line,

path: module.propertiesPath + ".fx_section_layer"

when resolved for 'module.propertiesPath' actually looks like this:

path: "mapping.state.fx_section_layer"

You can change the line, exchanging 'state' with 'setting', to make the mapping actually save the last used value, so that if you exit Traktor (or disconnect the controller), it will recall the last value next time you start Traktor.

Like this:

path: "mapping.setting.fx_section_layer"

This way, you can have your controller always in the preferred state, even if your preference changes.