yes, I’m running 3272 - and I’ve got things working now after some crazy experimenting.
But there seems to be something really weird going on with this setup - I’ll need to elaborate a bit, so I recreated a simpler version of my problem in a demo file. It consists of three racks:
The first (Guitar OnPedal) waits for CC66, then depending on its state either raises a trigger (#7) to set the guitar rack (Rack 4) to a lead sound or it sends another CC66 to the next rack (GuitarReturn) to then return the guitar sound to its original state.
The GuitarReturn rack contains just a binding that waits for CC 66 and then raises a state-specific trigger to return Rack 4 to a preset sound. So for its first state, it should send trigger #0, for the second state trigger #1 etc.
Now I set my Rack 4 to its third state and repeatedly press my soft pedal. The Guitar OnPedal rack dutifully switches back and forth between its two states and also sends CC66 to the GuitarReturn rack:
In the Guitar OnPedal rack bindings page, the LED for the binding lights up, so the trigger should be raised; also on the song leven bindings page, the LED lights up as well:
(both “State” LEDs turn green)
But Rack4 stubbornly stays at State 3.
Now it gets interesting:
- when I manually trigger the binding on the song-level bindings page by clicking the triangle, Rack 4 dutifully turns to State 1
- when I manually trigger the binding within the GuitarReturn rack, Rack 4 changes state correctly
- when I manually trigger the binding within the Guitar OnPedal rack, Rack 4 changes state correctly
- when I connect the Main Keyboard to the GuitarReturn rack instead of through the Guitar OnPedal rack, Rack 4 changes correctly
So it looked like somewhere between the Guitar OnPedal rack and its successor, something goes wrong, even though all optical indicators (MIDI monitor, Binding LEDs) signal that things are happening correctly. I suspected this was due to the fact that the Guitar OnPedal rack changes its own state on receiving CC66 and possibly messes up the routing.
So I changed the state-switching binding in the Guitar OnPedal rack to “Load State by index (delayed)” instead of “instant”. And suddenly everything works - Rack 4 dutifully switches back to State 1!
So - to cut a long story short: it looks like even though both the MIDI monitor as well as the bindings LEDs indicate a correct transmission, the state changing of the OnPedal rack (and the deactivation of the binding that sends CC66 to the GuitarReturn rack) interrupt the flow of the message that was sent before the changing of the state. Not sure why the state change should interrupt a CC message that has already been sent (and that shows on a MIDI monitor) and why the binding LEDs should flash but the actual binding not be executed??? Maybe some crazy multithreading issue?
I’ll send you the song file via email - maybe you can find some logic here…
Plus one annoyance I found while editing: when I change one of the problematic bindings’ target from “instant” to “delayed”, suddenly this changes the source from “Controller (No Edge Button)” to “Controller” and messes up the “value” column on the target side when I change it back to “Controller (No Edge Button)”. Maybe also something for the bug fix list?