Forums > Max For Live

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 ‘’ makes it send the value twice. Is this really default behavior?

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

-- Pasted Max Patch, click to expand. --

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.


btw, for grabbing tempo info, Andrew adviced me to use metro/transport instead the live API:

-- Pasted Max Patch, click to expand. --

but I’m sure you already knew that

Jan 26 2010 | 10:08 am


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 | 2:37 pm

I think it’s because both’s inlets trigger it to output.

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

-- Pasted Max Patch, click to expand. --

Dec 31 2015 | 4:55 pm

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

Oct 16 2016 | 10:39 am

Dimitri – I have used your 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. :-)

Viewing 7 posts - 1 through 7 (of 7 total)

Forums > Max For Live