I think I needed dinner -
wait isn't mean what I thought it was,
don't know why it worked
but it seems to work ok without it - and I worked out how to close
the patch
attached are better examples
simon
On 29 Apr 2007, at 10:04 PM, simon wise wrote:
On 29 Apr 2007, at 3:48 AM, Frank
Hallo,
simon wise hat gesagt: // simon wise wrote:
same here - possibly the patch gets printed before it is drawn??
Probably.
with the 'wait' these work for me - with printer.pd already open in
pd, try:
pdprint2.sh name /path/to/directory
I now made a little abstraction for printing.
yeh - it makes more sense to do it as a patch, I wanted to follow up
Andy's ideas, and wanted to test that message path - perhaps he has a
larger context where a bash script is more appropriate? but you
probably wouldn't want to use the 'old' option in [netreceive] anyway.
simon
On 30 Apr
Nice. Thanks for playing with this.
I dug myself into a terrible pit with this last night.
To be honest there are still subtle things I really don't understand.
I tried putting sleep commands in a perl script because
I guessed it was a print before draw type problem, but I got into
a mess with
I'm gonna try Franks method too in a moment. What I ran
up against last night was this:
I have rather a large directory of pd file to print.
A method that loads Pd anew for each patch takes a long time.
And I still had the problem of closing each instance. I was going
to fork, get a PID and
Seems to do what I want now.
One argument, the directory of the Pd files.
It incorporates awk script inline to correct
the font problems and slows it down enough
to be okay even for large Pd files, but still
fast enough.
Thanks all for help with this.
On Sun, 29 Apr 2007 23:40:42 +1000
simon
those are the Mac layout versions - you'll need to move things around
a bit for Linux, I've got those layouts as well - all the work on
trying to get the same font/layout working across platforms is VERY
appreciated - I look forward to the day I don't have to keep 2
versions of everything
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]
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
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
On 27/04/2007, at 2.15, Hans-Christoph Steiner wrote:
the complete contents of the Pd window
My experience is, that only the visible part of the patch window will
be printed (to postscript). That is, not the part, if any, that is
not visible in the patch window.
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'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
13 matches
Mail list logo
