pcoopergardner

Does anyone know of a simple way to set a TouchOSC controller value without output, à la a "set __" message? For most controls - faders, rotaries, etcetera - a simple feedback loop doesn't result in a loss of control. However, when I attempt the same strategy with a multitoggle (exclusive mode), it does indeed result in a runaway feedback loop.

Any suggestions would be most welcome. c


touchosc-feedback-loop

I'm using the Liine Lemur app and having similar problems getting visual feedback with toggles. My workaround now is to not have visual feedback for the toggles, but instead just have the lemur toggles (actually called switches) show their state. They also have "radio button" mode that helps. This isn't ideal, or really addressing your question, but I thought I'd mention it.

I'm using the Liine Lemur app and having similar problems getting visual feedback with toggles.  My workaround now is to not have visual feedback for the toggles, but instead just have the lemur toggles (actually called switches) show their state.  They also have "radio button" mode that helps.  This isn't ideal, or really addressing your question, but I thought I'd mention it.


Can you just ignore input for a while after setting the value?

I've gone for something similar to what Andrew suggests, when you operate the fader, feedback is not passed until 200ms after the last activity. I'd like to find a better way though.

https://cycling74.com/forums/live-object-live-observer-for-remote-control-how-to-prevent-a-feedback-loop

TouchOSC - feedback loop