All USB MIDI devices are greyed out when opening Live

[InteraX]

Hi there,
This is a recent issue that started a couple of weeks ago.
When I open Live, I have a custom Default Set.
In this Default Set, I have 3 track groups. In each track group is a MIDI track and an audio track.
In all my MIDI tracks, the pre-defined MIDI From and MIDI To is always greyed out, with the exception of 1 MIDI To setting.
All MIDI From settings are set to my MIDI controller (Novation Launchkey Mini Mk3) and the Midi To is set to my instrument USB MIDI with monitor set to 'Auto'.
To get things working again, I have to click the drop down menu and re-select the relevant source/destination each time I open/close Ableton.
How can I configure things so I don't have to keep doing this?
Thanks.

[molicki]

thanks for posting this.. I have the exact same issue and now i know i aint trippin..

did you happen find a fix?

I'm using a launchpad, and a mpk mini mk3 so could it be the controllers?

If i load the set normally, everything works. If i save it as a default set then when it loads, the mk3 is greyed out, even tho its active and listed in the prefs..

if i find a solution ill post it.

good luck

[[email protected]]

I've got exactly the same issue with all controllers including Yamaha Motif which is greyed out. I get a message saying 2 devices are trying to connect to drums, and it greys out everything, so I have to to reassign all track MIDI inputs, including those that don't have a drum option.

[scruffyfox]

add it to the list

viewtopic.php?p=1829992
viewtopic.php?t=251379
viewtopic.php?p=1829262

[supersaw]

Hey guys, I've got the same issue. And every time when switching on an additional midi device during a session, all other devices are greyed out again, so that all of them have to be selected again manually ...
But it only happens with Ableton Live version 12.1.x. Versions 11.3.x and 12.0.x work fine. Too bad that Ableton Live song-files aren’t backwards compatible…
I hope, there'll be an update soon

[henris42]

Same problem here. It seems to happen with some devices always, and some do start correctly.