I recently have some troubles mapping 2 layers of cuepoints on my Xone K1.
Basically the mapping is similar to the NI X1 MK1 Standard Mapping.
You got 4 buttons mapped to cuepoints 1-4 with modifier5 ( as an example ) = 0 and on the same buttons triggering cuepoints 5-8 using modifier 5 = 1. SO far this works pretty well for the Midi Ins.
Coming to the LED Mapping ( the Midi Outs ) I pretty much struggle with 2 things.
Mapping the HotCue - State
Well - if you believe the Traktor documentation these states are valid :
Controller Value -1 / Midi Value 0 → no hotcue
Controller Value 0 / Midi Value 1 → cue
Controller Value 1 / Midi Value 2 → Fade In
Controller Value 2 / Midi Value 3 → Fade Out
Controller Value 3 / Midi Value 4 → Load
Controller Value 4 / Midi Value 5 → Loop
Controller Value 5 / Midi Value 6 → Grid
But what are the usual Midi - / Controller - Ranges resulting from this.
I think there is no blend on a K1 Controller.
So basically I thought that I only need to map the exact controleller value
For example a Fade Out would result in a controller range of 2min & 2max - right ?
But what about the midi range ? I thought it is 0 (off) - 127(on)
Can you help please ?
I actually have some pretty weired behaviour regarding to the LED output. Sometimes they switch of randomly when I change the type of hot cue as if there is a state missing that is not mapped.
Switching between LED outputs for hotcues 1-4 and 5-8.
When i switch between LED outputs for hotcues 1-4 and 5-8. via modifier the LEDs do not change.
The expected behaviour would be
Modifier 5 = 0 → Show LEDs for hotcues 1-4
Modifier 5 = 1 → Show LEDs for hotcues 5-8
Is there anything important that I missed out expect adding proper modifier conditions to all midi outs
that represent a hotcue ?
Controller range: Min = -1 // Max = 5
MIDI Range: Min = 0 // Max = 127
Map “Send Monitor State” command on your modifier input buttons. (K2 has a hard time refreshing controller output while changing button states with a modifier)
thanks for the immediate reply but I still wonder about the midi range.
You said that I should leave it at the default value ( -1 / 5 ).
But how do you manage to have a differently colored LED output based on
the value that is transmitted from Traktor to the controller.
Sorry if that was a bit unclear but I’d like to have for example a green output for a loop,
a red one for basic cues / grids and a yellow one for Load markers - as an example.
So I think I need those pretty tight midi ranges to have a clear seperation.
Or is there some basic knowledge that I completely misunderstood so far ?
Regarding the Send Monitor State : Thanks for this information. I heard about terrible
audio dropouts when using this method. Did you have a similar experience so far ?
I’ll check this later and see what happens.
Hi Daniel,
K1 and K2 has a dedicated MIDI Note for each of different color unlike any other controller out there (check your user manual for more information on this) that’s why I said to leave MIDI Range at 0 to 127.
As for different cue types there is a modifier condition called “Hotcue 1-8 Type”. You should definitely check that out if you already did not knew about it.
Send monitor State can indeed give you a trouble with high CPU spikes BUT only if your machine is not well optimized for DJing and Music Production. Which I never had issues with on my Mac or PC. Hopefully your system rocks as well
well - I fixed the problem and so far it was not based on my mapping
It became more and more obvious that the second controller that was linked using the X:Link protocoll was a bit lame.
This again was the first controller where the problems occured.
So - having contacted the global A&H - support service I got the answer that I need to update my MAC OX from El Capitan to Sierra.
I did this today and … nothing happend. The problem was not solved.
Because I still thought that the real problem was based on less power for the 2 controllers on new Macbooks I did the following :
I added an active USB - Hub, added both controllers - each with a seperate USB cable ( no more X:Link !!! NO NO NO ) and gave each a seperate identifier. Switching to Traktor I gave each controller it’s own midimap ( both need a seperate midichannel )
Result :
Blazingly fast led performance, incredible responsive, tactile handling and extremely bright lights. Now this really starts to be huge fun. Shame on the A&H support - this could have been managed in a better way than simply forwarding me to a standard answer.
But I’m glad having found a definite solution for my problem
