M4L vs ROLI Studio Player

Craig Latta's icon

Greetings. I wrote a M4L device for my ROLI lightpad, which works great. However, when I add the ROLI Studio Player plugin to an Ableton track, it tries to load its own code onto the lightpad, and proceeds to fight with M4L over control of the lightpad. I notice that Studio Player has the ability to "lock" a lightpad to a particular plugin instance, so that multiple instances of Studio Player don't fight with each other.

I can capture the sysex that gets sent for this feature, but when I send it myself as part of my M4L device startup, it has no effect. Has anyone figured this out? Thanks!