Hi, Does anyone know of a way to grab messages that are printed to the PD window, for example if a sound file has a bad header or an object fails to load? Thanks, -Andrew
Andrew Cole wrote:
Hi, Does anyone know of a way to grab messages that are printed to the PD window, for example if a sound file has a bad header or an object fails to load?
use "-stderr" to dump them to the standard error, then redirect the stderr to stdout then pipe it to whereever you want.
i admit that this is not really trivial. this should give you a start:
pd -stderr -verbose 2>&1 | while read line do echo "${line};" | pdsend 6666 localhost udp done
you can then fetch everything that is printed via a udp-listener on port 6666, either via pdreceive (which might be kind of pointless in this case) or via [netreceive] in either a separate pd-task or in the very same pd-task; be aware of feedbacks then! and of course you have no console any more...
mfg.adr. IOhannes
On Apr 28, 2006, at 9:18 AM, IOhannes m zmoelnig wrote:
Andrew Cole wrote:
Hi, Does anyone know of a way to grab messages that are printed to the PD window, for example if a sound file has a bad header or an object
fails to load?use "-stderr" to dump them to the standard error, then redirect the stderr to stdout then pipe it to whereever you want.
i admit that this is not really trivial. this should give you a start:
pd -stderr -verbose 2>&1 | while read line do echo "${line};" | pdsend 6666 localhost udp done
you can then fetch everything that is printed via a udp-listener on
port 6666, either via pdreceive (which might be kind of pointless in this case) or via [netreceive] in either a separate pd-task or in the very same pd-task; be aware of feedbacks then! and of course you have no console any more...
That would be a nice script to have in /scripts/ with a matching patch.
.hc
News is what people want to keep hidden and everything else is
publicity.
- Bill Moyers
Hans-Christoph Steiner wrote:
On Apr 28, 2006, at 9:18 AM, IOhannes m zmoelnig wrote:
Andrew Cole wrote:
Hi, Does anyone know of a way to grab messages that are printed to the PD window, for example if a sound file has a bad header or an object fails to load?
use "-stderr" to dump them to the standard error, then redirect the stderr to stdout then pipe it to whereever you want.
That would be a nice script to have in /scripts/ with a matching patch.
Do you guys have a independent solution? I'm interested in something for Windows...
br, Piotr
On Apr 28, 2006, at 11:47 AM, Piotr Majdak wrote:
Hans-Christoph Steiner wrote:
On Apr 28, 2006, at 9:18 AM, IOhannes m zmoelnig wrote:
Andrew Cole wrote:
Hi, Does anyone know of a way to grab messages that are printed to
the PD window, for example if a sound file has a bad header or an
object fails to load?use "-stderr" to dump them to the standard error, then redirect the stderr to stdout then pipe it to whereever you want.
That would be a nice script to have in /scripts/ with a matching
patch.Do you guys have a independent solution? I'm interested in
something for Windows...
Such scripts will run perfectly in Cygwin or MinGW on Windows.
.hc
I spent 33 years and four months in active military service and
during that period I spent most of my time as a high class muscle man
for Big Business, for Wall Street and the bankers.
- General Smedley Butler
Piotr Majdak wrote:
Do you guys have a independent solution? I'm interested in something for Windows...
well, afaik stderr redirection does work on linux; piping does too. the only thing which will most likely not work is the loop i am using. (note: the problem is, that for FUDI we need the trailing semicolon which involves some treatment of the strings output by pd; trivial as it is, this would need some w32 script kiddie to do, not me....)
an even better solution would be to additionally send all messages to a global receiver within pd. this way you could do
[r pd_console] | [route error verbose] | | | ... (this is for "post", [print])
mfg.asdr. IOhannes
On Apr 28, 2006, at 12:00 PM, IOhannes m zmoelnig wrote:
Piotr Majdak wrote:
Do you guys have a independent solution? I'm interested in
something for Windows...well, afaik stderr redirection does work on linux; piping does too. the only thing which will most likely not work is the loop i am using. (note: the problem is, that for FUDI we need the trailing semicolon which involves some treatment of the strings output by pd; trivial
as it is, this would need some w32 script kiddie to do, not me....)an even better solution would be to additionally send all messages
to a global receiver within pd. this way you could do[r pd_console] | [route error verbose] | | | ... (this is for "post", [print])
Yes, that would be very nice. I thought I made a feature request in
the tracker for this, I guess I just thought about it.
.hc
Using ReBirth is like trying to play an 808 with a long stick. -David Zicarelli
Piotr Majdak wrote:
Hans-Christoph Steiner wrote:
On Apr 28, 2006, at 9:18 AM, IOhannes m zmoelnig wrote:
Andrew Cole wrote:
Hi, Does anyone know of a way to grab messages that are printed to the PD window, for example if a sound file has a bad header or an object
fails to load?use "-stderr" to dump them to the standard error, then redirect the stderr to stdout then pipe it to whereever you want.
That would be a nice script to have in /scripts/ with a matching patch.
Do you guys have a independent solution? I'm interested in something for Windows...
pd -verbose -stderr 2>test.txt
does something like this on Windows.
Siegfried Koepf
in line with this thread i will pose question that I originally thought this thread would be about before reading it, based on the subject line alone.
does anyone know of a list of commands that are sent to Pd itself ?
The messages in this format, with the semicolon in and such.
[x]
| ;
| pd dsp $1 (
For example, are there methods for changing attributes of the Tcl/Tk interface ?
tia,
./d5
you can see that in /messages (?) somewhere in cvs, maybe in /doc. it was
also mentioned already several times around, see the archives. it doesn't
seem to be finished, but has many things. it depends what you want to do
with them.
you can also make the opposite: |r pd|, and watch the output.
Am 28.04.2006, 20:49 Uhr, schrieb day 5 day5ive@gmail.com:
in line with this thread i will pose question that I originally thought
this thread would be about before reading it, based on the subject line
alone.does anyone know of a list of commands that are sent to Pd itself ?
The messages in this format, with the semicolon in and such.
[x]
| ; | pd dsp $1 (For example, are there methods for changing attributes of the Tcl/Tk
interface ?
On Fri, 28 Apr 2006, day 5 wrote:
does anyone know of a list of commands that are sent to Pd itself ?
see pd/src/m_glob.c
For example, are there methods for changing attributes of the Tcl/Tk interface ?
No, for that you need to modify .c and/or .tk files.
(In DesireData you would instead go in "Client Preferences..." but eventually there might be a way to control both the Server Preferences (pdrc) and Client Preferences through ";pd" messages or similar.)
Currently, ";pd" messages don't allow configuring pd except in ways that were designed only for use by lib/pd/bin/pd.tk and so are quite difficult to use in any other way.
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801 - http://artengine.ca/matju | Freelance Digital Arts Engineer, Montréal QC Canada
On 4/28/06, IOhannes m zmoelnig zmoelnig@iem.at wrote:
Andrew Cole wrote:
Hi, Does anyone know of a way to grab messages that are printed to the PD window, for example if a sound file has a bad header or an object fails to load?
use "-stderr" to dump them to the standard error, then redirect the stderr to stdout then pipe it to whereever you want.
i admit that this is not really trivial. this should give you a start:
pd -stderr -verbose 2>&1 | while read line do echo "${line};" | pdsend 6666 localhost udp done
O_o
How much of this is through Pd, and where does the rest of it go?