GP 3.5 / Windows 10 / Focusrite Scarlett 4i4
This is a recurring issue for me and happened twice in a gig last night, causing LOUD stuck notes that do NOT respond to MIDI panic.
When switching songs (and thus rackspaces, as I typically use a custom rackspace per song), if I accidentally have the sustain pedal depressed when switching, the rackspace I’m switching FROM will get stuck MIDI notes. MIDI panic does NOTHING to resolve the issue, presumably because the stuck notes are from the previous rackspace. Most of my rackspaces use multiple MIDI input blocks and multiple VSTs to implement keyboard splits.
The stuck note problem can ONLY be resolved by loading up the previous song/rackspace, finding the EXACT notes that are stuck on the keyboard and playing them again (to get a proper MIDI off message to fire). I can switch rackspaces a hundred times, but as soon as I reload the offending rackspace, the stuck notes are there, playing loudly and proudly. Obviously, in a live scenario, this is bad news and is quite embarrassing.
The obvious fix would seem to be to instruct GP to send an all MIDI notes off message when switching rackspaces. Is this possible? Alternatively, sending a sustain OFF message when switching rackspaces might solve it.
MIDI panic seems to only panic on the current rackspace, which limits its effectiveness.
As of now, I can’t rely on GP for live gigs because of this issue and it’s a real bummer.