Once again, thank you for your help and for the detailed explanation. I’m slowly making progress with my mapping. Not everything works as expected — sometimes it works, sometimes it doesn’t — and I’m trying to find solutions through a process of trial and error.
Right now, I can’t get a button to stop lighting up when a Cue Point is deleted. I’ve set the button LEDs on the second layer to yellow (C5, G#4, E4, C4), and when I delete a Cue Point using Modifier 1 (Shift), the Cue Point is removed, but the button remains lit.
My second question is more theoretical: is it possible to implement the following logic on the second layer (M2=1)?
Regular Cue Points are illuminated in yellow.
Saved Loops are illuminated in green.
When the Shift button is pressed, all saved Cue Points and Saved Loops change to red (delete mode).
Thanks again for such a detailed explanation and for the screenshots. With your help, I managed to get everything working.
There’s just one small issue I’ve noticed that’s a bit inconvenient. When I delete any HotCue, the corresponding button stops lighting up (which is exactly what I expect). However, if I immediately assign a new HotCue to that same button, the LED doesn’t update. I have to press Layer, switch back to the “control” layer, then return to the HotCues layer, and only then does the LED for that HotCue light up.
Are You sure You have EMPTY CUE value (which equals “-”) for every CUE type You are using?
Can You post a screenshot like one from me in the message above. How the same CUE button looks like for all CUE types used on the same button? Notes can be different on the same button, but this button should have EMPTY cue value for EVERY color you are using. For example. Green color out for loops and green color out for “-”, red color out for CUE and red color out for “-”.
When I dive into this mapping, I start having panic attacks.
I decided to finish the mapping before my next gig, and I spent about three hours adding all those values for every single button. I finally got everything done, then started putting together my playlist. I only had a couple of tracks left to reach 60 minutes when Traktor suddenly crashed… BAM. Everything was gone. Nothing had been saved. It was a huge disappointment.
After a while, I pulled myself together and rebuilt the mapping from scratch. But apparently I still misunderstood something along the way.
By the way, you have an excellent YouTube channel. Special thanks for the video where you explained how to set up the PSP42x. Please keep making more videos like that!
Thank You!
I see Your current mapping looks good? Hotcue 1 type on deck A misses the EMPTY cue value, but maybe it’s just how it scrolled in the application.
And yes, it’s harsh to lost 3 hours of work because of crash. Now export your config more often. And my recommendation, don’t overwrite it! Make an incremental copies when exporting. I’m talking from my personal experience.
BTW, I see You are using all types of values for the CUE? Are You using all of them? Because I’m not mapping the things I’m not needed.
I figured out the problem. I had misunderstood the advice you gave me earlier, but after reading your previous message everything became clear. It turns out that for every MIDI note used to display Cue Points, you need to define at least two states: the “-” (empty) state and its corresponding “active” state.
I really like Traktor, but honestly, this feels a bit outdated to me — especially for DJ software. As I understand it, I have to keep closing and reopening the program for changes to playlists or configuration files to be saved properly. I don’t understand why NI hasn’t added an Auto-Save option where the user could choose the save interval. That would seem much more logical and convenient.
“BTW, I see You are using all types of values for the CUE? Are You using all of them?”
Well, I set the regular Cue Points myself while previewing tracks. Traktor creates the Grid marker automatically during analysis. I don’t actually use the Load marker, but I thought it might come in handy someday. But thanks for advice…
I have another question as well. Am I right in thinking that I could use the third layer to control effects in Bitwig, like you showed in your video? For example, assigning the knobs to effects like Blackhole, Lexicon, and maybe another one? Is that difficult to set up? How did you learn to put all of this together?
The thing with the Bitwig - I’m not using layers anywhere except on the buttons at the bottom of K3. And keep in mind. In our case with Traktor, these “virtual layers” are only inside the Traktor. The controller itself always sends and receives the same notes from the same button/fader/knob. That means, every other control knob/button/fader are always are the same and I just mapped them to the effects in Bitwig. The only difference, at the same time, two programs are using the same controllers but they are using the different parts of the controller.
Now export your config more often. And my recommendation, don’t overwrite it! Make an incremental copies when exporting. I’m talking from my personal experience. 
