Cantabile’s “Tools → Options → MIDI Ports → Device Settings” button offers an option to control which devices receive “All Sounds Off” messages. But I’ve noticed that unchecked devices in that list still seem to receive “All Sounds Off” messages when Cantabile shuts down. Is that a bug?
I’m believe I’m the user that asked Brad for that feature because the “Panic Button / All Sounds Off” would send midi data that affects a few channels on the X32 and there was no way to filter out these low level commands at the midi port.
Refer to Panic Button / All Sounds Off
With that said, I tried to duplicate your problem and could not. When the box is not checked and panic button is pressed, the X32 faders do not move. When the box is checked, the faders move. When the box is checked and Cantabile exits, the X32 faders do not move.
Even when the panic button was sending the midi “All Sounds Off” packets before the feature was added, I do not remember the faders ever moving on a Cantabile exit. The problem only happened when Panic was activated. I wonder if Cantabile is cleanly shutting down in your situation?
If you have any particular cases you’d like me to attempt to reproduce, please respond in this thread or DM me.
1 Like
Hi @easteelreath!
Thanks for the response. I appreciated your feature request because I have a similar situation: My control surface’s lights go wonky whenever I exit Cantabile, presumably because Cantabile sends it some standard MIDI messages that don’t make sense for a control surface.
Digging a bit deeper, the most consistent weirdness is that Cantabile always resets CCs 64, 66, and 67 to zero whenever I close certain songs (e.g., via New Song or Exit menu options). I think maybe it only happens when the song has first sent some note MIDI events to the device (which is how one changes light RGB colors on it). I did two experiments:
- I loaded a song that sends some note events to the device on startup (which changes some lights on the device). Then I deleted everything from the song, including all plugins, racks, bindings (even in the background rack), so that any subsequent MIDI events going out to the device must be generated solely by Cantabile. Then I selected “New Song” from the menu. Result: The lights corresponding to CCs 64, 66, and 67 turned off at the moment the empty song unloaded.
- I closed and restarted Cantabile, and loaded the same now-empty song. To manually turn on lights 64, 66, and 67, I created and triggered three bindings that send value 127 to those CCs. Then I selected “New Song” from the menu. Result: The lights stayed on. Cantabile did not turn them off.
This seems to show that these events are coming from Cantabile, but only when some previous activity (probably note events?) has caused Cantabile to think that the device needs to receive these extra MIDI CC messages on exit.