Need help using Hotcue State with LED

[lsmith]

heh of course .. but i guess for them the "fix" was the X1 ..

[B33SON]

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.

Actually, sounds like a really good idea.

[alkmst]

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.

[lsmith]

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

[B33SON]

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.

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.

[alkmst]

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?

[B33SON]

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.

[JCribb]

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.

Would you mind posting up your bomes file so I can take a look at how you programmed it?