Hi,
I have the very same problem with version 1.0.18rc3.
Is it really a bug which makes alsa jack plugin unusable at all, or just
some misconfiguration on my side?
some verbose output from the jack server:
ivanszky@i2:~$ jackd -v -r -d alsa hw:0 -r 44100
jackd 0.118.0
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn
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
Memory locking is unlimited - this is dangerous. You should probably
alter the line:
@audio - memlock unlimited
in your /etc/limits.conf to read:
@audio - memlock 776928
getting driver descriptor from /usr/lib/jack/jack_firewire.so
no message buffer overruns
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
getting driver descriptor from /usr/lib/jack/jack_net.so
getting driver descriptor from /usr/lib/jack/jack_oss.so
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
start poll on 3 fd's
loading driver ..
new client: alsa_pcm, id = 1 type 1 @ 0x8059688 fd = -1
apparent rate = 44100
creating alsa driver ... hw:0|hw:0|1024|2|44100|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 44100Hz, period = 1024 frames (23.2 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 2 periods for playback
new buffer size 1024
registered port system:capture_1, offset = 4096
registered port system:capture_2, offset = 8192
registered port system:playback_1, offset = 0
registered port system:playback_2, offset = 0
registered port system:playback_3, offset = 0
registered port system:playback_4, offset = 0
registered port system:playback_6, offset = 0
++ jack_sort_graph
++ jack_rechain_graph():
+++ client is now alsa_pcm active ? 1
client alsa_pcm: internal client, execution_order=0.
-- jack_rechain_graph()
9262 waiting for signals
load = 0.0108 max usecs: 5.000, spare = 23214.000
load = 0.0205 max usecs: 7.000, spare = 23212.000
load = 0.0684 max usecs: 27.000, spare = 23192.000
load = 0.0450 max usecs: 5.000, spare = 23214.000
load = 0.0483 max usecs: 12.000, spare = 23207.000
load = 0.0371 max usecs: 6.000, spare = 23213.000
load = 0.0293 max usecs: 5.000, spare = 23214.000
server thread back from poll
new client: alsa-jack.pcm.jackP.9274.0, id = 2 type 2 @ 0xb7605000 fd = 12
start poll on 4 fd's
server thread back from poll
new client alsa-jack.pcm.jackP.9274.0 using 13 for events
start poll on 4 fd's
server thread back from poll
marking client alsa-jack.pcm.jackP.9274.0 with SOCKET error state = Not
triggered errors = 0
trying to lock graph to remove 1 problems
we have problem clients (problems = 1
++ Removing failed clients ...
client alsa-jack.pcm.jackP.9274.0 error status 10000000
removing failed client alsa-jack.pcm.jackP.9274.0 state = Not triggered
errors = 10000000
removing client "alsa-jack.pcm.jackP.9274.0"
removing client "alsa-jack.pcm.jackP.9274.0" from the processing chain
+++ deactivate alsa-jack.pcm.jackP.9274.0
client alsa_pcm error status 0
++ jack_sort_graph
++ jack_rechain_graph():
+++ client is now alsa_pcm active ? 1
client alsa_pcm: internal client, execution_order=0.
-- jack_rechain_graph()
-- jack_sort_graph
-- Removing failed clients ...
after removing clients, problems = 0
start poll on 3 fd's
load = 0.0254 max usecs: 5.000, spare = 23214.000
thanks,
Gabor
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Alsa-user mailing list
Alsa-user@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/alsa-user
