Why is live.object sending twice?

bouke's icon

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?

Max Patch
Copy patch and select New From Clipboard in Max.

Here is an example - click the bang - and the value is output twice:

Julien Bayle's icon

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!

Max Patch
Copy patch and select New From Clipboard in Max.

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

broc's icon

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.

bouke's icon

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

Dimitri Aatos's icon

I think it's because both live.observer's inlets trigger it to output.

Max Patch
Copy patch and select New From Clipboard in Max.

I made a workaround patch to make live.observer behave like a normal max object, triggered only from the left inlet.

Dimitri Aatos's icon

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

mda's icon

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