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

[Gaspard Bucher]

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

On Wed, Jan 28, 2009 at 9:36 PM, Sciss <contact at sciss.de> wrote:
> Am 28.01.2009 um 19:13 schrieb Andy W. Schmeder:
>
>> On Jan 28, 2009, at 1:47 AM, Gaspard Bucher wrote:
>>
>>> But since max/MSP is so common in the field I'm working in (live
>>> performance art, installations), I have to live with what it does.
>>
>> There is a some chance that the functionality will be added to
>> udpsend/
>> udpreceive.  I've been complaining about it for a long time...  there
>> is no technical reason it can't be done.
>>
>> Someone at CNMAT has a connection with Cycling that includes access to
>> source code of some objects--this is one of them.  It is possible that
>> it gets fixed and even merged into the mainstream max distribution.
>> Even more likely if other OSC libraries and applications also start
>> supporting bidirectional UDP (many still do not).
>>
>> Also max comes with some fairly competent networking objects written
>> in java--including the source code: net.udp.recv, net.udp.send.  What
>> is needed is net.udp.recvfrom and net.udp.sendto.
>
> check this out
>
> http://maxobjects.com/?v=objects&id_objet=3733
>
> _______________________________________________
> OSC_dev mailing list
> OSC_dev at create.ucsb.edu
> http://lists.create.ucsb.edu/mailman/listinfo/osc_dev
>