problems starting jack

Asked by Sbn on 2007-08-13

 when i open jack from the interface it shows this error message *warning* You have no standard location set, putting files into the current
           directory. Please consider setting base_dir in ~/.jack3rc.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu jack Edit question
Assignee:
No assignee Edit question
Solved by:
Cesare Tirabassi
Solved:
2007-08-13
Last query:
2007-08-13
Last reply:
2007-08-13
Cesare Tirabassi (norsetto) said : #1

The Jack Server is available through the jackd package:

Package: jackd (0.102.20-1) [universe]
JACK Audio Connection Kit (server and example clients)

Low-latency sound server. JACK allows the connection of multiple applications to an audio device, as well as allowing them to share audio between themselves.

See <http://jackit.sourceforge.net/> for more info.

Sbn (esbenvinsnes) said : #2

Ok, but I have that package installed and it still doesn't work...

Cesare Tirabassi (norsetto) said : #3

You mean you still get the message "could not connect with the Jack server"?
Can you paste here the exact error message, as well as what you did to obtain it?

Sbn (esbenvinsnes) said : #4

This is what happens: I go to "Applications" > "Sound & Video" >
"Jackbeat" and the error message is: "Unable to get on air. Is the JACK
server up?" When I open Muse the error message is: "Muse failed to find
a Jack audio server."

On Mon, 2007-08-13 at 18:11 +0000, Cesare Tirabassi wrote:
> Your question #11426 on jack in ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/jack/+question/11426
>
> Status: Open => Needs information
>
> Cesare Tirabassi requested for more information:
> You mean you still get the message "could not connect with the Jack server"?
> Can you paste here the exact error message, as well as what you did to obtain it?
>

Best Cesare Tirabassi (norsetto) said : #5

You have to start the Jack server. Either from terminal:

jackd -R -d alsa

or with the gui:

sudo apt-get install qjackctl

and then you will find a menu entry Jack Control under Sound & Video

Sbn (esbenvinsnes) said : #6

Thank you! Still learnin'...

See-ming Lee (seeminglee) said : #7

Hi,

I'd like some help with my Jack setup as well. I recall being able to use Jack when I tested it a while back but somehow I could not get it working anymore. I also don't know if it has to do with my fussing with the PulseAudio setup but hopefully not.

When I start up the JackCtl GUI, I get these messages:

09:04:09.390 Patchbay deactivated.
09:04:09.402 Statistics reset.
09:04:09.454 Startup script...
09:04:09.456 artsshell -q terminate
09:04:09.461 ALSA connection graph change.
sh: artsshell: not found
09:04:09.859 Startup script terminated with exit status=32512.
09:04:09.861 JACK is starting...
09:04:09.862 /usr/bin/jackd -v -R -dalsa -r44100 -p1024 -n3 -D -Chw:0 -Phw:1 -m -i2 -o2 -Xseq -H -M
09:04:09.867 JACK was started with PID=631.
getting driver descriptor from /usr/lib/jack/jack_alsa.so
getting driver descriptor from /usr/lib/jack/jack_firewire.so
no message buffer overruns
getting driver descriptor from /usr/lib/jack/jack_freebob.so
getting driver descriptor from /usr/lib/jack/jack_oss.so
getting driver descriptor from /usr/lib/jack/jack_net.so
getting driver descriptor from /usr/lib/jack/jack_dummy.so
jackd 0.116.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.
server `default' registered
cannot lock down memory for jackd (Cannot allocate memory)
registered builtin port type 32 bit float mono audio
registered builtin port type 8 bit raw midi
clock source = system clock via clock_gettime
start poll on 3 fd's
loading driver ..
new client: alsa_pcm, id = 1 type 1 @ 0x9a78f60 fd = -1
apparent rate = 44100
creating alsa driver ... hw:1|hw:0|1024|3|44100|2|2|hwmon|hwmeter|-|32bit
control device hw:1
configuring for 44100Hz, period = 1024 frames (23.2 ms), buffer = 3 periods
ALSA: final selected sample format for capture: 16bit little-endian
ALSA: got smaller periods 2 than 3 for capture
ALSA: cannot configure capture channel
cannot load driver module alsa
starting server engine shutdown
freeing shared port segments
server thread back from poll
stopping server thread
last xrun delay: 0.000 usecs
max delay reported by backend: 0.000 usecs
freeing engine shared memory
max usecs: 0.000, engine deleted
cleaning up shared memory
cleaning up files
unregistering server `default'
09:04:09.944 JACK was stopped successfully.
09:04:09.945 Post-shutdown script...
09:04:09.946 killall jackd
09:04:10.067 ALSA connection change.
jackd: no process killed
09:04:10.366 Post-shutdown script terminated with exit status=256.
09:04:12.181 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.

