Why is live.object sending twice?


    Jan 25 2010 | 9:40 pm
    If 'id #' is in the right inlet, and 'property ' is in the left, using 't b l', the 'initialization' of the 'live.observer' makes it send the value twice. Is this really default behavior?
    Here is an example - click the bang - and the value is output twice:

    • Jan 25 2010 | 10:36 pm
      live_set seems to have the id 1 it seems to be a particular case in which observer sends value when id 1 feeds them.
      strange!
      btw, for grabbing tempo info, Andrew adviced me to use metro/transport instead the live API:
      but I'm sure you already knew that :D
    • Jan 26 2010 | 10:08 am
      bouke,
      I think in your example the bang is not really needed for initialization since live objects are triggered automatically when loading the patch/device. Sending an additional (redundant) bang seems to cause the unexpected behavior.
    • Jan 26 2010 | 12:42 pm
      Thanks for the reply guys. @Julien.bayle - interesting - I didn't know that already, I'll update my patch, thanks!
    • Dec 26 2015 | 10:37 pm
      I think it's because both live.observer's inlets trigger it to output.
      I made a workaround patch to make live.observer behave like a normal max object, triggered only from the left inlet.
    • Jan 01 2016 | 12:55 am
      and by the way the title says live.object, it would be helpful if you could correct the title
    • Oct 16 2016 | 5:39 pm
      Dimitri - I have used your live.observer workaround subpatch in a max for live device. I have credited you. I hope this is OK. I have not found a way to PM you, or find a facebook or similar for you to ask you up front.
      Thanks for the workaround, it works perfectly. :-)