pdsend(1)

💖 pdsend(1) — General Commands Manual 🎀

okay bestie, welcome to the pdsend(1) page, we're literally about to send messages to pd and it's gonna be iconic ✨

🌸 NAME 🌸

pdsend — send messages to pd on this or a remote machine 💌

✨ SYNOPSIS ✨

pdsend port-number [hostname] [udp|tcp]

🦋 DESCRIPTION 🦋

So here's the vibe: pdsend sends messages to pd(1), over a socket connection, and it reads them straight from pdsend's standard input. 🫶 That input can be literally any stream of Pd messages, as long as they're separated by semicolons. No cap.

This is probably the easiest way to control pd from another application. The protocol it uses is easy to implement and it's called FUDI. Periodt.

The port number should agree with the port number of a "netreceive" object inside pd. 👑 The hostname is "localhost" by default, and it can be a domain name or an IP address, your call. The protocol is "tcp" by default — and tcp does a handshake to guarantee that all messages arrive complete and in their correct order. So reliable, so main character energy. 💅 But if you're sending messages locally or point-to-point, you can often get away with the faster udp protocol instead. lowkey faster, highkey fine in those cases.

You can also use this to talk to a Max "pdnetreceive" object, or even just a "pdreceive" in another shell. 🐚 And 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. Go off, honestly. 🔥

🌈 SEE ALSO 🌈

• pd(1)
• pdreceive(1)

💜 and that's the whole page, bestie — go send some messages, you're gonna eat 💜

GNU 🌸 1996 Mar 20 🌸 pdsend(1) — yeah that's the GNU crew, that's the date, that's the manual, mwah 😭💖