Help! Jack not starting in realtime mode!

Installation & Configuration Linux
#1

it says its starting then it srops and comes up with errors :frowning:

the message window displays:

22:17:45.714 Patchbay deactivated.
22:17:45.722 Statistics reset.
22:17:46.260 Startup script…
22:17:46.268 artsshell -q terminate
22:17:46.310 ALSA connection graph change.
sh: artsshell: not found
22:17:46.848 Startup script terminated with exit status=32512.
22:17:46.850 JACK is starting…
22:17:46.852 /usr/bin/jackd -R -P79 -dalsa -dhw:0 -r48000 -p1024 -n3 -S
22:17:46.866 JACK was started with PID=4423.
22:17:47.066 ALSA connection change.
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.
`default’ server already active
22:17:47.576 JACK was stopped with exit status=1.
22:17:47.580 Post-shutdown script…
22:17:47.581 killall jackd
22:17:48.031 Post-shutdown script terminated successfully.
22:17:49.100 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.

After some googling i saw that some people say it might be todo with the limits-conf file, so here that is:

/etc/security/limits.conf

#Each line describes a limit for a user in the form:

#

#Where:
# can be:

- an user name

- a group name, with @group syntax

- the wildcard *, for default entry

- the wildcard %, can be also used with %group syntax,

for maxlogin limit

- NOTE: group and wildcard limits are not applied to root.

To apply a limit to the root user, must be

the literal username root.

# can have the two values:

- “soft” for enforcing the soft limits

- “hard” for enforcing hard limits

# can be one of the following:

- core - limits the core file size (KB)

- data - max data size (KB)

- fsize - maximum filesize (KB)

- memlock - max locked-in-memory address space (KB)

- nofile - max number of open files

- rss - max resident set size (KB)

- stack - max stack size (KB)

- cpu - max CPU time (MIN)

- nproc - max number of processes

- as - address space limit (KB)

- maxlogins - max number of logins for this user

- maxsyslogins - max number of logins on the system

- priority - the priority to run user process with

- locks - max number of file locks the user can hold

- sigpending - max number of pending signals

- msgqueue - max memory used by POSIX message queues (bytes)

- nice - max nice priority allowed to raise to values: [-20, 19]

- rtprio - max realtime priority

- chroot - change root to directory (Debian-specific)

#

#* soft core 0
#root hard core 100000
#* hard rss 10000
#@student hard nproc 20
#@faculty soft nproc 20
#@faculty hard nproc 50
#ftp hard nproc 0
#ftp - chroot /ftp
#@student - maxlogins 4

End of file

@audio - memlock 383824unlimited
@audio - rtprio 99

@audio - memlock 383824unlimited

would anyone beable to help me??

thanksss

#2

are you in the “audio” group? if you added yourself to the group, did you logout and back in after adding yourself?
also, the lines for memlock are badly formatted and should either be

@audio - memlock unlimited

OR

@audio - memlock 383824

the numerical value is almost certainly too small, btw.

#3

thanks for the reply

yeah i added my self to the audio group and logged in and out

and ive tryed editing the limits-conf file but it says i do not have the nessecary permissions???

#4

looks like your limits.conf is not correct

you need root privileges to edit. Try to use the sudo command with a text editor of your choice (I usually use emacs but you have probably plenty others like ‘nano’ or … ‘vi’ … ahem … )

OK, use nano:

sudo nano /etc/security/limits.conf

and follow Paul’s suggestion (pick unlimited).

#5

Hi

Got some questions for you, so we can find the error

What changes did you make, compared to the last time?
What is the error output from the Jack message box?

Did you try launching Jack as root or sudo (just to find where the problem comes from)???

What system are you running?

#6

thanks alot the posts guys, it started to work for a little, but now its completely screwed, it wont even open in not realtime mode, maybe i did something wrong?

#7

okay, i edited the limits conf file in nano, so that it was:

@audio - memlock unlimited

and re-added myself to the audio group.

Jack displays these messages when i try to start up (if it doesn’t freeze):

Could not connect to JACK server as client.

  • Overall operation failed.
  • Unable to connect to server.
    Please check the messages window for more info.

21:05:01.767 Patchbay deactivated.
21:05:01.781 Statistics reset.
21:05:01.951 ALSA connection graph change.
21:05:02.310 ALSA connection change.
21:05:04.573 Startup script…
21:05:04.574 artsshell -q terminate
sh: artsshell: not found
21:05:04.981 Startup script terminated with exit status=32512.
21:05:04.983 JACK is starting…
21:05:04.985 /usr/bin/jackd -R -dalsa -dhw:0 -r44100 -p128 -n2
21:05:05.092 JACK was started with PID=2864.
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.
`default’ server already active
21:05:05.212 JACK was stopped with exit status=1.
21:05:05.214 Post-shutdown script…
21:05:05.216 killall jackd
21:05:05.643 Post-shutdown script terminated successfully.
21:05:07.197 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server.

I’m not really sure what you mean when you ask how i launched jack :confused: i just clicked applications>sound and video>jack control

and i’m running ubuntu 9.10 and i think its the 2.6.31.9-rt kernnel but im not too sure

thanks for all the help guys

#8

NOTE: `default’ server already active

JACK is aready running!