Problem using a midi controller to launch midi clips

[MGrouse]

Hi,

I'm making a set for live use where I switch between different instruments in an instrument rack. I have followed various tutorials where chain selector is used (for example: https://www.youtube.com/watch?v=tcdLKrSuYDE)

The workflow:
. Instrument rack
. Each instrument in the rack is given a unique chain number in chain selector
. I add MIDI clips on the track in question, and add envelope automation that corresponds to a chain selector number (e.g. if I trigger the first MIDI clip 1, with the chain selector envelope set to '1', then the chain selector in the instrument rack moves to notch '1'

----

This is all well and good. It works pretty seamlessly when I use the mouse to launch the clips / change patches OR if I use a QWERTY keyboard with key assignments. Ideally though, I'd use available pads on the MIDI keyboard I'm playing with (AKAI MPK miniplay mk III) to replace the mouse clicks or qwerty keys. Like a normal MIDI mapping, I open the MIDI Mapping dialogue, click where you'd launch the desired MIDI clip and then touch the pad on my AKAI controller.

As soon as I try to launch this clips and in turn chain patches, it seems like Ableton completely freezes (even audio meters get stuck) and then as much as 10 seconds later, the midi clip launches and things return to normal UNTIL I try to switch to another patch using another one of the AKAI's pads.

I have been tearing my hair out trying to find solutions. I can't really understand why there would be such a difference between triggering the patch changes via key mapping rather than MIDI mapping.

I wondered if it was something to do with the AKAI putting out MIDI note values and if it was getting stalled because a pad press is techincally putting out 2 messages straight after eachother (note-on and then note-off). I then tried a different midi device to trigger the midi clips (korg nanokontrol2) mapping the solo buttons, which put out midi cc data instead but the same stalling happens.

Is this a known bug? Is it something I'm doing wrong? Any help would be greatly appreciated!

I am attaching a screen rec to try and demonstrate the problem and also to show settings in case there's an obvious culprit (google drive link below): https://drive.google.com/file/d/1CcXZ2O ... sp=sharing

In case it's useful:
Ableton Live 12 Suite 12.4.3
MBP 2021 M1 Max
Sequoia 15.7.4
Memory 64GB
500GB storage remaining on the internal SSD

All the best,
M

[chapelier fou]

Sounds like midi feedback loop. Try to figure out what’s causing it by unchecking unnecessary routings in the midi prefs tab.

[MGrouse]

Sounds like midi feedback loop. Try to figure out what’s causing it by unchecking unnecessary routings in the midi prefs tab.

I think you're right! I disable the track and remote options on the IAC Driver Bus in Midi settings and it seems to have fixed the problem! Thank you

[chapelier fou]

I'm glad I helped. Have fun !