chapelier fou

I'm working on a project where I use note data from many tracks to trigger lights/video cues via OSC. 

I'm currently using a small device (attached) in almost EACH track (it will be roughly 40 in the end). Each [udpsend] will connect to the same IP and also the same port. 

Would you rather advice to use only one [udpsend] in a "master" device that would gather all messages (using sends and receive) ?

CF_OSC_Notes.amxd

I'm working on a project where I use note data from many tracks to trigger lights/video cues via OSC. 
I'm currently using a small device (attached) in almost EACH track (it will be roughly 40 in the end). Each [udpsend] will connect to the same IP and also the same port. 
I have a bad feeling about it. 
Would you rather advice to use only one [udpsend] in a "master" device that would gather all messages (using sends and receive) ?

I'm working on a project where I use note data from many tracks to trigger lights/video cues via OSC. 
I'm currently using a small device (a

many-udpsend-object-versus-one

But I think the more important factor is to try to make osc messages as short as possible

only when values change, avoiding repetitions.

A short test with 100 udpsend objects works well,

but that is in Max, don't know anything about Live and if it would

Screen Shot 2021-05-14 at 13.51.04.png

I can't really answer your question.
But I think the more important factor is to try to make osc messages as short as possible
and to take care that messages get sent
only when values change, avoiding repetitions.
A short test with 100 udpsend objects works well,
but that is in Max, don't know anything about Live and if it would
behave, or cause problems.


Thanks for the test. I'm sure Max itself would initialize all udpsend correctly. But in M4L, not sure how funky it can go when connecting to the same port from multiple sources...

The reason is I encountered some weirdness in the past with udpsend/receive in M4L, with unresponsive ports even after a reboot, and never got the last word about it, so I wondered if someone knew something about it.

Also, it works currently fine, but I'm working currently on several pieces, that I will gather in one big live set, once they are all ready.

The reason is I encountered some weirdness in the past with udpsend/receive in M4L, with unresponsive ports even after a reboot, and never got the last word about it, so I wondered if someone knew something about it.
Also, it works currently fine, but I'm working currently  on several pieces, that I will gather in one big live set, once they are all ready.

I think that only *udpreceive* is problematic with M4L because switching between edit and performance mode may lead to a binding conflict between Live and Max. In contrast, with *udpsend* there is no such binding and so it should work in M4L just like in Max.

Thank you very much. That could explain what I encountered earlier, and it should then be ok to use multiple udpsend.[]

Many udpsend object versus one