On Tue, 2005-01-03 at 11:26 +0100, Frank Barknecht wrote:
Hallo,
Dave Robillard hat gesagt: // Dave Robillard wrote:
The nice thing about this system (thanks largely
to Steve) is that it
will also work with non-liblo clients, and so could become an OSC
'standard' if it catches on. At the very least it will promote OSC to
the same level of modularity that MIDI and Jack have, as far as linux
audio systems are concerned. Plus, since everything is network
transparent, programs run on other machines on the network will
automatically register their (er) "ports", so could magically appear in
other machine's patch bays - very cool.
I wonder how to handle broadcast OSC messages in that context? They
are an important possibility in OSC when playing together with lots of
machine: One is sending to 192.168.0.255:xxxx and everyone receives
data there.
Ciao
Nothing at all forces a client to use the thing - that's very important!
Whatever works now will always work, this stuff is 100% optional in
every way - liblo clients can, of course, still send and receive to
whatever address they please.
But anyway, the patch bay app I envision will allow setting arbitrary
addresses without needing an application to claim them anyway. Picture
an "add port" button in osc-patch-bay that allows you to type in an
arbitrary address to define a 'destination' - normal, broadcast,
whatever.
-DR-