if user needs just 2 layers for some use cases, why he must scroll through 3 layers and make extra unnecessary button press every time?
Completly agree! I have two K3âs and use them for 2 decks each and would love to have an option to limit them to 2 layers (one for each deck) instead of 3.
It would be interesting to know what strategy the Xone team has for supporting current products.
Are they motivated only to fix critical bugs?
Are they have enthusiasm to add new features and listen to user ideas?
Do they even read the forum?
Hi @Goanguru, @s0medud3
Welcome to the community ![]()
Of course we read the forums ![]()
And maintain enthusiasm to add features and listen to our customerâs ideas and suggestions.
check the guidelines
With respect to your opening point @Goanguru,
What in particular are the âuse casesâ youâre considering?
Itâs possible solutions already exist.
In terms of @s0medud3 âs comment
- assuming âdecksâ is referring to an app like Traktor Pro (?), the option to have only two layers of control can potentially be achieved within the softwareâs local options, and together with using the K3 with hardware latching layers off.
Neither point here rules out potential ânew featuresâ for the hardware.
But if you can provide a bit more context and info, we can get a better idea of on your aims, and so offer more focussed guidance in replies
- and more info is always useful to know when weâre considering feature requests

With respect to your answer, but are you joking or didnât read the first message carefully?
Use case is very simple:
software 1: Xone user uses one layer - no questions
software 2: Xone user uses all three layers - no questions
software 3: Xone user uses just two layers⌠why he must scroll through 3rd empty layer and make extra unnecessary button press every time?
Do you think itâs somehow possible to jump over Layer 2(or Layer 3) when scrolling layers with LAYER button?
From my point of view, this is a very simple modification that is not difficult to program in your software.
In Tractor, you can generate what you want by applying a modifier to all the mapping lines, although that would mean disregarding one of the two conditions. xoneoficialâs answer is correct but impractical for complex mappings.
I have complex mapping in Traktor with modifiers. 3 layers, with different colors for every layer (You an create only 2 layers if you need).
- Green layer. Everything for transport. Controls decks, PLAY/STOP/CUE, LOAD/UNLOAD tracks, browse songs, change tempo, SYNC ON/OFF, pitch bend buttons (if SYNC OFF), beat jump buttons (if SYNC ON) and buttons for HOT CUE jumping.
- Red layer. Controls (create/delete/jump-to) 8 HOT CUE points for every deck. Green button - HOT CUE LOOP, Red button - HOT CUE point;
- Yellow layer. Various settings of Traktor. RECORD button ON/OFF, FX slots ON/OFF, KEY LOCK ON/OFF, SNAP/QUANT ON/OFF buttons, 4 view change buttons, full-screen ON/OFF;
Here is a short video how it works.
Iâm now using Djay Pro which unfortunately doesnât have advanced Traktor-style modifiers, but only a single âShiftâ modifier. Holding the shift button doesnât influence the LED feedback of other buttons. Furthermore, I would like to use more than 3 colors to better differentiate between two decks mapped to the same K3 controller. K3âs LEDs are so freaking awesome and great looking when I turn it on, I would really like to use them as much as possible. ![]()
Example:
- Layer 1 - Deck A with its own set of colors
- Example: Play button is green, CUE is yellow, SYNC is red
- Layer 2 - Deck B with its own set of colors
- Example: Play button is turquoise, CUE is orange, SYNC is purple
As far as I can tell this is not something that is possible even in Traktor without enabling latching layers. But then as @Goanguru said, you have to skip the 3rd unit layer every time when switching the decks with the âLayerâ button.
It would make things so much easier if we could have the ability to configure the controller to have 2 or 3 unit layers. Maybe as a 4th POWER ON SETUP mode? That way we could have all the latching layer options but also an ability to have 2 or 3 unit layers. For some of us that donât need the 3rd unit layer.
Hopefully this explains it a bit more. ![]()