[PD] port used by sendOSC

[Axel Balley]

Le 17 déc. 05 à 12:05, Frank Barknecht a écrit :

>
>
> [sendOSC] itself is not using a "local port" or source port, it just
> connects to the remote host's destination port, sends its messages,
> but doesn't read anything back. That's the job of [dumpOSC].
>

AFAIK, any transmission of data between a client and server implies  
the use of 2 ports : one on the client side (in that case, the  
sendOSC object in pd), and one on the server side (here, the 57110  
port SC3 listens to). That's why I wanted to know if there was a way  
to display which port was used by the sendOSC to connect to SC3. I  
actually found that port number using the netstat command, however I  
couldn't create a dumpOSC object to listen on it : probably because  
it's already used by the sendOSC object so a new socket cannot be  
created.

> SC3 automatically uses a specific port, but Pd doesn't. Note that for
> OSC using the UDP protocol, you can only run one application on one
> machine's port. So if you run SC3 on port 57110, you will not be able
> to create a [dumpOSC 57110] in Pd anymore, as that port, 57110,
> already is taken by Supercollider. Instead you'll get a 'Address
> already in use' error or something like that. Of course you can create
> [connect localhost 57110( --- [sendOSC] chains, but you already did
> that.

Yes, I'm aware of that. Besides, there's no point in using the  
dumpOSC object on the 57110 port when SC3 is running, since there  
exists a way to display incoming OSC messages in SuperCollider.