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

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.

Thanks for the reply guys. @Julien.bayle - interesting - I didn't know that already, I'll update my patch, thanks!

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.

and by the way the title says live.object, it would be helpful if you could correct the title

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. :-)