Push Current State Disappearing In User mode (SOLVED)

[PoonceDoctor]

This is my first post on the support forum so please bare with me if this is a bleedingly obvious fix or i emit some important information.

I'm trying to use the first three pads on the 8x8 grid to mute/unmute a channel. I know these functions are available in normal mode but i'm just fiddling about and i want them on this page too.

Midi mapping them to those three pads is easy enough.

-Illumination, channel isn't muted.
-No illumination, Channel is muted.

Yay, that was easy!

Except... if i have some channels un-muted (pad is illuminated) and i click "User" to go back to normal functionality, then click "User" again to come back, all the lights go off regardless of what state i left them in. If i click on a pad that should be illuminated (but isn't) the channel will mute and the light will stay off, if i click it again the pad finally illuminates and the channel un-mutes.

What's going on here? Given the fact the push's lights don't change if i tap one that not illuminated when it should be or vice versa, it (or at least ableton?) knows what state it should be in, but it doesn't light up the appropriate lights when i click "user" after venturing into the other parts of push. Like the lights aren't initializing or something when i go into user mode.

Is this a known problem? Is there a fix?


Any advice appreciated!

[metastatik]

The state of LEDs in User Mode is not stored. So, anytime you switch to User Mode, all LEDs will be turned off.

There is no fix for this AFAIK, but you can workaround it by switching to User Mode and then entering/exiting MIDI mapping mode. All LEDs will be refreshed upon exiting MIDI mapping mode.

[PoonceDoctor]

There's no way around it? That's a pretty annoying design flaw. If entering/entering midi mode fixes it why couldn't ableton make it do that every time you go into user mode? Hopefully that's fixed in a firmware update.

Anyway, hitting cmd + m on my laptop is pretty tedious and slow. Is there anyway to trigger that by hitting a pad on the push in user mode? I'm nearly certain that it's not but i thought someone might know of some 3rd party software or something that can make it happen.

[metastatik]

Sure, there’s other ways to workaround it, but nothing that would be as straightforward as entering/exiting MIDI mapping mode.

You could use a piece of software like Midi Translator to translate the MIDI message that one of the pads/buttons send into a keystroke (such as Cmd+M). You could, alternatively, use software like Midi Translator to store LED states and recall them upon switching to User Mode. The latter would allow you to have more control over LED colors.

Another option would be to create a MIDI Remote Script that refreshed the controller’s state upon switching to User Mode.

And, lastly, you may be able to put something together with Max for Live.

[PoonceDoctor]

Thanks!

I found some free software called midiStroke and i've managed to get that to send cmd+m twice when i hit the pad nearest to the User button. Pretty decent work around. I'll keep tinkering to see if i can get the user button itself to trigger the event but if not this current system works.

I appreciate your help kind sir!