Fernando Lopez-Lezcano
<nando(a)ccrma.Stanford.EDU> writes:
On Thu, 2007-11-08 at 13:26 +0100, joakim(a)verona.se wrote:
> Hello,
>
> Im trying to use jackd on fc8 on a lenovo x61 laptop.
>
> Sound is ridiculously choppy. Even if I fail to set realtime settings
> properly or something it shouldnt be this choppy. Normal sound
> through alsa works well.
>
> It makes no difference if I run jackd as root or not.
> I run it through qjackctl, and set alsa port hw:0.
> I also tried no duplex.
>
> I dont think I have any other sound daemons such as pulseaudio,
> esd or arts running.
>
> Any hints how to debug this are apreciated.
If this is using snd-hda-intel hardware you should try setting
"Periods/Buffer" to 3 or more, 2 just does not work on that (toy)
hardware - which I also have in a T61.
-- Fernando
Thanks for these hints! However, I'm still unsucessful.
Log attached.
jackd --realtime -v -R -P14 -dalsa -dhw:0 -r44100 -p2048 -n4 -P
getting driver descriptor from /usr/lib/jack/jack_dummy.so
getting driver descriptor from /usr/lib/jack/jack_alsa.so
getting driver descriptor from /usr/lib/jack/jack_freebob.so
jackd 0.103.0
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
registered builtin port type 32 bit float mono audio
registered builtin port type 8 bit raw midi
clock source = system clock via clock_gettime
loading driver ..
apparent rate = 44100
creating alsa driver
... hw:0|-|2048|4|44100|0|0|nomon|swmeter|-|32bit
control device hw:0
new client: alsa_pcm, id = 1 type 1 @ 0x84aee30 fd = -1
configuring for 44100Hz, period = 2048 frames, buffer = 4 periods
ALSA: final selected sample format for playback: 32bit little-endian
ALSA: use 4 periods for playback
new buffer size 2048
registered port alsa_pcm:playback_1, offset = 0
registered port alsa_pcm:playback_2, offset = 0
++ jack_rechain_graph():
client alsa_pcm: internal client, execution_order=0.
-- jack_rechain_graph()
cannot use real-time scheduling (FIFO at priority 24) [for thread
-1233609840, from thread -1233609840] (1: Operation not permitted)
19984 waiting for signals
late driver wakeup: nframes to process = 4096.
late driver wakeup: nframes to process = 4096.
late driver wakeup: nframes to process = 4096.
late driver wakeup: nframes to process = 4096.
late driver wakeup: nframes to process = 4096.
load = 0.0581 max usecs: 54.000, spare = 46385.000
delay of 46427.000 usecs exceeds estimated spare time of 46385.000;
restart ...
late driver wakeup: nframes to process = 4096.
delay of 46432.000 usecs exceeds estimated spare time of 46385.000;
restart ...
late driver wakeup: nframes to process = 4096.
late driver wakeup: nframes to process = 4096.
delay of 46474.000 usecs exceeds estimated spare time of 46385.000;
restart ...
delay of 46474.000 usecs exceeds estimated spare time of 46385.000;
restart ...
late driver wakeup: nframes to process = 4096.
jack main caught signal 2
starting server engine shutdown
stopping driver
delay of 46404.000 usecs exceeds estimated spare time of 46385.000;
restart ...
unloading driver
freeing shared port segments
stopping server thread
stopping watchdog thread
last xrun delay: 46404.000 usecs
max delay reported by backend: 46474.000 usecs
freeing engine shared memory
max usecs: 54.000, engine deleted
no message buffer overruns
cleaning up shared memory
cleaning up files
unregistering server `default'
--
Joakim Verona