Trouble with JACK

What other apps and distros do you use to round out your studio?

Moderators: MattKingUSA, khz

Post Reply
chimples
Established Member
Posts: 7
Joined: Wed Dec 30, 2009 4:51 am

Trouble with JACK

Post by chimples »

Hi all, I had my Jack audio control up and running recently and got myself to grips with the audio and midi connections involved but now when i start it up i get no sound and i cant think why, im pretty certain im doing what i did before but it just wont work.

This is the messages it gives on startup, hope it helps:

15:53:14.229 Patchbay deactivated.
15:53:14.232 Statistics reset.
15:53:14.448 ALSA connection graph change.
15:53:14.692 ALSA connection change.
15:53:17.808 Startup script...
15:53:17.809 artsshell -q terminate
sh: artsshell: not found
15:53:18.212 Startup script terminated with exit status=32512.
15:53:18.212 JACK is starting...
15:53:18.213 /usr/bin/jackd -R -p128 -t5000 -dalsa -dhw:0 -r48000 -p64 -n2 -s -S
15:53:18.216 JACK was started with PID=6273.
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.
loading driver ..
apparent rate = 48000
creating alsa driver ... hw:0|hw:0|64|2|48000|0|0|nomon|swmeter|soft-mode|16bit
control device hw:0
configuring for 48000Hz, period = 64 frames (1.3 ms), 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
15:53:20.357 Server configuration saved to "/home/chimples/.jackdrc".
15:53:20.358 Statistics reset.
15:53:20.414 Client activated.
15:53:20.416 JACK connection change.
15:53:20.421 JACK connection graph change.
User avatar
GarryO
Established Member
Posts: 167
Joined: Mon Apr 06, 2009 7:30 pm
Location: UK
Contact:

Re: Trouble with JACK

Post by GarryO »

