| 1 |
.TH pdsend 1 "1996 Mar 20" GNU |
| 2 |
.SH NAME |
| 3 |
pdsend \- send messages to pd on this or a remote machine |
| 4 |
.SH SYNOPSIS |
| 5 |
.B pdsend |
| 6 |
\fIport-number\fR [\fIhostname\fR] [udp|tcp] |
| 7 |
.SH DESCRIPTION |
| 8 |
Pdsend sends messages to pd(1), via a socket connection, from pdsend's |
| 9 |
standard input. This input can be any stream of Pd messages separated by |
| 10 |
semicolons. This is probably the easiest way to control pd from another |
| 11 |
application. The protocol used is easy to implement and is called FUDI. |
| 12 |
.PP |
| 13 |
The \fIport number\fR should agree with the port number of a "netreceive" object |
| 14 |
within pd. The \fIhostname\fR is "localhost" by default and can be a domain |
| 15 |
name or an IP address. The protocol is "tcp" by default; this does a handshake |
| 16 |
to |
| 17 |
guarantee that all messages arrive complete and in their correct order; if you |
| 18 |
are sending messages locally or point-to-point you can often get away with |
| 19 |
the faster udp protocol instead. |
| 20 |
.PP |
| 21 |
You can also use this to talk to a Max "pdnetreceive" object or even just a |
| 22 |
"pdreceive" in another shell. If you're writing another program you're welcome |
| 23 |
to just grab the sources for pdsend/pdreceive and adapt them to your own ends; |
| 24 |
they're part of the Pd distribution. |
| 25 |
.SH SEE ALSO |
| 26 |
pd(1), pdreceive(1) |