Hallo! Sorry for just another jack problem - but I have searched the archive, and it's really strange ... My problem: I am able to start jack with qjackctl or jackd. [1] - see example output of qjackctl I want to use PD with jack and the strange thing is, that a few months ago everything worked fine with the same hard- and software. Then I installed a new version of PD and I couldn't connect to jack from PD anymore. So I reinstalled the old version, installed new alsa, jack drivers ... I tried a lot, but I cannot manage it :( My configuration: RME HDSP Multiface, PD 0.38-4, jackd version 0.99.51, QJackCtl version 0.2.15a, debian, kernel 2.6.8 First I thought it is a PD problem, but I also couldn't connect with e.g. jack-rack. I tried different users, settings, ... nothing helped. Maybe someone has an idea? Thanks a lot, LG Georg [1]: 13:36:06.193 Startup script terminated with exit status=256. 13:36:06.193 JACK is starting... 13:36:06.193 /usr/bin/jackd -dalsa -dhw:0,0 -r44100 -p1024 -n2 13:36:06.196 JACK was started with PID=4102 (0x1006). jackd 0.99.51 Copyright 2001-2005 Paul Davis and others. jackd comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details JACK compiled with System V SHM support. loading driver .. apparent rate = 44100 creating alsa driver ... hw:0,0|hw:0,0|1024|2|44100|0|0|nomon|swmeter|-|32bit control device hw:0 configuring for 44100Hz, period = 1024 frames, buffer = 2 periods nperiods = 2 for capture nperiods = 2 for playback 13:36:08.208 Server configuration saved to "/home/holzi/.jackdrc". 13:36:08.208 Statistics reset. 13:36:08.211 Client activated. 13:36:08.212 Audio connection change. 13:36:08.213 Audio connection graph change. 13:36:09.446 Transport start. 13:36:10.726 XRUN callback (1). **** alsa_pcm: xrun of at least 216.911 msecs ...