So to send messages to a [receive my_msgs] you would run this from the

command line:

pdsend 4444 "my_msgs hello world;"

this is actually not working ... pdsend reads from stdin ... i don't think this is very useful, expecially if you want to do write some shell scripts ... i'll try to edit the pdsend to be used like: pd <portnumber> [host] [udp|tcp] "msg_to_pd;"

cheers...

Tim mailto:TimBlechmann@gmx.de ICQ: 96771783 -- The only people for me are the mad ones, the ones who are mad to live, mad to talk, mad to be saved, desirous of everything at the same time, the ones who never yawn or say a commonplace thing, but burn, burn, burn, like fabulous yellow roman candles exploding like spiders across the stars and in the middle you see the blue centerlight pop and everybody goes "Awww!" Jack Kerouac

On Thu, 1 Apr 2004, Frank Barknecht wrote:

Tim Blechmann hat gesagt: // Tim Blechmann wrote:

...

...

pdsend 4444 "my_msgs hello world;"

this is actually not working ... pdsend reads from stdin ... i don't think this is very useful, expecially if you want to do write some shell scripts ...

Connecting to Pd is a simple socket-connection, for which you even could use something like netcat, so I'd see not much use in changing pdsend just to make scripting easier.

I don't understand; is there a problem or some difficulty with the following command?

echo my_msgs hello world ; | pdsend 4444

or is there with the following one?

pdsend 4444 <<EOF my_msgs hello world ; my_msgs hello world take deux ; my_msgs hello world again ; EOF

or my favourite:

( echo my_msgs hello world ; echo my_msgs hello world take deux ; echo my_msgs hello world again ; ) | pdsend 4444

Mathieu Bouchard http://artengine.ca/matju

morning everyone,

On 1 April 2004 at 12:18:36, Frank Barknecht wrote:

Mathieu Bouchard hat gesagt: // Mathieu Bouchard wrote:

...

On Thu, 1 Apr 2004, Frank Barknecht wrote:

...

Tim Blechmann hat gesagt: // Tim Blechmann wrote:

...

...

pdsend 4444 "my_msgs hello world;"

I don't understand; is there a problem or some difficulty with the following command?

Not at all, IMO. Of course, it often is nice to be able to do a bit more structured (network) programing, for which I'd prefer something like Python anyway.

... if anyone's interested, i just uploaded some oo perl wrappers for communication via netsend/netreceive -- udp send isn't working, but it's another possibility...

http://www.ling.uni-potsdam.de/~moocow/projects/pd/Pd-Socket-0.01.tar.gz

marmosets, Bryan

Hallo, Mathieu Bouchard hat gesagt: // Mathieu Bouchard wrote:

If anyone's interested, I just wrote a Ruby wrapper for communication via netsend and

ruby -rsocket -e'TCPSocket.open("localhost",4444){|s|s.print ARGV[0]}'

it's shorter than the URL for the Perl wrapper.

Okay, attached is my quick hack Python PdSender-object/script. Either call it directly for a nice command line interface to with history (if readline is available) or use it in a Python script like:

# --- from pdsender import PdSender pd = PdSender( "localhost", 3000 ) pd.send("something was sent;") # ---

It could be much shorter, probably as short as the Ruby example, if I didn't go for a bit of comfort with readline support and a nicer prompt.

ciao

Frank Barknecht _ ______footils.org__

Btw where do I download pdsender.py from ?

It was an attachment to Frank's mail.

best, Thomas

I don't understand; is there a problem or some difficulty with the following command?

echo my_msgs hello world ; | pdsend 4444

well, ... i already wrote a small patch and commited it to the cvs ... maybe a bit to fast ... if you want, i can remove it again ...

cheers...

Tim mailto:TimBlechmann@gmx.de ICQ: 96771783 -- The only people for me are the mad ones, the ones who are mad to live, mad to talk, mad to be saved, desirous of everything at the same time, the ones who never yawn or say a commonplace thing, but burn, burn, burn, like fabulous yellow roman candles exploding like spiders across the stars and in the middle you see the blue centerlight pop and everybody goes "Awww!" Jack Kerouac

I didn't look at it yet, but I think it's better to remove it, if it introduces incompatibilities which aren't good here (because they might break others' shell scripts)

it's not breaking anything, but it's simply unnecessary ...

i've removed it ... sorry for all this useless traffic.

cheers...

Tim mailto:TimBlechmann@gmx.de ICQ: 96771783 -- The only people for me are the mad ones, the ones who are mad to live, mad to talk, mad to be saved, desirous of everything at the same time, the ones who never yawn or say a commonplace thing, but burn, burn, burn, like fabulous yellow roman candles exploding like spiders across the stars and in the middle you see the blue centerlight pop and everybody goes "Awww!" Jack Kerouac

hi all,

i added a small feature to pdsend so that we can write shell scripts more easily:

pd <portnumber> [host] [udp|tcp] ["message;"] (before: pd <portnumber> [host] [udp|tcp])

if no message is given, it reads from stdin as before (note that you'll have to add a hostname and protocol to be able to write a message ... if not, it's looking for the corresponding hostname) ...

i hope, i'm not the only one who benefits from this feature ... cheers...

Tim mailto:TimBlechmann@gmx.de ICQ: 96771783 -- The only people for me are the mad ones, the ones who are mad to live, mad to talk, mad to be saved, desirous of everything at the same time, the ones who never yawn or say a commonplace thing, but burn, burn, burn, like fabulous yellow roman candles exploding like spiders across the stars and in the middle you see the blue centerlight pop and everybody goes "Awww!" Jack Kerouac