The devices running area09:04:09.390 Patchbay deactivated.
09:04:09.402 Statistics reset.
09:04:09.454 Startup script...
09:04:09.456 artsshell -q terminate
09:04:09.461 ALSA connection graph change.
sh: artsshell: not found
09:04:09.859 Startup script terminated with exit status=32512.
09:04:09.861 JACK is starting...
09:04:09.862 /usr/bin/jackd -v -R -dalsa -r44100 -p1024 -n3 -D -Chw:0 -Phw:1 -m -i2 -o2 -Xseq -H -M
09:04:09.867 JACK was started with PID=631.
getting driver descriptor from /usr/lib/jack/jack_alsa.so
getting driver descriptor from /usr/lib/jack/jack_firewire.so
no message buffer overruns
getting driver descriptor from /usr/lib/jack/jack_freebob.so
getting driver descriptor from /usr/lib/jack/jack_oss.so
getting driver descriptor from /usr/lib/jack/jack_net.so
getting driver descriptor from /usr/lib/jack/jack_dummy.so
jackd 0.116.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.
server `default' registered
cannot lock down memory for jackd (Cannot allocate memory)
registered builtin port type 32 bit float mono audio
registered builtin port type 8 bit raw midi
clock source = system clock via clock_gettime
start poll on 3 fd's
loading driver ..
new client: alsa_pcm, id = 1 type 1 @ 0x9a78f60 fd = -1
apparent rate = 44100
creating alsa driver ... hw:1|hw:0|1024|3|44100|2|2|hwmon|hwmeter|-|32bit
control device hw:1
configuring for 44100Hz, period = 1024 frames (23.2 ms), buffer = 3 periods
ALSA: final selected sample format for capture: 16bit little-endian
ALSA: got smaller periods 2 than 3 for capture
ALSA: cannot configure capture channel
cannot load driver module alsa
starting server engine shutdown
freeing shared port segments
server thread back from poll
stopping server thread
last xrun delay: 0.000 usecs
max delay reported by backend: 0.000 usecs
freeing engine shared memory
max usecs: 0.000, engine deleted
cleaning up shared memory
cleaning up files
unregistering server `default'
09:04:09.944 JACK was stopped successfully.
09:04:09.945 Post-shutdown script...
09:04:09.946 killall jackd
09:04:10.067 ALSA connection change.
jackd: no process killed
09:04:10.366 Post-shutdown script terminated with exit status=256.
09:04:12.181 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.

My audio hardware on this box has:
hw0 = a soundblaster live 5.1 card
hw1 = a Lexicon Pro Omega 8x4x2 conncted through USB

As an fyi, I was not able to get capture working with PulseAudio either. I do know that there's nothing 'wrong' with the hardware in that the unit functions properly under Vista (though of course it also uses specific drivers for that OS).

Any help would be much appreciated!

Dave (davidpilcherclayton) said : #8

Hi,

I also have a jackd server problem.

When i try to start the jackd server from the terminal i get this output

dave@dave-desktop:~$ jackd -R -d alsa
no message buffer overruns
jackd 0.116.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.
cannot use real-time scheduling (FIFO at priority 10) [for thread -1211761920, from thread -1211761920] (1: Operation not permitted)
cannot create engine

jackd has never worked for me and i am new to linux so any help would be greatly appreciated, it is holding back my music production!

 :-( :-( :-(

joekluse (joekluse) said : #9

Hi,

   I'm also new to Linux, and have the same problem. Not sure what the solution is, but I think it's related to permissions. I say this because I can open a terminal window and type

      sudo /usr/bin/jackd -R -dalsa -dhw:0 -r44100 -p1024 -n2
(which is the command I find in the messages window) and it seems to start up fine. I don't get an error in the message window.
Now, if I try to start Muse from the window menu, I get the error, but when I start it through a terminal window via

     sudo muse

it seems to start up fine (now I still have no idea how to run Muse, so I don't know if it is running correctly, but I don't get the errors any more.
I suspect we can change permissions on some of these executables to fix this problem but have no idea which ones. If anyone could help out with this, it would be appreciated. I'm guessing I can write a script to run both commands, but that seems like the brute-force approach. I'm guessing that there is a better way.....

Thanks,
Joe

Dave (davidpilcherclayton) said : #10

HI,

when i enter the line you found in a terminal it appears to be working, however when i enter the corresponding line from my own message dialog

 /usr/bin/jackd -R -dalsa -dhw:0 -r44100 -p1024 -n3

it won't work. any idea what the -n2/-n3 refers to??

thanks for letting me know about muse by the way! although i can't seem to get that working yet either

i have opened a new question on the subject, you might like to check here as well

https://answers.launchpad.net/ubuntu/+source/jack/+question/81151

Dave

european (mariejozee) said : #11

Hi!

I use xubuntu 9.10

Sound card: Soundblaster live Platinum

Try to use Rosegarden, but can't start Jack.
This message appeares:

16:13:30.908 Patchbay deactivated.
16:13:30.967 Statistics reset.
16:13:31.003 Startup script...
16:13:31.003 artsshell -q terminate
16:13:31.040 ALSA connection graph change.
sh: artsshell: not found
16:13:31.405 Startup script terminated with exit status=32512.
16:13:31.405 JACK is starting...
16:13:31.406 /usr/bin/jackd -R -P25 -p128 -dalsa -r44100 -p128 -n2 -D -Chw:0 -Phw:0 -i2 -o2 -Xraw
16:13:31.420 JACK was started with PID=30625.
no message buffer overruns
jackd 0.116.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.
cannot use real-time scheduling (FIFO at priority 10) [for thread 260376304, from thread 260376304] (1: Operation not permitted)
cannot create engine
16:13:31.426 JACK was stopped successfully.
16:13:31.426 Post-shutdown script...
16:13:31.427 killall jackd
16:13:31.620 ALSA connection change.
jackd: no process found
16:13:31.834 Post-shutdown script terminated with exit status=256.
16:13:33.644 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.

Can anybody tell what I'm doing wrong? I'm kind of a Linux newbe

Thanks!

Bagga (pbarracl) said : #12

I get this problem and have had for ages, you install Rosegarden from the suppositories, but it just doesn't work, due to the Jack server, it's a pain in the harris. Really want it to work, any ideas guys?

run this:
sudo su -c 'echo @audio - rtprio 99 >> /etc/security/limits.conf'
and it should start working. and please let me know, if u are able to use the general midi interface with all those beautiful instruments in rosegarden, cause in my system only the synth plugin works...