Xone 1d/2d/3d/4d Lightpipes/Light rings
Xone 1d/2d/3d/4d Lightpipes/Light rings Posted on: 14.10.2010 by Layla Portela Has anyone gotten the lightpipes/light rings to work in Traktor Scratch Pro? I've searched the interweb for an answer and have not found anything that resembles a decent answer. I have tried adding an out for deck focus select, and then assigning it to the respective deck but then from there I have no idea how I would go about doing it. I am specifically trying to get them to change state depending on which deck is the focus deck, and maybe if I can take it one step further have the corresponding light ring blink if a loop is active on that deck. I am running TSP 1.2.6 on a 15" MBP using a Xone:2d if that helps at all. | |
| Layla Portela 14.10.2010 | Has anyone gotten the lightpipes/light rings to work in Traktor Scratch Pro? I've searched the interweb for an answer and have not found anything that resembles a decent answer. I have tried adding an out for deck focus select, and then assigning it to the respective deck but then from there I have no idea how I would go about doing it. I am specifically trying to get them to change state depending on which deck is the focus deck, and maybe if I can take it one step further have the corresponding light ring blink if a loop is active on that deck. I am running TSP 1.2.6 on a 15" MBP using a Xone:2d if that helps at all. |
| Teresia Janusch 10.11.2010 | when you say 'set up light pipes correctly' i take it you mean its set to map 2 for traktor? working my way through your thread to get mine to work |
| Layla Portela 18.10.2010 | Thanks again for the explanation Yul, and I apologize if the problems I am running into seem hurr durr, the finer points of modifier states and the exact logic and processing order of operations in Traktor's controller manager is something I am only now really coming to grips with. Your explanations so far have been very helpful, and the examples provided have given me a lot of insight into how the modifiers work and what is/is not possible. I did finally get it to work, but I did it as follows (and decided to scrap the button hold method): I did like you mentioned and assigned a modifier to the bottom row of buttons to toggle M4 between 1-4 depending on which button I pressed. Setting M4 from 1 to 4 also toggles each of the 4 lightpipes on and off as well as setting the deck focus correctly. This gives me a M4=0 for non-deck mode as well as m4=1-4 for deck modes A through D. |
| Kecia Wnukowski 17.10.2010 | I believe I already answered almost that same exact question from you in another thread not so long ago. http://www.djranking s.com/community /showthread.php?t=19005 But mixing the two threads together: if you plan to use the modifier I suggested you don't need deck focus select and you don't need it to light up the pipes. The problem with deck focus select is that it has always a value (0 from 3, 0 being something: deck A): ie in this system , if set properly, a led would always be lit. If you want to use deck focus select anyway, I just gave you the way to do it:
that translates:
Out deck focus select: for deck focus A button 1 :controller range 0-0 / midi range 0-127 for deck focus B button 2 :controller range 1-1 / midi range 0-127 for deck focus C button 3 :controller range 2-2 / midi range 0-127 for deck focus D button 4 :controller range 3-3 / midi range 0-127 Remember also that 'deck focus select is a kind of additional built-in modifier in a way in fact, the only difference is that it translates its states or conditions with the ASSIGNMENTS. So either you use deck focus select but that ruins a bit your starting idea for the 3 rows of buttons (being obliged to hold one button to select a deck - once again not something deck focus select can do as it will be like one of your button would always be on hold - or better you use the modifier seen together in the previous thread. In this last case, the commands to light the pipes would be a modifier 'X' output, not a 'deck focus select' one. that would translate to for the first light pipe: modifier X output command with modifier condition when modif=0: 0-0 /0-0 (no button hold) when modif=1: 1-1/127-127 ('deck a' is hold) when modif=2: 2-2/0-0 (unlit) when modif=3: 3-3/0-0 (unlit) when modif=4: 4-4/0-0 (unlit) now reproduce the mapping for the second light pipe, switching the range 127-127 accordingly to the position of the led (ie it will be lit when modif 2-2, 127-127). and then the other two, doing the same. I'm detailing a bit on purpose. That's 5 commands X 4 different mid notes =20 commands in total (for the outputs) |
| Layla Portela 17.10.2010 | Well I've proven that the lightpipes work, but there's still some functionality that is either erratic or I am not programming something right. I am using the bottom 4 buttons above the rotary encoder on the 2d to select deck focus as well as create a shift hold based modifier X - X - X - X Those are my 4 buttons, in the unpressed state M4=0 when the first X is pressed, M4=1, second X M4=2 and so on until M4=4 I am then using M4=0 on the 4 buttons to cycle through deck focus first X selects deck A, second X deck B and so forth. However I want each of the 4 lightpipes to light up to indicate the focus deck. It works perfectly with deck A and deck C, but B and D are giving me problems. I set up the programming as follows Out Deck Focus Select mapped to Note A#4 (first lightring) controller range 0-0 (for deck A) midi range 127-127 (on) modifier condition M4=1 Out Deck Focus Select mapped to Note A#4 controller range 0-0 midi range 0-0 (off) no modifier condition this makes the first lightring perfectly light up every time deck A is the focus deck and turns it off when another deck becomes the focus deck. However duplicating the exact programming for deck B does not create the same results. The second lightpipe/lightring only briefly flashes every time deck B is the focus deck. Randomly for deck C the same programming for deck A works no problem, totally as expected however deck D exhibits the same odd behavior that deck B does. Any thoughts? |
| Kecia Wnukowski 16.10.2010 | Cool |
| Layla Portela 16.10.2010 | Yay, it worked! Thanks Yul. Found out what the problem was, the user manual incorrectly labeled the note. It says it is A#3, its actually A#4. |
| Kecia Wnukowski 15.10.2010 | ok, I understand it may be confusing so: - check your driver and firmware (in case) - set the 2d for midi channel 16 (which you are on apparently), it translates as having the 4 light pipes lit when doing this step if I remember correctly (please check). - at the step for midi map, choose midi map 1 (usually used for traktor it means the top row of encoders would send two midi notes when turned instead of a CC) - I don't remember here but if there's a step to tell the light pipes to light on and off at this stage do it. do a simple test Now go into your controller manager: - do the correct settings for in and out ports and check that the device is set to focus - create a modifier 1 that you would set on hold for a value of 1, this modifier will be your first light pipe's button - check what is the note sent please (what midi channel, is the note sent is the good one, if not, go to step 1 or check you're not working on the natural shift layer of the 2d - yes, the 2d has two midi layers, you activate the second layer by pressing the 'natural' shift from the unit and the little screen tells you you're on the shift layer). - check that there no other kind of functions related to this button (in case there are some already, erase them or reset them so they're not active). - check you see within the controller manager, the modifier 1 getting a value of 1 when the button is hold, and gets back to 0 when it isn't. - create a modifier 1 output with the same midi note - hold your button, the led should lit on and off when the button is pressed or not. Does that work? |
| Layla Portela 15.10.2010 | This part makes perfect sense I wrote previously you had to : - The deck output command has a controller range from 0 to 3 (0 being deck A, 1 being deck B, etc...) so you have to tell for each light pipe what they do depending on the deck focus range (and apply the midi range accordingly) that translates: Out deck focus select: for deck focus A button 1 :controller range 0-0 / midi range 0-127 for deck focus B button 2 :controller range 1-1 / midi range 0-127 for deck focus C button 3 :controller range 2-2 / midi range 0-127 for deck focus D button 4 :controller range 3-3 / midi range 0-127 Where I get confused is I tried this exact configuration and it did not work. I set: Out deck focus select: Set CH16.NoteA#3 (since my 2d is on channel 16 and A#3 is the leftmost button/lightring, at least according to the user manual) Set controller range to 0-0 and left midi-range alone (0=off, 127=on) Did not mess with the invert or blend settings (but ticking or unticking either box did nothing) Cycling deck focus had no effect on the status of the LEDs. I will check my audio firmware, drivers and midi firmware but I only recently updated the firmware on it and am 100% positive running MIDI firmware 1.10. |
| Kecia Wnukowski 15.10.2010 | Guess what, you're not the only one to own a 2d, there are hundreds out there, I did have one and the light pipes do work perfectly with traktor it's just a matter of settings. Now I don't pretend that you may not have eventually a defective unit but you get the point. And you don't need Bomes. I've just done it on another A&H controller, and it works fine. I wrote previously you had to : - The deck output command has a controller range from 0 to 3 (0 being deck A, 1 being deck B, etc...) so you have to tell for each light pipe what they do depending on the deck focus range (and apply the midi range accordingly) that translates: Out deck focus select: for deck focus A button 1 :controller range 0-0 / midi range 0-127 for deck focus B button 2 :controller range 1-1 / midi range 0-127 for deck focus C button 3 :controller range 2-2 / midi range 0-127 for deck focus D button 4 :controller range 3-3 / midi range 0-127 that works if you set up your light pipes correctly and if your "in" functions for deck focus select are correct too (and if of course your hardware is up to date, drivers and firmware speaking) |
| Layla Portela 15.10.2010 | I am still having issues getting the LEDS on the Xone 2d to respond to any kind of output messages in Traktor. I went into the lightpipe setup and changed it so that the lights now respond to midi messages (or at least they should) However I still cannot get the LEDS to do anything. According to the manual the leds should respond to a the corresponding notes the buttons, so the leftmost button should be Note A#3, but setting an output for deck focus select and setting it to that note does nothing, no manner of combinations between the min max and the midi range makes the leds do anything other than stay unlit. There also seems to be something regarding how old my Xone2d is as the one I own does not have the 'light conn' text by the button. I've also been reading many conflicting reports on whether the lights even do work in Traktor at all. Does anyone know if the lights can be used at all in Traktor with an older 2d? I don't care if I need to sort out some workaround through Bomes, but I'd like to know or see someone that actually has the lights working and doing something before I go down that route and possibly waste a lot of time for nothing. |
| Layla Portela 14.10.2010 | You are right in that the question is frequently asked, you are however the first person to give me an answer that seems like it was written in proper logical english. Although I do deserve a personal /facepalm for totally glossing over the lightpipe setup page in the manual, that was super smrt of me. Thanks however for patiently answering my question again Yul! |
| Kecia Wnukowski 14.10.2010 | It's probably one of the more asked question about the D series man... I've just made a search and found several topics on the subject... - You have to set up correctly your light pipes from the unit (read the manual it's at the very beginning) - The deck output command has a controller range from 0 to 3 (0 being deck A, 1 being deck B, etc...) so you have to tell for each light pipe what they do depending on the deck focus range (and apply the midi range accordingly) As for the led blinking you'll have to use the beat phase monitor output command, note that it may not be accurate 100% of the time for led feedback (ie if you're under a 1 beat loop, the led won't blink - well for me they don't ^^). Traktor lacks a global command output to have blinking leds. You'll have to integrate the modifier 'is in loop' (0 being not in loop, 1 being in loop) to all your output functions. The modifier 'is in loop' comes directly from Traktor (within the drop down menu for modifiers "inside the function"). |
<< Back to Post and find Controller MappingsReply