1 Mar
2005
1 Mar
'05
9:20 a.m.
On Tue, Mar 01, 2005 at 01:27:38PM -0500, Dave Robillard wrote:
When a destination is added/removed, the patching
server will notify the
client (via OSC), and the client will update it's list of destinations
appropriately (this will all be abstracted by liblo's API though).
How would you handle SC3's way of doing things ?
When you create a new OSCResponder object in sclang, this does not
create a new port - it just adds a new 'accepted source' for messages
coming in at the one and unique sclang port (57120). OSCResponders are
created by specifying the source, not a local port.
Given this, the JACK / MIDI patchbay is not the correct model. For both
JACK and the ALSA sequencer, connecting multiple outputs to the same
input just adds / merges the signals coming from those outputs. This is
not the case for UDP: messages coming in from different sources remain
quite separate, and a client in effect never needs more than one input
port.
--
FA