13 messages in at.iem.pd-listRe: [PD] pd window messages| From | Sent On | Attachments |
|---|---|---|
| Andrew Cole | Apr 27, 2006 1:20 pm | |
| IOhannes m zmoelnig | Apr 28, 2006 12:17 am | |
| Hans-Christoph Steiner | Apr 28, 2006 2:36 am | |
| Piotr Majdak | Apr 28, 2006 2:47 am | |
| Hans-Christoph Steiner | Apr 28, 2006 2:57 am | |
| IOhannes m zmoelnig | Apr 28, 2006 3:00 am | |
| Hans-Christoph Steiner | Apr 28, 2006 3:32 am | |
| Chuckk Hubbard | Apr 28, 2006 5:37 am | |
| s.koepf | Apr 28, 2006 7:32 am | |
| day 5 | Apr 28, 2006 11:49 am | |
| João Miguel Pais | Apr 29, 2006 7:02 am | |
| Mathieu Bouchard | Apr 29, 2006 12:46 pm | |
| day 5 | Apr 29, 2006 6:36 pm |
| Subject: | Re: [PD] pd window messages | |
|---|---|---|
| From: | Hans-Christoph Steiner (ha...@eds.org) | |
| Date: | Apr 28, 2006 2:36:50 am | |
| List: | at.iem.pd-list | |
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