starting jack

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

starting jack

Gilles Pelletier
I have just installed jack through planet CCRMA's global package and
real time kernel.
When I start it up it shuts down with the following messages:
<quote>
12:26:15.809 Startup script...
12:26:15.809 artsshell -q terminate
JACK tmpdir identified as [/dev/shm]
12:26:16.047 Startup script terminated with exit status=256.
12:26:16.047 JACK is starting...
12:26:16.047 jackd -v -R -dalsa -dhw:0 -r44100 -p1024 -n2
12:26:16.049 JACK was started with PID=3779 (0xec3).
getting driver descriptor from /usr/lib/jack/jack_alsa.so
getting driver descriptor from /usr/lib/jack/jack_freebob.so
getting driver descriptor from /usr/lib/jack/jack_dummy.so
jackd 0.103.0
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.
server `default' registered
loading driver ..
apparent rate = 44100
creating alsa driver ... hw:0|hw:0|1024|2|44100|0|0|nomon|swmeter|-|32bit
control device hw:0
registered builtin port type 32 bit float mono audio
registered builtin port type 8 bit raw midi
clock source = system clock via clock_gettime
new client: alsa_pcm, id = 1 type 1 @ 0x805c7b8 fd = -1
configuring for 44100Hz, period = 1024 frames, buffer = 2 periods
ALSA: final selected sample format for capture: 16bit little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 16bit little-endian
ALSA: use 2 periods for playback
new buffer size 1024
registered port alsa_pcm:capture_1, offset = 4096
registered port alsa_pcm:capture_2, offset = 8192
registered port alsa_pcm:playback_1, offset = 0
registered port alsa_pcm:playback_2, offset = 0
++ jack_rechain_graph():
client alsa_pcm: internal client, execution_order=0.
-- jack_rechain_graph()
3779 waiting for signals
12:26:18.229 Server configuration saved to "/home/gillesg/.jackdrc".
12:26:18.230 Statistics reset.
12:26:18.230 Client activated.
12:26:18.231 Audio connection change.
12:26:18.232 Audio connection graph change.
JACK tmpdir identified as [/dev/shm]
new client: qjackctl-3761, id = 2 type 2 @ 0xb6c6e000 fd = 15
++ jack_rechain_graph():
client qjackctl-3761: start_fd=5, execution_order=0.
client qjackctl-3761: wait_fd=10, execution_order=1 (last client).
-- jack_rechain_graph()
jackd watchdog: timeout - killing jackd
zombified - calling shutdown handler
12:26:21.092 Shutdown notification.
12:26:21.092 Client deactivated.
12:26:21.093 JACK was stopped successfully.
12:26:21.093 Post-shutdown script...
12:26:21.093 killall jackd
cannot send request type 7 to server
cannot read result for request type 7 from server (Broken pipe)
cannot send request type 7 to server
cannot read result for request type 7 from server (Broken pipe)
jackd: no process killed
12:26:21.309 Post-shutdown script t
<\quote>

Could someone advise me on what this means and what can be done about it?
Thanks.

--
Gilles

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Jackit-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jackit-devel