hmm, as I was saying...<br><br>When I try to startup jack with the JACK Audio Connection Kit I get the following output in the messages window:<br><br><b>With realtime option selected in Setup:</b><br clear="all">21:05:23.603 Patchbay deactivated.<br>
21:05:23.680 Statistics reset.<br>21:05:23.796 ALSA connection graph change.<br>21:05:23.924 ALSA connection change.<br>21:07:48.630 Startup script...<br>21:07:48.631 artsshell -q terminate<br>21:07:49.078 Startup script terminated with exit status=256.<br>
21:07:49.082 JACK is starting...<br>21:07:49.084 /usr/bin/jackd -R -P70 -dalsa -dhw:0 -r48000 -p64 -n2 -m<br>jackd 0.109.12<br>Copyright 2001-2005 Paul Davis and others.<br>jackd comes with ABSOLUTELY NO WARRANTY<br>This is free software, and you are welcome to redistribute it<br>
under certain conditions; see the file COPYING for details<br>JACK compiled with System V SHM support.<br>21:07:49.124 JACK was started with PID=6336.<br>loading driver ..<br>Enhanced3DNow! detected<br>SSE2 detected<br>apparent rate = 48000<br>
creating alsa driver ... hw:0|hw:0|64|2|48000|0|0|nomon|swmeter|-|32bit<br>control device hw:0<br>configuring for 48000Hz, period = 64 frames (1.3 ms), buffer = 2 periods<br>ALSA: final selected sample format for capture: 32bit little-endian<br>
ALSA: use 2 periods for capture<br>ALSA: final selected sample format for playback: 32bit little-endian<br>ALSA: use 2 periods for playback<br>**** alsa_pcm: xrun of at least 0.055 msecs<br>**** alsa_pcm: xrun of at least 0.072 msecs<br>
... many more xruns ...<br><b>21:07:51.150 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.<br></b>... many more xruns ...<br>
... and so I stop it ...<br>21:07:55.842 JACK is stopping...<br>**** alsa_pcm: xrun of at least 0.042 msecs<br>jack main caught signal 15<br>no message buffer overruns<br>21:07:55.893 JACK was stopped successfully.<br>21:07:55.895 Post-shutdown script...<br>
21:07:55.897 killall jackd<br>jackd: no process killed<br>21:07:56.365 Post-shutdown script terminated with exit status=256.<br><br><b>With realtime option unselected in Setup:</b><br>21:21:59.084 Patchbay deactivated.<br>
21:21:59.262 Statistics reset.<br>21:21:59.395 ALSA connection graph change.<br>21:21:59.480 ALSA connection change.<br>21:22:10.464 Startup script...<br>21:22:10.465 artsshell -q terminate<br>21:22:10.911 Startup script terminated with exit status=256.<br>
21:22:10.913 JACK is starting...<br>21:22:10.913 /usr/bin/jackd -dalsa -dhw:0 -r48000 -p64 -n2 -m<br><b>21:22:10.937 JACK was started with PID=6398.</b><br>jackd 0.109.12<br>Copyright 2001-2005 Paul Davis and others.<br>jackd comes with ABSOLUTELY NO WARRANTY<br>
This is free software, and you are welcome to redistribute it<br>under certain conditions; see the file COPYING for details<br>JACK compiled with System V SHM support.<br>loading driver ..<br>Enhanced3DNow! detected<br>SSE2 detected<br>
apparent rate = 48000<br>creating alsa driver ... hw:0|hw:0|64|2|48000|0|0|nomon|swmeter|-|32bit<br>control device hw:0<br>configuring for 48000Hz, period = 64 frames (1.3 ms), buffer = 2 periods<br>ALSA: final selected sample format for capture: 32bit little-endian<br>
ALSA: use 2 periods for capture<br>ALSA: final selected sample format for playback: 32bit little-endian<br>ALSA: use 2 periods for playback<br>**** alsa_pcm: xrun of at least 0.491 msecs<br>**** alsa_pcm: xrun of at least 0.075 msecs<br>
... many more xruns ...<br><b>21:22:13.000 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.<br></b>... many more xruns ...<br>
... so I stop it ...<br>21:22:16.732 JACK is stopping...<br>**** alsa_pcm: xrun of at least 0.058 msecs<br>jack main caught signal 15<br>no message buffer overruns<br>21:22:16.779 JACK was stopped successfully.<br>21:22:16.784 Post-shutdown script...<br>
21:22:16.785 killall jackd<br>jackd: no process killed<br>21:22:17.230 Post-shutdown script terminated with exit status=256.<br><br>The only difference I can see is that JACK was reported to have actually started with the realtime option turned off but not when it was turned on. In either case though, the client could not connect to the server.<br>
<br>Here's my setup:<br><br><b>JACK Audio Connection Kit version:</b><i><br>rpm -q jack-audio-connection-kit</i><br>jack-audio-connection-kit-0.109.12-0.svn1135_942.1.fc8.ccrma<br>jack-audio-connection-kit-0.109.12-0.svn1135_942.1.fc8.ccrma<br>
- there seems to be 2 of them! Maybe because I have 2 versions of the planetccma kernel installed. Could this cause problems?<br><br><b>planetccrma kernel version:</b><br>2.6.24.6-1.rt3.4.fc8.ccrmart.x86_64<br><br><b>I have the following lines at the bottom of the /etc/security/limits.conf</b><br>
## Automatically appended by the Planet CCRMA jack-audio-connection-kit<br>* - rtprio 99<br>* - memlock 4194304<br>* - nice -10<br><br><b>Snippets from /var/log/messages that might be relevant:</b><br>May 15 14:12:06 localhost kernel: Linux version 2.6.24.6-1.rt3.4.fc8.ccrmart (<a href="mailto:mockbuild@cm-matlab.stanford.edu">mockbuild@cm-matlab.stanford.edu</a>) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)) #1 SMP PREEMPT RT Tue May 6 16:44:13 EDT 2008<br>
...<br>May 15 14:12:06 localhost kernel: Real-Time Preemption Support (C) 2004-2007 Ingo Molnar<br>...<br>May 15 14:12:06 localhost kernel: Clockevents: could not switch to one-shot mode:<6>Clockevents: could not switch to one-shot mode: lapic is not functional.<br>
May 15 14:12:06 localhost kernel: Could not switch to high resolution mode on CPU 0<br>May 15 14:12:06 localhost kernel: lapic is not functional.<br>May 15 14:12:06 localhost kernel: Could not switch to high resolution mode on CPU 1<br>
...<br>May 15 14:12:06 localhost kernel: Clockevents: could not switch to one-shot mode:<6>Clockevents: could not switch to one-shot mode: lapic is not functional.<br>May 15 14:12:06 localhost kernel: Could not switch to high resolution mode on CPU 1<br>
May 15 14:12:06 localhost kernel: lapic is not functional.<br>May 15 14:12:06 localhost kernel: Could not switch to high resolution mode on CPU 0<br>...<br>May 15 14:12:06 localhost kernel: ALSA sound/pci/hda/hda_intel.c:732: codec_mask = 0x1<br>
...<br>May 15 14:12:06 localhost kernel: Clocksource tsc unstable (delta = -62578070 ns)<br>...<br>May 15 14:12:55 localhost pulseaudio[3053]: main.c: This program is not intended to be run as root (unless --system is specified).<br>
May 15 14:12:56 localhost pulseaudio[3053]: alsa-util.c: Device (null) doesn't support 44100 Hz, changed to 48000 Hz.<br>May 15 14:12:56 localhost pulseaudio[3053]: alsa-util.c: Device (null) doesn't support 44100 Hz, changed to 48000 Hz.<br>
May 15 14:12:56 localhost pulseaudio[3053]: alsa-util.c: Cannot find fallback mixer control "Mic".<br>...<br>May 15 14:16:53 localhost pulseaudio[3354]: polkit.c: Failed to show grant dialog: Unable to lookup exe for caller<br>
May 15 14:16:53 localhost pulseaudio[3354]: polkit.c: PolicyKit responded with 'auth_admin_keep_always'<br>May 15 14:16:53 localhost pulseaudio[3354]: main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not permitted<br>
May 15 14:16:53 localhost pulseaudio[3354]: alsa-util.c: Device (null) doesn't support 44100 Hz, changed to 48000 Hz.<br>May 15 14:16:53 localhost pulseaudio[3354]: alsa-util.c: Device (null) doesn't support 44100 Hz, changed to 48000 Hz.<br>
May 15 14:16:53 localhost pulseaudio[3354]: alsa-util.c: Cannot find fallback mixer control "Mic".<br>...<br><br>I hope this is is enough information to spark some ideas about how to get JACK working on my machine.<br>
<br>-- <br>Kind Regards,<br><br>Paul Vallee<br><a href="mailto:pv.vallee@gmail.com">pv.vallee@gmail.com</a><br><br>.