Need help using Hotcue State with LED
I’m trying to highlight a grid of LEDs on my Maschine controller to show when a button already has a Hotcue assigned to it. I thought “HotcueX State” under Out in Traktor 1.2.2.
Anyhow, the state doesn’t seem to show when their is a cue active. Is there some trick to this?
I was able to do this for the padKontrol, but I don’t remember what I tweeked to get it to work and I’m not in front of Traktor atm. Hotcue X State ouputs what state hotcue x is in, ie if it’s a loop cue, then it’s 8/8 out of 127, if it’s a grid, it’s 1/8 out of 127, or something similar.
I believe what I did was have it output 127 when the state was greater than -1. Are using any type of paging on your maschine, cause you might have to use bomes to have it refresh the states when you page, as Traktor won’t resend the state unless it’s changes.
Well… The mapping seems to half work. The pad does light up when the corresponding hotcue exists, but then as soon as I press the pad to trigger the cue, the Pad looses its highlighting. There was a suggestion about setting the “Invert” setting on another thread, but that didn’t work for me. 
I remember now. I had to use bomes to correct that. I basically had traktor send out the state, which I stored as a variable in bomes, and then had bomes send a 127 out to the padkontrol if the state was greater than 0, or a 0 if 0. I’m not sure why it only stays on for a sec, but I think it’s because the pad is acting as a momentary pad instead of a switch, and when you set it to a high, as soon as you let it go from pressing it, it returns to a low but doesn’t recieve a new high from traktor so it stays low.
Hi, I just joined this forum because I have ran into a similar issue and it seems what I want to accomplish is not doable with the new version of TP.
Long story short -Kontrolpad, LPD8, Nocturn and I even tried the microKontrol all have LED pads that are contolled by the hardware unit (choice from momentary or toggle) and it cannot be bypassed, perhaps BOME will help as DJ Phaidon mentions, its unfortuante as I am trying to take advantage of the Hotcue state.
Here is the feedback I have been getting on NI’s forum.
http://www.native-instruments.com/forum/showthread.php?t=99634&highlight=hotcue
I have had success with the Hercules Steel Control as the LEDs rely solely on software. I may have to look into the Midifighter DIY controller as I think that will be controlled by software also, buts I havent decided yet.
The issue is that, even if you can set the hardware to a momentary or a toggle, Traktor doesn’t resend the state after the hotcue has been pressed.
The solution I came up with was basically this, and this was the sole reason that I bought bomes until I realized all the cool stuff it could do.
-Have traktor output the state of each hotcue for each deck
-This output is stored in a bomes as a variable, one variable for each hotcue for each deck, so 32 variables
-anytime that a variable changes, it triggers a clock specific to the deck
-anytime that a hotcue is pressed, it triggers a clock specific to the deck
-(on a side note, any time a page is pressed, it triggers the clock also so my 16 padkontrol buttons turn into full control for 4 decks with LED feedback for the hotcues.)
-when the clock is triggered, the hotcue LED’s are lit or extinguished based on the state of each variable for each deck.
Problem fixed, but it’s not a very simple solution. Would be easier if it was sent from Traktor itself.
thats what they have their proprietary protocol for .. sigh
I suppose I can try this… a pitty though. I just got rid of Bomes… now it’ll have to come back. lol.
shouldnt it be possible to provide a fairly generic TSI and bome script to manage those variables inside bome? then all that would be needed is to adjust the sending of the proper MIDI messages depending on the given controller used.
possible, but would be an easier fix inside of Traktor I would think. All they would have to do is add a funtion to resend the states after any hotcue was pressed or modified.
heh of course .. but i guess for them the “fix” was the X1 ..
Actually, sounds like a really good idea.
Yes it does. However NI would have to take it further and do this for rest of other midi out LED assignments. As no matter what midi funtion is chosen it may provide inaccurate status results after hitting the pads on various controllers such as Maschine.
BTW .. slightly off topic, but i would assume the audience from this thread would also appreciate my vision for the 3.0 mapping .. which basically consists of routing everything through Bome for much much greater flexibility .. obviously also enabling stuff like what is discussed in this thread
i wouldnt mind if any of you do agree with this vision that you use whatever opportunity you have to convince Ean that this is the way to go 
As far as I can tell, Christmas has come early. Traktor 1.2.3 fixes this issue. My pads now highlight and stay lite as expected.
Thanks for the update.
I will have to buy back my button Led-based controllers and see this fix with my own eyes.
Did you have any unusual midi assignments I should be aware of?
Nope. Nothing special. I didn’t change anything. It just worked.
Would you mind posting up your bomes file so I can take a look at how you programmed it?