[OSC_dev] oscit registration complete !

[Jeff Glatt]

>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).

Ok, I gather that you're writing your own app (which you want to
communicate with max/MSP), so whatever you come up with for
oscit _must_ work with max/MSP (as it exists today).

Got it.

>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

Ok, I'm not familiar with max/MSP specifically. (Sorry, not a Mac
guy. Linux and Windows here). But I gather that these are some
sort of "exposed software interfaces" that a separate app like yours
can "connect" to?

>you have *no* way to define the outgoing port of an "udpsend"
>object.

>From within max/MSP, I gather? But surely it must know what UDP
port to send a message to your app? How does it  determine what
UDP port you're using? It just can't pick its own, random number.

To get more familiar with what you're doing, I did a search for
"max/msp udpsend" and I came up with a URL to a message on
this very list:

http://opensoundcontrol.org/topic/222

In one of the replies someone mentions "enter IP and Port for your
udpsend object via Text/Number boxes with prepended host and port".
Are you sure what you want to do is not possible? Or is this
incorrect/outdated info?