Hi,
I'd like to use the print function in Pd, in a batch process to create postscript files of an entire directory of patches.
I imagined a FUDI solution from a Bash script something like
pd -nogui & ..... start a pd instance for i in *.pd pdsend pd open $i pdsend pd print $i.ps ...etc
I'm not having much joy. My experience and knowledge of using FUDI communication is poor and I see a pitfall with passing an output filename to print.
Any thoughts most welcome, cheers,
Andy
I've been thinking that it would be very handy to be able to get the
complete contents of the Pd window in Pd space. Then you could parse
the error messages in Pd space and have your program respond. I
tried for a little bit to code it, but it was not as easily as it
seemed at first glance.
That's my two bits.
.hc
On Apr 27, 2007, at 6:56 AM, Andy Farnell wrote:
Hi,
I'd like to use the print function in Pd, in a batch process to create postscript files of an entire directory of patches.
I imagined a FUDI solution from a Bash script something like
pd -nogui & ..... start a pd instance for i in *.pd pdsend pd open $i pdsend pd print $i.ps ...etc
I'm not having much joy. My experience and knowledge of using FUDI communication is poor and I see a pitfall with passing an output filename to print.
Any thoughts most welcome, cheers,
Andy
-- Use the source
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
Access to computers should be unlimited and total. - the hacker ethic
Hans-Christoph Steiner wrote:
I've been thinking that it would be very handy to be able to get the
complete contents of the Pd window in Pd space. Then you could parse
the error messages in Pd space and have your program respond. I
tried for a little bit to code it, but it was not as easily as it
seemed at first glance.
i think i (and others) have posted several solutions to this in the past.
however, i think that padawan's question was more into the direction of how to control pd (itself) from outside, which would not involve such feedback-like stuff.
so:
- in order to make printing patches work, the first important thing is,
that you must not disable the gui. after all it is tcl/tk that does the patch-to-postscript conversion; when you turn it off, you also turn this feature of pd off.
- in order to send something to pd via pdsend, you cannot use a syntax
like
pdsend pd open $i
because this is not how this applications works. "man pdsend" will reveil that you should do something like:
echo "pd open $i;" | pdsend 4321
- you cannot directly control the pd process via pdsend.
pdsend is the command-line version of [netsend], so you can do no more (and no less) with it than with this object: you will need a [netreceive] object in the running instance of pd which will receive the messages sent via pdsend. if you want to control the pd-server, you will have to send the messages received at the [netreceive] via pd's messaging system to the server. (with [send pd])
so basically you will have to start a server pd-patch on your running pd that does the interfacing to the pdsend. the simplest version of this patch would be something like:
[netreceive 4321] | [s pd]
- "pd open $i" is not a valid message to open a file.
mfg.asdr IOhannes
Hallo, Andy Farnell hat gesagt: // Andy Farnell wrote:
I'd like to use the print function in Pd, in a batch process to create postscript files of an entire directory of patches.
I imagined a FUDI solution from a Bash script something like
pd -nogui & ..... start a pd instance
Did you try without "-nogui"?
for i in *.pd pdsend pd open $i pdsend pd print $i.ps ...etc
Ciao
Frank Barknecht _ ______footils.org_ __goto10.org__
On 27 Apr 2007, at 8:56 PM, Andy Farnell wrote:
pdsend pd print $i.ps
pdsend will need a port number, and you will need a [netreceive] in
your pd patches, also note that [netreceive] does not send into the
general message space, you will have to parse its output and connect
to a [send] object (or set it to work 'old' style, which is quite
insecure). See man pdsend and the help for netreceive.
Finally you will need to send the appropriate message, ending with a
';' eg:
echo "print name.ps;" | pdsend 3000
I could send some examples if you want
simon
-
Andy Farnell -
Frank Barknecht -
Hans-Christoph Steiner -
IOhannes m zmoelnig -
simon wise -
Steffen