Xone K3 - 2 layers

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 :waving_hand:

Of course we read the forums :slight_smile:
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 :nerd_face:

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).

  1. 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.
  2. Red layer. Controls (create/delete/jump-to) 8 HOT CUE points for every deck. Green button - HOT CUE LOOP, Red button - HOT CUE point;
  3. 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. :smiley:

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. :slight_smile:

Hi @s0medud3
Thanks for the extra info. Feedback’s appreciated.

Different apps offer different features and not all work with MIDI in the same ways.

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. :smiley:

Example:

  • Layer 1 - Deck A with its own set of colors…

  • Layer 2 - Deck B with its own set of colors…

While djay PRO doesn’t include complex modifiers, as of today, Agoriddim’s v5.6.3 update now officially supports Xone:K3.
The latest release provides a plug & play set up for full dynamic control of the app across three layers, including;
Layer 1 - 4 Decks, Browse/Transport/EQ/Neural EQ/Loops
Layer 2 - Single (focus) Deck; full control, all decks.
includes Browse/Transport/Cues/EQ/Stems/Loop/FX/Filter/Key and more
Layer 3 - Sampler and 4 Looper Track control

It also includes options to change LED colours direct from the app.

As far as I can tell this is not something that is possible even in Traktor without enabling latching layers

Traktor Pro’s options are the most extensive, but software mappings become complex.
An extra ‘Layer’ shift is currently possible using the app’s modifiers etc as @Vandit74 and @Isotoxin mention.

With Xone:K3‘s Layers OFF, up to three colours are available to each LED per control.
So it’s possible your examples are doable, but this level of integration in Traktor’s mappings is not straight-forward.

We continue to work with different developers to find the best solutions for many varied uses.
Info will be shared online in due course.

Feature requests for an ‘Inc/Dec’ type option for K3’s hardware Layers from yourself and @Goanguru are duly noted.

In the meantime, I hope the news for djay PRO users is welcome

Hi!
Same question here:
Is there any chance we can have an option to choose how many layers we want to be active? There are only two options now: just one layer (with latching layers off) and three layers (latching layers on). So if I only need two layers to be active I still need to press the “Layers” button one extra time to switch between MY MAPPED layers.
Example:
I have latching layers ON and I want the first layer (SWITCH MATRIX) to be the control layer for all 4 decks (PLAY/PAUSE, CUE, SYNC, LOAD) and I want the second layer to show 4 CUE Points for decks A, B, C, D. The third layer is not mapped as long as I don’t need it. And I want to have a possibility to simply switch between TWO layers jumping from CONTROLS to active CUE POINTS. And to do that I need to press the LAYERS button one extra time more at this moment and I find this very annoying especially when playing 4 decks and trying to control everything.. ) So it would be great if you could please add an option in controller editor to make the layer ACTIVE or INACTIVE. Thank you!

Which software Your are using?

Hey… I’m using Traktor Pro 4

I’m assuming You are using your own custom mapping in Traktor? In this case, use internal Traktor mapping features for two layers you need (2, 3 or even 8 layers). For this to achieve you need to disable layers on the K3 itself, upgrade firmware to the latest version and use one modifier in Traktor. You will need to use SEND MONITOR STATE command for layers to update after pressing layer change button on the controller.

Thanks for your input. I’m trying to implement your advice and struggling with Claude at the moment ))

Today after work I will create an empty TSI template for You with two layers.

Here is a simple example of two layer TSI file for Traktor4. I have created it with K3 controller (latest firmware version) but it should work with K2 to. Controller should be set to MIDI channel 15.

TSI file itself has 9 commands (5 input and 4 output). Every command is commented:

Pressing the LAYER button (lower left corner) will swap colors of this button from GREEN to RED (or vice versa). And at the same time it will change MODIFIER #1 (M1) state from 0 to 1, or from 1 to 0 (depends which state was set previously - …0>1>0>1>0…). M1 state change to 0 will lit this LAYER button in RED, M1 state change to 1 will lit this LAYER button in GREEN. So let’s call them GREEN and RED layers. To achieve this color and M1 swapping, there is a four “Modifier #1” commands. Two IN and two OUT. Two IN commands will toggle M1 state from 0 to 1, or from 1 to 0 with condition checking. Two OUT commands will change the color of the button respectively with the same condition checking.

