[OSC_dev] SYNoscopy (or something like it)

[werteplus at gmail.com]

>
> From: "Jeff Glatt" <jgglatt at roadrunner.com>
>
> >a synthesizer hosting program has one osc-listening port open and does
> >the routing to the hosted destination IDs
>
> Ok, so it _is_ a very basic "routing number".
>
> I still don't know why you need this ID number. All you need is the
> hostname
> and port number of each connected device. If some "hosting program" wants
> to route messages between devices, all it needs to know are those two
> pieces
> of info about each device. And of course, it must already have that info if
> the
> software is communicating with those devices individually.
>
> So what's the extra ID for?
>

ok, it's not really necessary. the host could offer some ports and route the
data from this port to any synth.

i read through your spec. why are you then using "musician numbers" at all?
you could keep consistent and have a dedicated port for every musician.

please don't just use just Hz for notes. i really beg you to not make this
mistake. make it possible to additionally be able to either use cent or a
ratio (see scala .scl tuning standard) + a base frequency for the whole
musician/synth.

btw, how does your tuning for the middle A work if you send frequencies?

and what about other initial parameters than velocity? when you e.g. look at
FL Studio, a note can also have additionally a x- and y-value (which can be
mapped to anythig by internal synths as Sytrus).

i find it a bit strange that every note can only have a limited + named set
of parameters (cutoff, resonance, lfo...). it could eg have 20 filters where
i would want to set cutoff-frequency, type, etc for every filter. or just a
20 band eq.

other than that: thanks for reusing some of my thoughts, i'm glad my
research didn't die alone in the cold!

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