[OSC_dev] bidirectional udp, was: Re: oscit registration complete !

[salsaman at xs4all.nl]

On Thu, January 29, 2009 00:04, Gaspard Bucher wrote:
> Thanks for the link. Good to know bidirectional OSC is available to
> max/msp. This also means that the "/.reply_to" is no longer needed.
>
> Please tell me if there are any other reasons to keep "/.reply_to" or
> I will remove it from oscit's draft.
>
> What about observers (something that needs to get notified when a
> value changes so the slider is kept in sync for example) ?
>
> Should an observer receive all return values => observe everything ?
>
> Should it only observe a list of urls ?
>
> Gaspard

The way I had envisaged this for LiVES is that an observer gets everything
by default, but it is possible to turn off certain notifications using
some kind of bitmask. Thus the host would maintain a matrix of notify
addresses versus events to notify.

So for example:

/notify_to [host] port [bitmask]

However, the problem is, what do these events represent ? For example, in
LiVES there are enumerated events like "video frame synch", "new clip
available", "clip closed" and "application exit". One solution might be to
create a common list (enumeration) of events. Also, with many event types,
the length of the bitmask to block events becomes increasingly silly.


Salsaman.
http://lives.sourceforge.net