M1 state is used on the other commands to follow the layer itself. And it works like this. The very next button above the LAYER button can be used to trigger “PLAY DECK A” (will lit GREEN) or “Toggle unit FX1” (will lit YELLOW). But this button will ALWAYS depend on M1 state (condition check). It will work as a “PLAY DECK A” button if M1 will be 0 (GREEN layer). And it will “Toggle unit FX1” if M1 will be 1 (YELLOW layer). And finally, if You toggle the LAYER button few times when both features are active (“deck A playing” and “FX1 unit is ON”), the color of this button above the LAYER button will change and it will work only when the corresponding layer is engaged. The LED color will always swap with the last command - “Send monitor state”. It just refreshes the current state of LED lights on the controller.

Here is some limits of this solution:

You can add more layers by using higher M1 values (…0>1>2>0>1>2>0…). But because LAYER button can only have 3 different colors it is not possible to REPORT which layer is active at the moment with a single button color (it is possible to use a combination of few buttons, but it is more complex topic).
Another one thing to keep in mind. Because You have only two modifier condition fields in Traktor, that means one of these fields will be always used to track which layer is active for ALL the commands in that layer. You are stuck with only one condition field for your needs.
And the third thing. If the button is used in one layer, it should have something added on OUT in all the other layers. If you leave the button empty on other layers, then the color from the first layer will not swap to EMPTY color with the “Send Monitor State” command. Because there is nothing to swap to. :grin: For example. I’m using some fake status colors from features I’m not using in Traktor. OUT command on the empty buttons in other layers with features like “CUE button”, “not used FX units” or anything.

I hope my explanation will help You. :smiling_face:

Thank you very much! :yellow_heart: Will try this out :raising_hands:

That is exactly what I was struggling with. Thanks for the explanation!

I’m stuck… And I don’t really understand how to solve this problem.

Let’s say I want to have two layers: Layer 1 > Controls, Layer 2 > Hot Cues.
I want the left column on LAYER 1 to control my deck A and I want to map 4 buttons in the pad section as follows: 1 button > PLAY/PAUSE, 2 button > CUE, 3 button > SYNC ON/OFF, 4 button > LOAD SELECTED. And on LAYER 2 I want those buttons to be Hot Cue 1, Hot Cue 2, Hot Cue 3 and Hot Cue 4… And the problem starts when I’m trying to select the button mode.
Xone Control Editor allows me to set the button to work in Gate (Hold), Toggle or Trigger Modes. And Traktor wants some buttons to work in Hold mode and some buttons in Trigger mode only. For example “LOAD SELECTED” button allows me to select Trigger mode only. And when I switch to Layer 2 and try to set the cue point with this button it doesn’t work correctly… How can I solve this? Thank you.

So the first thing You need to do - reset the K3 to the default settings and disable native latching layers on K3. Set the midi channels you need (different midi channels for two K3 controllers) and that’s it! The good thing with Traktor - You don’t need to think about how every button works on the MIDI controller natively (I don’t remember which mode is default for K3 buttons - i think hold, like piano key). Buttons can be toggle or trigger or gate but Traktor will solve this for you inside Traktor software itself. You can change color combinations for buttons inside Xone Controller Editor, but keep in mind the same color combination will be used on every Traktor layer. This is just how the colors works on the Xone K3 at the time.

After you set the controller to the default settings, use ONLY INTERNAL software Traktor button types inside the Traktor itself. If You need the hold button (like SHIFT) just use the HOLD settings in Traktor controller editor. If you need the toggle type button (PLAY/PAUSE) use this type of button by setting it inside Traktor. There is no difference how buttons are set internally in the controller by the Xone Controller Editor. Traktor will do everything for you inside the DJing software itself!