There's probably a very obvious solution/explanation to this, but I'm tired of beating my head into the wall 
I'm working on a very simple patch to observe the state of the loop bracket in arrangement view and, based a few parameters, potentially turn off the master record button if it has been on.
I am using several live.observer objects to monitor the loop position and other information -- these were a breeze to setup...
The output information is being filtered through several "if" objects to selectively output a bang (to a live.object) in only a few specific cases.
However, the critical problem is that these bang messages seem to be unable to trigger the "set record_mode 0" message leading to the live.object. When the "set record_mode 0" message is clicked directly, or even when the switches leading to it are flipped manually, the message is transmitted with no problem. But when I leave the patch to its own devices, I just watch as the toggles turn on and off when appropriate bangs are sent while somehow the "set record_mode 0" message is unresponsive.
Any thoughts? Needless to say, I apologize in advance for wasting everyone's time if this is something stupidly obvious...
Unresponsive "set" triggering with live.object
Sat, 01/23/2010 - 15:43
Unresponsive "set" triggering with live.object
