Binary package hint: jackd
when I try to start jack with qjackctrl, it seems to work but in a few seconds it gets killed.
Messages showed by qjackctrl:
20:49:55.015 Startup script...
20:49:55.016 artsshell -q terminate
20:49:55.356 Startup script terminated with exit status=256.
20:49:55.370 JACK is starting...
20:49:55.375 jackd -R -dalsa -dhw:0 -r48000 -p128 -n2
20:49:55.393 JACK was started with PID=5177 (0x1439).
jackd 0.101.1
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 = 48000
creating alsa driver ... hw:0|hw:0|128|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 48000Hz, period = 128 frames, buffer = 2 periods
Note: audio device hw:0 doesn't support a 32bit sample format so JACK will try a 24bit format instead
Note: audio device hw:0 doesn't support a 24bit sample format so JACK will try a 16bit format instead
nperiods = 2 for capture
Note: audio device hw:0 doesn't support a 32bit sample format so JACK will try a 24bit format instead
Note: audio device hw:0 doesn't support a 24bit sample format so JACK will try a 16bit format instead
nperiods = 2 for playback
20:49:57.589 Server configuration saved to "/home/samuele/.jackdrc".
20:49:57.596 Statistics reset.
20:49:57.637 Client activated.
20:49:57.644 Audio connection change.
20:49:57.660 Audio connection graph change.
20:49:57.666 XRUN callback (1).
20:49:59.676 XRUN callback (380 skipped).
jackd watchdog: timeout - killing jackd
20:50:00.556 Shutdown notification.
20:50:00.563 Client deactivated.
20:50:00.570 JACK was stopped successfully.
zombified - calling shutdown handler
cannot send request type 7 to server
cannot read result for request type 7 from server (Pipe interrotta)
cannot send request type 7 to server
cannot read result for request type 7 from server (Pipe interrotta)
It could be dual core specific problem:
http://
Some quotes pasted here:
"I've got similar hardware and Lee's right, the "-clockfix" branch of jack CVS fixes this problem. The root problem is that the TSC clock sources on the AMDx2 cores are not sync'd, therefore time, as perceived by JACK, can appear to leap forward or backward as the process migrates across the CPU cores. The -clockfix branch works around this "feature"."
"Just make sure the kernel is not using the TSC for its own internal
timekeeping. "