Sampo Savolainen kirjoitti:
This is the messages printed in messages window of qjackctl:
15:41:20.664 Patchbay activated.
15:41:20.667 Statistics reset.
15:41:20.738 ALSA connection graph change.
15:41:20.929 ALSA active patchbay scan...
15:41:20.932 ALSA connection change.
15:41:21.136 ALSA active patchbay scan...
15:41:35.807 Startup script...
15:41:35.809 artsshell -q terminate
sh: artsshell: not found
15:41:36.230 Startup script terminated with exit status=32512.
15:41:36.232 JACK is starting...
15:41:36.234 /usr/bin/jackd -R -p128 -dalsa -dhw:0 -r48000 -p256 -n4
15:41:36.244 JACK was started with PID=3261.
no message buffer overruns
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|256|4|48000|0|0|nomon|swmeter|-|32bit
control device hw:0
15:41:37.555 JACK was stopped successfully.
15:41:37.557 Post-shutdown script...
15:41:37.559 killall jackd
15:41:37.561 JACK has crashed.
jackd: no process killed
15:41:37.980 Post-shutdown script terminated with exit status=256.
15:41:38.442 Could not connect to JACK server as client. - Overall
operation failed. - Unable to connect to server. Please check the
messages window for more info.
It seems to me that the actual cause is not revealed in these messages,
perhaps there is better log somewhere else?
> In a (bash) shell, running:
These will give me right numbers that I have set in limits.conf (250000,99).
> On a system like a netbook, you can also try 'jackd --no-mlock' or
These don't seem to help much.
But the thing I'm also interested is why same Jack settings work when
running qjackctl as sudo?
Linux-audio-user mailing list