Maboroshy

Interesting device. On my system I often get "0 123" to [ctlout] and [midiout] having a race condition. Resolved that by inserting [deferlow] to the [midiout] path.

The way it works, I always get some non-root note bleed when changing chords, since I don't take chords instantly.
Maybe making the device to wait a set amount of time for a stable chord before root detection would resolve that.

Randomizer is a part of my new Parameter Value Buttons device at at
https://maxforlive.com/library/device/15041/Parameter%20Value%20Buttons

Free as usual.

No I don't. Grab it! If you want to thank me - spread the word.

Great idea! I'll try to implement that in a future release.

The device can select chains, it does that on preview animation. Max for Live has no way to get rack's chain selector zone for a specific chain. The idea is that the device replaces rack's chain selector so you don't have to update zones when rearranging chains.

I could add more buttons but I think about making universal "button device" that can be mapped to any parameter instead.

I'll implement the delays in the next version.

I've updated the device to fix the chain selection issues and improve rack detection. Please check the new version.

To change chains and play notes simultaneously, you'll need to disable the “Disable Inactive” and “Cut Off Notes” options and use only “Mute Inactive.” Enabling and disabling devices takes time, so notes played right at chain change may end up somewhere in between. I advise leaving a margin between changing the chain and playing notes.

I've resaved the device and put it to the testing branch on GitHub, please check:
https://github.com/Maboroshy/Max-for-Live-Devices/raw/refs/heads/testing/Exclusive%20Chain/Exclusive%20Chain%201.0%20(MIDI)%20(test).amxd

Can't reproduce. I open a new Live set, double click the file, get the device on track. Same Live 12.3.