Live API: and communication timing

    Feb 01 2010 | 9:16 pm
    Hi! I have an OSC client that sends data to my M4L patch, I have a fader that is mapped to a track volume in Live. It works moving the fader on my OSC client and the Live volume moves with it. One thing though, I have an observer on the track volume, to make the fader on my OSC client move when I move it in Live. This makes moving the fader on my OSC client a bit wobbly, because moving the OSC client fader triggers the observer, which sends it back to my OSC client updating it there immediately.
    Is there a way to avoid this? For example, there could be some way, when the OSC client fader moves, that a max object will consume the output of the volume observer immediately, avoiding it being sent back to the OSC client.
    Not entirely fluent with Max yet though so some hints are appreciated :)

    • Feb 02 2010 | 6:27 pm
      check live.remote~ instead of live.object