Re: gephex-0.5: OSC and link serialization

> Starting point was the observation that we wanted to build OSC support
> into the core of gephex-0.5. The most basic and at the same time most
> important
> use of OSC we could think of was support to change inputs of effects via
> OSC
> (e.g. control a xfader).

The other direction, sending OSC messages with the value of some link,
is also important. With bidirectional support for OSC it is quite simple
to develop new software or hardware user interfaces.

> So the idea to solve this is:
>
>   1/ define standard serialisations of all used types to OSC
>
>   2/ define a standard mapping between these OSC formats and s-expressions
>      (for the command line we think this is a good format, e.g. a color
>       could be represented as (color <r> <g> <b>))
>
>   3/ remove the serialise and deserialise method form the link interface

With change 3. the only way to change or read the value of a effect
parameter is to receive or send an OSC message.

>   4/ add "creator" units which accept OSC input and initialise a link with
>      this serialised value

Inputs:
-osc stream
-osc address
-old value

Output:
-new value

Behavior:
If there is no osc message in the stream with the specified osc address
new value=old value otherwise the value from the message is the new
output value.

Usage:
old value and new value is connected to the same link.

Martin

_______________________________________________
gephex-devel mailing list
[email protected]
http://lists.gephex.org/mailman/listinfo/gephex-devel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFCIHnECm3i57PRsbsRApzuAKCRNW1vtDec9QWLWBYTo88rDk3s9ACgx17b
zhVL5E0yj1EX9GbM6yQnTyQ=
=2wgt
-----END PGP SIGNATURE-----