Traktor breaks commands up into Ins (Going from the controller, hopefully doing something) and Outs (Feedback from Traktor to the controller.) Combining both of these allows two-way communication between the client and controller,so the position of any control remains constant across the system.
I will assume that readers will be familiar with how to put their TouchOSC user interface together, with appropriate controls
used for the tasks at hand. Care should also be taken to ensure that Channel and Number fields do not repeat.
Once we have a rudimentary UI, we are likely to have several groups which need to have their Ins and Outs assigned.
Allocating Ins is generally quite intuitive, especially with the reference articles given in the resources section. Outputs
aren’t always quite as straightforward. If simple feedback is all that’s required, the Output and input are mapped to the same MIDI signal.
LEDs are a little different, but provide a good insight as to how these things fit together:
Should signals interfere with each other, separate the controls in the group into more specific sections, and allocate a different MIDI
channel to each. Continue with this, refining your allocations so they start coincide with the original design.
Points of interest:
When using a touchpad, assign a value for x and y, these axes ought to also have the same channel, but different numbers, so that two functions can be allocated within Traktor, such as effect volume and pitch, separately, as indicated by our resources.