Hi,
I have installed Arch linux on my Raspberry Pi and am logging in with ssh -Y raspberrypi.local. I can run xterm fine over the connection but pd fails with no information other than:
$ pd priority 6 scheduling enabled. priority 8 scheduling enabled. watchdog: signaling pd... pd: exiting
If I set the debug level to 5 I get the following information:
$ pd -d 5 set pd_whichmidiapi 2 priority 6 scheduling enabled. priority 8 scheduling enabled. pdtk_watchdog set ::tmp_path {} set ::sys_searchpath $::tmp_path set ::tmp_path {} lappend ::tmp_path {/home/james/pd-externals} lappend ::tmp_path {/usr/local/lib/pd-externals} lappend ::tmp_path {/usr/lib/pd/extra} set ::sys_staticpath $::tmp_path set ::startup_flags {} set ::startup_libraries {} pdtk_pd_startup 0 43 4 {} { {OSS 2} {ALSA 1} {jack 5} } { {default-MIDI 2} {ALSA-MIDI 1} } {DejaVu Sans Mono} bold set pd_whichmidiapi 2 pd: exiting
Any ideas why pd can't run over the ssh connection? It runs fine with the -nogui option.
James
On 05/26/2013 05:05 PM, James Dunn wrote:
Hi,
I have installed Arch linux on my Raspberry Pi and am logging in with ssh -Y raspberrypi.local. I can run xterm fine over the connection but pd fails with no information other than:
$ pd priority 6 scheduling enabled. priority 8 scheduling enabled. watchdog: signaling pd... pd: exiting
If I set the debug level to 5 I get the following information:
$ pd -d 5
this is of not much use unless you want to debug the pd<->gui connection.
try instead: "-v" (for verbose) "-v -v" (for more verbosity)
other flags you might want to check (in any combination) "-nogui" (see whether Pd can start without the gui) "-nosound" (does the sound-card give you trouble?) "-noprefs" (stupid preference file?)
my bet is, that your soundcard is the culprit, e.g. Pd doesn't handle the case well, where you only have half-duplex (e.g. playback only) and your are using alsa. if that's the case ("-nosound" should run ok), try "-noadc" or "-nodac" (without the "-nosound"))
famsdr IOhannes
Quoth IOhannes zmölnig, on 26/05/2013 16:16:
try instead: "-v" (for verbose) "-v -v" (for more verbosity)
The pd -v, or -v -v options don't work, it justs prints out the valid options, ie:
usage: pd [-flags] [file]...
audio configuration flags: -r <n> -- specify sample rate -audioindev ...
etc..
"-nogui" (see whether Pd can start without the gui) "-nosound" (does the sound-card give you trouble?) "-noprefs" (stupid preference file?)
As mentioned previously, pd runs fine with -nogui. I made a patch on another machine, then opened it on the RPi. The patch sends a message via netsend to pdreceive (both on the pi) and it works fine when run as -nogui. None of the audio options make any difference (-noaudio, -nosound, -noadc, -nodac, -nomidi) and -noprefs has no effect either.
I made another patch to loadbang a sound out of the pi in -nogui but that didn't work.
Strange that xterm works but pd doesn't - I have quite a minimal arch install so maybe some other X packages are needed for tcl/tk/wish, etc?
On 05/26/2013 05:42 PM, James Dunn wrote:
Quoth IOhannes zmölnig, on 26/05/2013 16:16:
try instead: "-v" (for verbose) "-v -v" (for more verbosity)
The pd -v, or -v -v options don't work, it justs prints out the valid options, ie:
usage: pd [-flags] [file]...
audio configuration flags: -r <n> -- specify sample rate -audioindev ...
etc..
when reading on, you might also come across: -verbose -- extra printout on startup...
so indeed, it's "-verbose" and "-verbose -verbose" (instead of "-v")
As mentioned previously, pd runs fine with -nogui. I made a patch on
i missed that info in your original mail (please don't require anyone willing to answer to have read all your emails to this list and remember them :-))
another machine, then opened it on the RPi. The patch sends a message via netsend to pdreceive (both on the pi) and it works fine when run as -nogui. None of the audio options make any difference (-noaudio, -nosound, -noadc, -nodac, -nomidi) and -noprefs has no effect either.
I made another patch to loadbang a sound out of the pi in -nogui but that didn't work.
check the various posts on this list about why [loadbang]->[; pd dsp 1( often does not work. a simple workaround is to introduce a [delay 1000] to start dsp only after some "boot time".
Strange that xterm works but pd doesn't - I have quite a minimal arch install so maybe some other X packages are needed for tcl/tk/wish, etc?
can you run $ wish via the ssh connection?
if so, Pd should be able to run fine. which version of tcl/tk do you have installed?
you could also try to run Pd without realtime priviliges $ pd -nrt
fgm,asdr IOhannes
Quoth IOhannes zmölnig, on 26/05/2013 17:07:
so indeed, it's "-verbose" and "-verbose -verbose" (instead of "-v")
$ pd -verbose Pd-0.43.4 ("") compiled 22:56:34 Aug 6 2012 port 5400 TCL_LIBRARY="/usr/lib/pd/lib/tcl/library" TK_LIBRARY="/usr/lib/pd/lib/tk/library" wish "/usr/lib/pd/tcl//pd-gui.tcl" 5400 priority 6 scheduling enabled. Waiting for connection request... priority 8 scheduling enabled. /usr/lib/pd/bin/pd-watchdog ... connected pd: exiting
i missed that info in your original mail (please don't require anyone willing to answer to have read all your emails to this list and remember them :-))
sorry, thanks for your help so far!
check the various posts on this list about why [loadbang]->[; pd dsp 1( often does not work. a simple workaround is to introduce a [delay 1000] to start dsp only after some "boot time".
I'd forgotten about the [delay] for [loadbang] when turning the dsp on but it doesn't result in any sound when running in -nogui.
can you run $ wish via the ssh connection?
Yes, it opens a blank window on the local machine.
if so, Pd should be able to run fine. which version of tcl/tk do you have installed?
tk-8.6.0-1 tcl-8.6.0-4
you could also try to run Pd without realtime priviliges $ pd -nrt
I tried that but it didn't help either.
For the archives, I've solved the issue - it seemed I just needed to install the package xf86-video-fbdev.
Quoth James Dunn, on 26/05/2013 18:06:
Quoth IOhannes zmölnig, on 26/05/2013 17:07:
so indeed, it's "-verbose" and "-verbose -verbose" (instead of "-v")
$ pd -verbose Pd-0.43.4 ("") compiled 22:56:34 Aug 6 2012 port 5400 TCL_LIBRARY="/usr/lib/pd/lib/tcl/library" TK_LIBRARY="/usr/lib/pd/lib/tk/library" wish "/usr/lib/pd/tcl//pd-gui.tcl" 5400 priority 6 scheduling enabled. Waiting for connection request... priority 8 scheduling enabled. /usr/lib/pd/bin/pd-watchdog ... connected pd: exiting
i missed that info in your original mail (please don't require anyone willing to answer to have read all your emails to this list and remember them :-))
sorry, thanks for your help so far!
check the various posts on this list about why [loadbang]->[; pd dsp 1( often does not work. a simple workaround is to introduce a [delay 1000] to start dsp only after some "boot time".
I'd forgotten about the [delay] for [loadbang] when turning the dsp on but it doesn't result in any sound when running in -nogui.
can you run $ wish via the ssh connection?
Yes, it opens a blank window on the local machine.
if so, Pd should be able to run fine. which version of tcl/tk do you have installed?
tk-8.6.0-1 tcl-8.6.0-4
you could also try to run Pd without realtime priviliges $ pd -nrt
I tried that but it didn't help either.
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Hi,
I had the same exact problem. My main computer running arch and thr rpi running raspian.
I ultimately solved it by :
on main computer: xhost +
on rpi: export DISPLAY=mycomputer.local:0 # or export DISPLAY=10.0.0.1:0 if you don't have avahi running
Then, the display will not pass inside a ssh tunnel but straight on the X11 connection.
Beware that it requires the X server listens to tcp x11 session, which is not the default on arch i guess. You can check that with:
~$ sudo netstat -lntp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:6000 0.0.0.0:* LISTEN 1110/X <-- this line !
Check in the list archive for "X11 forwarding woes" in january 2013, this might help too.
James Dunn wrote:
Hi,
I have installed Arch linux on my Raspberry Pi and am logging in with ssh -Y raspberrypi.local. I can run xterm fine over the connection but pd fails with no information other than:
$ pd priority 6 scheduling enabled. priority 8 scheduling enabled. watchdog: signaling pd... pd: exiting
If I set the debug level to 5 I get the following information:
$ pd -d 5 set pd_whichmidiapi 2 priority 6 scheduling enabled. priority 8 scheduling enabled. pdtk_watchdog set ::tmp_path {} set ::sys_searchpath $::tmp_path set ::tmp_path {} lappend ::tmp_path {/home/james/pd-externals} lappend ::tmp_path {/usr/local/lib/pd-externals} lappend ::tmp_path {/usr/lib/pd/extra} set ::sys_staticpath $::tmp_path set ::startup_flags {} set ::startup_libraries {} pdtk_pd_startup 0 43 4 {} { {OSS 2} {ALSA 1} {jack 5} } { {default-MIDI 2} {ALSA-MIDI 1} } {DejaVu Sans Mono} bold set pd_whichmidiapi 2 pd: exiting
Any ideas why pd can't run over the ssh connection? It runs fine with the -nogui option.
James
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list