[PD-cvs] pd/man pd.1, NONE, 1.1.1.1.26.2 pdreceive.1, NONE, 1.1.1.1.26.2 pdsend.1, NONE, 1.1.1.1.26.2

[Tim Blechmann]

Update of /cvsroot/pure-data/pd/man
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv3567

Added Files:
      Tag: devel_0_39
	pd.1 pdreceive.1 pdsend.1 
Log Message:
man

--- NEW FILE: pd.1 ---
.TH pd 1 "1996 Mar 20" GNU
.SH NAME
pd \- pure data
.SH DESCRIPTION
Pd is a graphical programming environment for real-time audio synthesis
and related applications.  It sports a rich set of real-time control
and I/O features.
.PP
To get a list of allowable arguments to pd, type
.IP
.B pd -help
.PP
and for more documentation either start pd and get help, or consult
.PP
.B http://www.crca.ucsd.edu/~msp/Pd_documentation/index.htm
.PP
or seek a copy on your own machine, perhaps in
.PP
.B file:/usr/local/bin/pd/doc/1.manual/index.htm
.PP
or
.PP
.B file:/usr/bin/pd/doc/1.manual/index.htm
.SH SEE ALSO
pdsend(1), pdreceive(1)

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

--- NEW FILE: pdreceive.1 ---
.TH pdreceive 1 "1996 Mar 20" GNU
.SH NAME
pdreceive \- receive messages from pd on this or a remote machine
.SH SYNOPSIS
.B pdreceive
\fIport-number\fR [udp|tcp]
.SH DESCRIPTION
Pdreceive opens a socket (with the specified port number) and
waits for messages to arrive from one or more instances of pd(1).  Each
message received is printed to the standard output with a trailing semicolon. 
The protocol used is easy to implement and is called FUDI.
.PP
The \fIport number\fR should agree with the port number of a "netsend" object
within pd.  The protocol is "tcp" by default; this does a handshake
to
guarantee that all messages arrive complete and in their correct order; if you
are sending messages locally or point-to-point you can often get away with
the faster udp protocol instead.
.PP
You can also use this to get messages from a Max "pdnetsend" object or even
just a
"pdsend" in another shell.  If you're writing another program you're welcome
to just grab the sources for pdsend/pdreceive and adapt them to your own ends;
they're part of the Pd distribution.
.SH SEE ALSO
pd(1), pdsend(1)