Hit this issue repeatedly during a rehearsal yesterday. Discouraging. I could never be sure if my song was initialized correctly and the expected routes were enabled. Often resulted in “No Sound” …
Came home and I’ve spent hours attempting to subset the problem in a separate Cantabile Configuration for study and diagnosis. But every time I simplified anything (like removing plugins from a song file, or taking irrelevant bindings out of the Background Rack, or altering bindings in a linked rack), the issue vanished.
-
It does not seem to me that the issue is related to the particular CC I’m using (#39), so I’ve change the title of this thread from ‘Are some MIDI controllers “Special”?’ to “Bindings Not Firing, Round 2”.
-
I believe this is related to the Bindings Not Firing issue from a year ago. However, that’s just a hunch - I have no direct evidence.
-
The issues seems highly dependent on what is in memory - removing even one plugin can cause the issue to vanish. Changing which song was previously loaded can cause the issue to come and go.
-
I’ve addressed the issue previously by switching from bindings that send CCs to a linked rack to bindings that fire global triggers. That sledge hammer solution doesn’t work in my current scenario, since I need to send a a value along with the message output by the binding …
The video …
… does show the issue happening from an (off screen) rotary encoder, but it also happens if I fire the binding from the enclosing song file by explicitly triggering the binding by clicking on the “fire binding” widget.
I suspect the issue may be related to timing and the delays I have installed on various bindings to get things to work. I don’t fully understand (read: “I barely understand the basics of …”) Cantabile’s timing controls on bindings.