Hello,
I've been getting back to using Traktor with version 4, after having used standalone DJ systems for years. I tried connecting my standalone DJ system into Traktor as a controller for it, and was delighted to see just how good sounding and super low latency Traktor Pro 4 is when using the Standalone DJ system as a controller, as opposed to using it in standalone! Those poor DenonDJ systems must have **** CPUs, as their processing latency is much worse than a modern laptop running T4. So now, I want to take the most of my existing gear, and I've been making a custom mapping for the device by myself..
FWIW the device I am using is a DenonDJ SC Live 2. I found a mapping for SC Live 4, which I've been digging into, and was able to suss out things such as the CC numbers for controlling the peak meters etc.. But am only using the SC Live 4 mapping as a learning resource. I want to build my custom mapping from scratch, as this also teaches me how to do custom mappings on my own. I always want to know what makes things tick..
So far, I have all of the basics working great! Most of the controls on the surface work more or less as intended, including shift functions. There is however, one last hurdle I find myself struggling with.. The dynamically changing UI of the 4 performance pads, and the CUE / LOOP / ROLL mode selectors above them.
Ideally, I'd like to mirror the functionality of the Standalone operation - I press the CUE selector, and the 4 performance pads update themselves to show my first 4 hotcues from traktor. Then, if I press LOOP or ROLL mode selector, I'd want the 4 performance pads to update their view & functionality to mirror the selected mode.. But this doesnt seem to be anywhere as easy / intuitive as anything else I've yet done..
It is my understanding, that its always best to use the internal Traktor 4 conditional UI feedback when this is available, instead of relying on using the Modifiers, because even if the modifiers are easy enough to set, any changes in the modifier statuses do not update to the LED outputs without some sort of extra command? Is that right? For example, I'm using the "Show Hotcue 1-4 state" conditions to control the hotcue performance pads, and they update dynamically and perfectly whenever those hotcues are set, deleted etc.
So, I ask the community for guidance. First off, what would you recommend as best practice for interpreting which mode I have currently selected? Should I just use a single Modifier, and just change its integer value to reflect the selected mode (ie, lets say Modifier #3 - if I set CUE mode, M#3=1, if I set LOOP mode, M#3=2,if I set ROLL mode, M#3=3)? Or would it be wiser to use a discreet Modifier number for each mode (ie, setting CUE mode sets M#3=1, setting LOOP mode sets M#4=1, setting ROLL mode sets M#5=1)? I'm assuming its better to use a single Modifier number, since I want the three modes to be mutually exclusive, otherwise I'd have to add modifier value resets for each one, adding lots more lines..
Then, comes the hard part = How do I then tell the LEDS to update themselves? At the moment, I am unable to get the mode select LEDs to even work as intended - if I press a mode, sure enough the button lights up, but then if I press the next mode, that button also lights up, and if I press the third mode button, now all the mode buttons are lit up.. I'd obviously only want the currently selected mode LED to light up, and the rest should turn off..
And this is just for the mode select buttons! Then I'd need to figure out how to actually get the 4 performance pads below to follow mode "focus"..
TIA for any assistance!
