Mapping Two different colors on a Xone:K1

[strz]

Hello gentlemen, i have a simple question

Im Using a K1, and i want to map the following thing
Lets say i have a button mapped to an effect 1 in my group
I would simply like it to light - RED when it is not activated and when it is activated - GREEN



Thank you in advance !

[Stewe]

Unlike many other controllers the K2 uses specific midi note that determines which color is going on display. Check the user manual to see entire button/color scheme.

Firstly disable latching layer system in your K2.

Since we will be using one note per color you we will need two different outputs for one button/command.

1st command: Button OFF STATE
Controller Range / min=0 / max=0
MIDI Range / min=0 / max=127
Note assignment / Note for RED color

2nd command: Button ON STATE
Controller Range / min=1 / max=1
MIDI Range / min=0 / max=127
Note assignment / Note for GREEN color

This should work in theory I sold my K2 so I can't test it right now

[strz]

Uhm i tried it but... im not really sure if im doing it right.
Can you please walk me through it a bit more detailed...

And i dont know why i wrote X1 in the topic title when im talking about the K1... faceplam

[padi_04]

fixed your title =)

[Stewe]

Uhm i tried it but... im not really sure if im doing it right.
Can you please walk me through it a bit more detailed...

And i dont know why i wrote X1 in the topic title when im talking about the K1... faceplam

Like I said before I don't have a K1 or K2 to test this for you. Anybody here with K1 here can chime in?

[Sulherokhh]

Color switching on the K1/K2 are pretty buggy. The only workaround i found to make sure 100% that an altered state/modifier switches from one color to another (not from on to off or vice versa) is by using BEAT PHASE Midi-Out Assignment. It can't be used for everything, only for states that are in the list of selectable conditions.

Use it like this (example for modifier#1 switching from 0 to 1):

Add Out ---> Deck Common ---> Beat Phase
Assignment: Deck A [B/C/D]
Control: LED
Interaction: Output
Controller Range : -0.5/0.5
Blend: X
MIDI Range Min: 5 (With the K1/K2 this means Color On)
MIDI Range Max: 127 (With the K1/K2 this means Color On)
Mapped To: [MIDI Key for GREEN]
Condition1: modifier#1 = 0


Add Out ---> Deck Common ---> Beat Phase
Assignment: Deck A [B/C/D]
Control: LED
Interaction: Output
Controller Range : -0.5/0.5
Blend: X
MIDI Range Min: 5 (With the K1/K2 this means Color On)
MIDI Range Max: 127 (With the K1/K2 this means Color On)
Mapped To: [MIDI Key for RED]
Condition1: modifier#1 = 1

Result: The Button will light GREEN when modifier#1 = 0, it will light RED when modifer#1 = 1.

WILL ONLY WORK if Deck A is running! So i personally do the assignment 4 times, once for each Deck [A, B, C, D] so it doesn't matter which Deck is running.

Rationale: Beat Phase constantly updates it's value, so the assignment is checked constantly and so the LED is activated constantly because the MIDI Range changes along the values. This works, although Value 5 and Value 127 express the same LED brightness (K1/K2 only knows on/off) but the change still registers.

Don't bother to use "Global --> Send Monitor State". It's buggy as it is, even more so with the K1/K2, and only puts a strain on the processor.

[Stewe]

Color switching on the K1/K2 are pretty buggy. The only workaround i found to make sure 100% that an altered state/modifier switches from one color to another (not from on to off or vice versa) is by using BEAT PHASE Midi-Out Assignment. It can't be used for everything, only for states that are in the list of selectable conditions.

Use it like this (example for modifier#1 switching from 0 to 1):

Add Out ---> Deck Common ---> Beat Phase
Assignment: Deck A [B/C/D]
Control: LED
Interaction: Output
Controller Range : -0.5/0.5
Blend: X
MIDI Range Min: 5 (With the K1/K2 this means Color On)
MIDI Range Max: 127 (With the K1/K2 this means Color On)
Mapped To: [MIDI Key for GREEN]
Condition1: modifier#1 = 0


Add Out ---> Deck Common ---> Beat Phase
Assignment: Deck A [B/C/D]
Control: LED
Interaction: Output
Controller Range : -0.5/0.5
Blend: X
MIDI Range Min: 5 (With the K1/K2 this means Color On)
MIDI Range Max: 127 (With the K1/K2 this means Color On)
Mapped To: [MIDI Key for RED]
Condition1: modifier#1 = 1

Result: The Button will light GREEN when modifier#1 = 0, it will light RED when modifer#1 = 1.

WILL ONLY WORK if Deck A is running! So i personally do the assignment 4 times, once for each Deck [A, B, C, D] so it doesn't matter which Deck is running.

Rationale: Beat Phase constantly updates it's value, so the assignment is checked constantly and so the LED is activated constantly because the MIDI Range changes along the values. This works, although Value 5 and Value 127 express the same LED brightness (K1/K2 only knows on/off) but the change still registers.

Don't bother to use "Global --> Send Monitor State". It's buggy as it is, even more so with the K1/K2, and only puts a strain on the processor.

Thank you for your input Sulherokhh!

I didn't knew that K1 and K2 suffer from that same issue...
The Send Monitor State command works perfectly fine on my i5 (Z2 audio) and i7 (Traktor Audio 2) which meets Traktor's system requirements. And I'm using it for years in my mappings and I have never hear anyone who had reported a problem with pops and clicks in audio because of the mapping only until recently. Which was the Traktor version when you started to notice this issue? And do you use a PC or a Mac?

Those processors are pretty powerful and they shouldn't be at all stressed about sending a couple of messages to the controller unless there are some problems with audio drivers.

[Sulherokhh]

I use a PC, not of the highest calibre. I use the Soundcard of the S4Mk1. Send Monitor State only troubles me when i have about 10 mappings in the oven. Obviously every mapping will get processed by the command and so i get spikes, sometimes cracks. Well, my system really isn't optimal. ^^

[BUG_RANT]
It all started with Traktor 2.8.1 i think. The version with Freeze/Slice Mode added where the Remix-Deck Bonus Bugs had their first appearance. STEM-Support made it even worse. I am still considering not to use any version other than 2.6.8. I don't need most of the bonus features, although they are fun to map, and the inherent bugs (like recording levels being tuned by the main software gain) are quite managable. The only real gripe is the missing DualCore support.
[BUG_RANT/]

[strz]

Meh, f--k it, i quit trying to map this BS.
Im really disappointed in the K1's LED functions.

No Brightness, only 3 colors, difficult to map...

Thank you for all your help, gentlemen.

[Stewe]

You are welcome.

Now I remember why I sold my K2 controller... It was useless for advanced mappings