Hi, Chimples. Your jack messages look healthy to me, there's nothing wrong there.
Are your audio outputs turned up? Use alsamixer or similar.
How are you generating the audio (that you can't hear)?
chimples
Established Member
Posts: 7
Joined: Wed Dec 30, 2009 4:51 am

Re: Trouble with JACK

Post by chimples »

I had tried running virtual midi keyboard through aeolus, which previously worked, but failing that I was playing youtube videos (to test the sound) which also failed. The audio was definately turned up as they would run fine, id start jack, and audio would just stop.
Pablo
Established Member
Posts: 1274
Joined: Thu Apr 17, 2008 9:57 pm
Been thanked: 3 times

Re: Trouble with JACK

Post by Pablo »

Hi chimple, have you checked that the interface is the right one, in the qjackctl setup?

If you happen to have more than one audio device and you have not given to them consistent numbers in the alsa configuration file, they could change device ID number in different boots. In this case, jack would be controlling the other device (if there is such other, I am just trying to guess)
chimples
Established Member
Posts: 7
Joined: Wed Dec 30, 2009 4:51 am

Re: Trouble with JACK

Post by chimples »

Ive tried to run jack with all the options under interface with no luck. I've also found that jack crashes other programs when i run it.
chimples
Established Member
Posts: 7
Joined: Wed Dec 30, 2009 4:51 am

Re: Trouble with JACK

Post by chimples »

Thanks to all for the help, have just noticed these in the message box and figured they might be useful

17:31:54.207 Patchbay deactivated.
17:31:54.227 Statistics reset.
17:31:54.282 ALSA connection graph change.
17:31:54.534 ALSA connection change.
17:31:57.006 Startup script...
17:31:57.007 artsshell -q terminate
sh: artsshell: not found
17:31:57.409 Startup script terminated with exit status=32512.
17:31:57.409 JACK is starting...
17:31:57.410 /usr/bin/jackd -R -p128 -t5000 -dalsa -dhw:0 -r48000 -p64 -n2 -s -S
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.
loading driver ..
apparent rate = 48000
creating alsa driver ... hw:0|hw:0|64|2|48000|0|0|nomon|swmeter|soft-mode|16bit
control device hw:0
17:31:57.457 JACK was started with PID=6398.
configuring for 48000Hz, period = 64 frames (1.3 ms), 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
17:31:59.594 Server configuration saved to "/home/chimples/.jackdrc".
17:31:59.595 Statistics reset.
17:31:59.629 Client activated.
17:31:59.631 JACK connection change.
17:31:59.637 JACK connection graph change.
17:32:10.813 XRUN callback (1).
delay of 2220.000 usecs exceeds estimated spare time of 1250.000; restart ...
delay of 2220.000 usecs exceeds estimated spare time of 1250.000; restart ...
17:32:12.447 XRUN callback (1 skipped).
17:32:13.480 Client deactivated.
17:32:13.481 JACK is stopping...
jack main caught signal 15
17:32:13.586 JACK was stopped successfully.
17:32:13.586 Post-shutdown script...
17:32:13.587 killall jackd
jackd: no process found
17:32:13.997 Post-shutdown script terminated with exit status=256.
17:32:14.562 Startup script...
17:32:14.563 artsshell -q terminate
sh: artsshell: not found
17:32:14.966 Startup script terminated with exit status=32512.
17:32:14.966 JACK is starting...
17:32:14.967 /usr/bin/jackd -R -p128 -t5000 -dalsa -dhw:0 -r48000 -p64 -n2 -s -S
no message buffer overruns
17:32:14.984 JACK was started with PID=6413.
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.
loading driver ..
apparent rate = 48000
creating alsa driver ... hw:0|hw:0|64|2|48000|0|0|nomon|swmeter|soft-mode|16bit
control device hw:0
configuring for 48000Hz, period = 64 frames (1.3 ms), 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
17:32:17.065 Server configuration saved to "/home/chimples/.jackdrc".
17:32:17.067 Statistics reset.
17:32:17.069 Client activated.
17:32:17.071 JACK connection change.
17:32:17.078 JACK connection graph change.
17:32:20.981 XRUN callback (1).
delay of 1872.000 usecs exceeds estimated spare time of 1265.000; restart ...
delay of 1872.000 usecs exceeds estimated spare time of 1265.000; restart ...
17:32:21.080 XRUN callback (1 skipped).
17:32:22.236 XRUN callback (3).
delay of 1739.000 usecs exceeds estimated spare time of 1242.000; restart ...
delay of 1739.000 usecs exceeds estimated spare time of 1242.000; restart ...
delay of 3652.000 usecs exceeds estimated spare time of 1242.000; restart ...
delay of 3652.000 usecs exceeds estimated spare time of 1242.000; restart ...
delay of 3652.000 usecs exceeds estimated spare time of 1242.000; restart ...
17:32:23.086 XRUN callback (4 skipped).
17:32:26.212 XRUN callback (8).
delay of 3762.000 usecs exceeds estimated spare time of 1266.000; restart ...
delay of 3762.000 usecs exceeds estimated spare time of 1266.000; restart ...
delay of 3762.000 usecs exceeds estimated spare time of 1266.000; restart ...
delay of 2841.000 usecs exceeds estimated spare time of 1266.000; restart ...
delay of 2841.000 usecs exceeds estimated spare time of 1266.000; restart ...
delay of 2841.000 usecs exceeds estimated spare time of 1266.000; restart ...
delay of 1694.000 usecs exceeds estimated spare time of 1266.000; restart ...
delay of 1694.000 usecs exceeds estimated spare time of 1266.000; restart ...
17:32:27.099 XRUN callback (7 skipped).
User avatar
GarryO
Established Member
Posts: 167
Joined: Mon Apr 06, 2009 7:30 pm
Location: UK
Contact:

Re: Trouble with JACK

Post by GarryO »

Unfortunately playing you-tube vids isn't going to work unless you're using something like the ALSA Jack Plugin because neither your browser or flash is jack-aware. ( I personally don't find this plugin very effective but YMMV. )
Aeolus should work but you will need to manually connect the audio & midi ports.
Jack grabs control of the audio system and will block any other program that tries to use it ( and crash them too It sounds like!).
Have you tried using a jack-capable media player like aqualung to play an audio file?
Further to Pablo's suggestion, can you post the result of typing

Code: Select all

 cat /proc/asound/cards
into a terminal? Also

Code: Select all

 lsmod | grep snd
?
User avatar
GarryO
Established Member
Posts: 167
Joined: Mon Apr 06, 2009 7:30 pm
Location: UK
Contact:

Re: Trouble with JACK

Post by GarryO »

Just missed your last post. Try setting periods=1024 ( a nice safe value ). 64 is a very low setting which is why you are getting all those xruns.
check out the wiki: http://wiki.linuxmusicians.com/doku.php ... 2978397f76
What sound card are you using?
chimples
Established Member
Posts: 7
Joined: Wed Dec 30, 2009 4:51 am

Re: Trouble with JACK

Post by chimples »

Changing the period settings did it, thanks a lot for the help, still seems to crash my web browser though, regardless of whether its producing audio, but i can live with that. Thanks again
Post Reply