Thanks! Yeah the Code is a nice piece of kit, it took me a while to get the Code editor to work like I wanted to, but once it's configured, it's pretty flexible
Yes I had that problem too, but I fixed it. The most important part is to have your LED rings update locally (you can change that in the editor) AND to control the LEDs through Traktor. Usually people pick one of the two, they either have the LEDs update locally (without Traktor's output) or only by Traktor, but you need to enable them both. I tried using it without the local LED control, but it would cause the LEDs to update like a second after I turned the knob, not useful at all
So in the Code Editor it's setup like this:
CC Numbers: All the encoders AND LED rings are set to the same CC numbers, going from "1" to "32". This is important by the way, if you set the encoders and the LED rings to the same CC numbers, whenever Traktor outputs an LED (after a reset for example), it will also reset the current value of the encoder itself. That is what you need for your encoders+LEDs to work properly in conjunction with a reset button. By default the LED rings are set to different CC numbers, but just configure them to the same and it will work. This is also nice for Ableton btw, since you don't have output commands there. When you update a knob on the screen, it will also update on your controller this way.
Note Numbers: All the push buttons are set to notes, going from "1" to "32", the same numbers as the encoders (easy to remember ).
Mode: All the encoders are set to "Absolute", that way they work as a standard knob (or fader) instead of an actual encoder. All the pushbuttons are set to "Momentary" since it doesn't matter for Traktor anyway (you can let them work as a toggle even if they are momentary).
Resolution: I have Encoder speed A at "1x" and Encoder speed B at "1/2x". This is NOT ideal though, because my ideal setting would be somewhere between "1/2x" and "1x", but there's no option in the dropdown menu to configure it like that. It would be ideal if they would give us a percentage value to fiddle around with, I also mentioned this on the Livid forums.
Style: The FX are all set to "Fill", the EQs and Filters are set to "EQ" and the Gains and Loop Size are set to "Walk". You could pick other ones, but setting them like I did is pretty intuitive.
LED ring local control: "Absolute" is enabled, since your encoders are all set at "Absolute" anyway
In Traktor I've set it up like this:
All the encoders are set up like as a "Fader / Knob" with "Direct" as Interaction Mode.
Soft takeover is NOT enabled on any of them, it doesn't really work anyway
All the LED rings are set up just as default, so controller range from "0" to "1" and midi range from "0" to "127" (Blend is ON).
The push buttons that work as a reset button are mapped to the same command as the encoders, the only difference is that they're mapped a button input with the "reset" function.
Like I said before, if the CC numbers of your encoders match the CC numbers of your LED rings, it will work like a charm. You turn the knob, the value on your screen changes and the LED on your code updates locally. You push the reset button, Traktor resets the knob on your screen, outputs the LED value to the LED on your Code AND changes the current value of your encoder itself on the Code, since both have the same CC number. When you turn your encoder after you've pushed the reset button, the value won't jump anymore (or start from where it was BEFORE you pushed the reset button).
I've included my Code preset and TSI file for the Code, that way you can test it out.
The Code presets goes under "C:\Users\username\AppData\Roaming\Livid\Code2 " if you're on Windows, that way it'll show up in the editor.
Code Preset: https://dl.dropbox.com/u/7776728/29122012_Traktor.json
Traktor TSI: https://dl.dropbox.com/u/7776728/29122012_CodeV2.tsi
What was your nickname there? I heard they closed it a while ago, too bad
Bookmarks