Hi
Basic OSC confusion here: I'd like to run a server that keeps track of time and shares that to a number of clients, each of which run on their own, but with access to this common, global time.
However all the examples I found with [sendOSC] or [tcpsend] suggests that the sender connects to *one* client, which isn't what I want. I'd rather like to have the server broadcast to any number of clients that can pick up this information if they like.
Have I got OSC all wrong? How to best achieve what I need?
On 02.02.2014 17:37, Atte wrote:
Hi
Basic OSC confusion here: I'd like to run a server that keeps track of time and shares that to a number of clients, each of which run on their own, but with access to this common, global time.
However all the examples I found with [sendOSC] or [tcpsend] suggests that the sender connects to *one* client, which isn't what I want. I'd rather like to have the server broadcast to any number of clients that can pick up this information if they like.
Have I got OSC all wrong? How to best achieve what I need?
well, there's oscgroups: http://www.rossbencina.com/code/oscgroups
never used it, but should be able to help you out.
cheers, ub
You can broadcast over UDP by sending to the address 255.255.255.255.
Joel On Feb 2, 2014 10:57 AM, "Atte" atte@youmail.dk wrote:
Hi
Basic OSC confusion here: I'd like to run a server that keeps track of time and shares that to a number of clients, each of which run on their own, but with access to this common, global time.
However all the examples I found with [sendOSC] or [tcpsend] suggests that the sender connects to *one* client, which isn't what I want. I'd rather like to have the server broadcast to any number of clients that can pick up this information if they like.
Have I got OSC all wrong? How to best achieve what I need?
-- Atte
http://atte.dk http://modlys.dk
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
if you want to make one server talking to several clients, you could use [tcpserver]/[tcpclient] and encapsulate your OSC in Slip packet see [mrpeach] externals
a
-- do it yourself http://antoine.villeret.free.fr
2014-02-02 Joel Matthys jwmatthys@gmail.com:
You can broadcast over UDP by sending to the address 255.255.255.255.
Joel On Feb 2, 2014 10:57 AM, "Atte" atte@youmail.dk wrote:
Hi
Basic OSC confusion here: I'd like to run a server that keeps track of time and shares that to a number of clients, each of which run on their own, but with access to this common, global time.
However all the examples I found with [sendOSC] or [tcpsend] suggests that the sender connects to *one* client, which isn't what I want. I'd rather like to have the server broadcast to any number of clients that can pick up this information if they like.
Have I got OSC all wrong? How to best achieve what I need?
-- Atte
http://atte.dk http://modlys.dk
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On 2014-02-02 11:37, Atte wrote:
Hi
Basic OSC confusion here: I'd like to run a server that keeps track of time and shares that to a number of clients, each of which run on their own, but with access to this common, global time.
However all the examples I found with [sendOSC] or [tcpsend] suggests that the sender connects to *one* client, which isn't what I want. I'd rather like to have the server broadcast to any number of clients that can pick up this information if they like.
Have I got OSC all wrong? How to best achieve what I need?
It's not really OSC, more the transport layer. With [udpsend] you can broadcast or send to a multicast address (http://en.wikipedia.org/wiki/Multicast_address). Multicasting may be more efficient as it only sends to clients that connected to the multicast address. Broadcasts go to every machine on the subnet. Multicasting is usually more of a pain to get working.
Martin