How do get the hotcue led's to turn off when pressing the "hotcue" button on the x1?

[funke]

I've been searching all afternoon and can't seem to find an answer to my problem. I started off making a fresh mapping for my x1. I mapped the lower buttons to act as hotcues when the "hotcue" button is selected just like the factory mapping. I mapped the led's to the hotcues, and while they turn on and off with the hotcues fine, they don't turn off when I push the "hotcue" button to switch to the other functions. As far as I know, I can't map the "hotcue" button as a modifier. Does anyone know what I need to do to get them to turn on and off with the hotcue state?

[padi_04]

The hotcue layer is a different hardware layer that shouldn't interfere with the regular. Did you mad the leds correctly for your normal layer?

[funke]

Thanks for your response. I'm going to have another look at it tonight. I might compare it to the stock mapping and see what I can find.

[padi_04]

You shouldn't need modifiers unless you are doing everything in MIDI mode, where the hotcue layer is non exsistant.

[Stewe]

You can sacrifice one button, maybe hotcue 8, and map that button for shift (modifier) if you wish possibility to delete cue in MIDI mode.

[funke]

I'm not using midi mode. The controls all work fine. It's the led mapping that is giving me trouble. I copied the led mapping from the default mapping. It has a led mapped to both the hotcue and shift/hotcue. I mapped led's to the hot cue buttons in normal mode as loop indicators. Those work fine in normal mode, but when I have eight hot cues lit up in hotcue mode and hit the hotcue button, those are the only leds that go off.

[funke]

Are you saying that I need to have leds mapped to the base functions in order to have the hotcue leds turn off when switching from hot cue mode?

[funke]

It is true! In order for the hotcue leds to turn off, the primary functions must have leds mapped to them even if those leds are not mapped to any particular function or even ever turned on.