[OSC_dev] oscit registration complete !

[Gaspard Bucher]

>>Because it doesn't work ! Most implementations of OSC I have
>>tried do not let you define the outgoing port when creating a
>>connection.
>
> Oh dear. Are you writing your own software? If so, then try my
> new EasyOSC lib. It saves the sender's address with every received
> UDP or TCP message. You don't even need to know what that
> address is. To reply to a message you receive, you just call the
> function OscReplyMsg, and EasyOSC takes care of sending it to
> the right device.

When I talk about "implementations" I don't mean "osc library", but
real world applications with OSC support that need to be supported one
way or the other (max/MSP for example). I haven't tested EasyOSC with
max/MSP though but I doubt it would work since "oscsend" and
"oscreceive" are two different and agnostic objects and you have *no*
way to define the outgoing port of an "udpsend" object.
>
> _______________________________________________
> OSC_dev mailing list
> OSC_dev at create.ucsb.edu
> http://lists.create.ucsb.edu/mailman/listinfo/osc_dev
>