[OSC_dev] SYNoscopy (or something like it)

[werteplus at gmail.com]

>
> Date: Wed, 28 Jan 2009 01:18:16 -0500
> From: "Jeff Glatt" <jgglatt at roadrunner.com>
>
> I've looked at the SYNoscopy specification, and here's the first
> thing that puzzled me.
>
> Does the spec assume that every synth (ie, sound module, device,
> whatever) is "listening" to _every_ OSC message sent from any
> given device, much like daisy-chained MIDI devices? In other words,
> SYNoscopy assumes that there is one "bus", without any means of
> data routing in the "bus transport" itself, just like daisy-chained
> MIDI? And that's the reason why each synth must have a unique ID
> number? It's a very basic "routing number" built into the spec
> itself?
>

good thoughts. the answer is no.
the (to discuss) reason for this was that it would be possible in this way
that a synthesizer hosting program has one osc-listening port open and does
the routing to the hosted destination IDs=synths (that are not all in the
network!). otherwise when you play with your external osc keyboard, and want
to control a different synth, you have to change that on the keyboard, and
it's not direct possible from the synthesizer hosting program.

IDs would only have to be unique within the host, so no broadcasting.

greetings,
fabb
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.create.ucsb.edu/pipermail/osc_dev/attachments/20090128/7268b1dd/attachment-0001.html