Jack Control problem

[Leevi]

I got the following message when starting the Jack Control.

Could not connect to JACK server as client.
- Overall operation failed.
- Unable to connect to server.
Please check the messages window for more info

15:25:37.902 Patchbay deactivated.
15:25:37.903 Statistics reset.
15:25:38.020 ALSA connection graph change.
15:25:38.216 ALSA connection change.
15:25:39.777 Startup script...
15:25:39.779 artsshell -q terminate
sh: artsshell: not found
15:25:40.182 Startup script terminated with exit status=32512.
15:25:40.183 JACK is starting...
15:25:40.183 /usr/bin/jackd -R -dalsa -dhw:0 -r44100 -p1024 -n2
15:25:40.190 JACK was started with PID=2052.
no message buffer overruns
jackd 0.116.1

/Leevi

[isic]

i have the same problem. have been running kxstudio on an external hardrive on a laptop. then switched to a desktop with and audigy sound blaster. i boot kxstudio on the external and i get the same message when starting jack. you have an old post. just wondering what you did to fix the problem.

[Leevi]

I don't have the problem any more. I have upgraded my Ubuntu to 10.04 and the problem doesn't exist there. Below the message (correct?) I receive when I start Jack Control.

23:50:52.103 Patchbay deactivated.
23:50:52.188 Statistics reset.
23:50:52.477 ALSA connection graph change.
23:50:52.735 ALSA connection change.
23:51:20.551 Startup script...
23:51:20.552 artsshell -q terminate
sh: artsshell: not found
23:51:20.955 Startup script terminated with exit status=32512.
23:51:20.956 JACK is starting...
23:51:20.958 /usr/bin/jackd -r -dalsa -dhw:0 -r44100 -p1024 -n2
jackd 0.118.0
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn 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
Memory locking is unlimited - this is dangerous. You should probably alter the line:
@audio - memlock unlimited
in your /etc/limits.conf to read:
@audio - memlock 769779
23:51:20.973 JACK was started with PID=2547.
no message buffer overruns
JACK compiled with System V SHM support.
loading driver ..
apparent rate = 44100
creating alsa driver ... hw:0|hw:0|1024|2|44100|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 44100Hz, period = 1024 frames (23.2 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 2 periods for playback
23:51:23.019 Server configuration saved to "/home/ollura/.jackdrc".
23:51:23.020 Statistics reset.
23:51:23.022 Client activated.
23:51:23.024 JACK connection change.
23:51:23.035 JACK connection graph change.

[isic]

from going to other linux forums i was able to locate the problem. just needed to reduce the buffer from 3 to 2. in case any one else is reading. open jack control. if you are having the same problem it will open "stopped". go to set up. look for "periods/buffer". its default maybe "3". change it to 2. press start on Jack. if it keeps running: its good. if the "RT" is flashing, you will be in real time. it worked for me anyway.