Bug report, track mute with external controller, midi learn

I'm going to freak out, the buttons only respond from the second or third press for track mute with a mapped external controller. This makes the controller unusable unless you have pressed two or three times on each button before launching the live, which has the gift of annoying me for a machine at the cutting edge of technology.

The midi message is present from the first press and I tried all the possible midi settings, nothing worked, I'm up to date and I got a set to prepare.

Seriously Akai what are you doing at the moment, exept implementing authentication at each start for plugins which in my opinion will also cause issues the day I won't have any connection.

The MPC live will eventually learn to fly if this joke continues it will add one more function that does not work.

Maybe the controller is sending data in a toggle type way which would make the stuff change every second press - sounds like that's on the config and mappings side, not the MPC itself

handthrow wrote:Maybe the controller is sending data in a toggle type way which would make the stuff change every second press - sounds like that's on the config and mappings side, not the MPC itself

Thank you for your answer, I dug a little on this side and it works correctly by disabling the "toggle" function of the controller buttons and if the tracks are not mute on the MPC.
If they are mute then I still have to press twice for the button to respond, it's not ideal but it's better, the controller is a Livid DS1, if other people have the same, the web interface used to configure it still works here is the link: https://lividinstruments.com/editor_2017/



If only the midi feedback worked for the LEDs this would be the best controller ever with MPC Live, maybe with the next updates I have to wait before teaching it to fly