Re: [Alsa-user] Alsa Delta66 and Jack no work :(

[Fernando Lopez-L. <na...@cc...>]

On Fri, 2004-12-03 at 15:38, Chris Olsen wrote:
> chris@linux:~>  jackd -v -d alsa -d hw
> getting driver descriptor from
> /usr/lib/jack/jack_dummy.so
> getting driver descriptor from
> /usr/lib/jack/jack_oss.so
> getting driver descriptor from
> /usr/lib/jack/jack_alsa.so
> jackd 0.98.1
> Copyright 2001-2003 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
> 
> registered builtin port type 32 bit float mono audio
> loading driver ..
> new client: alsa_pcm, id = 1 type 1 @ 0x8057868 fd =
> -1
> creating alsa driver ...
> hw|hw|1024|2|48000|0|0|nomon|swmeter|-|32bit
> configuring for 48000Hz, period = 1024 frames, buffer
> = 2 periods
> new buffer size 1024
> registered port alsa_pcm:capture_1, offset = 4096
> registered port alsa_pcm:capture_2, offset = 8192
> registered port alsa_pcm:capture_3, offset = 12288
> registered port alsa_pcm:capture_4, offset = 16384
> registered port alsa_pcm:capture_5, offset = 20480
> registered port alsa_pcm:capture_6, offset = 24576
> registered port alsa_pcm:capture_7, offset = 28672
> registered port alsa_pcm:capture_8, offset = 32768
> registered port alsa_pcm:capture_9, offset = 36864
> registered port alsa_pcm:capture_10, offset = 40960
> registered port alsa_pcm:capture_11, offset = 45056
> registered port alsa_pcm:capture_12, offset = 49152
> registered port alsa_pcm:playback_1, offset = 0
> registered port alsa_pcm:playback_2, offset = 0
> registered port alsa_pcm:playback_3, offset = 0
> registered port alsa_pcm:playback_4, offset = 0
> registered port alsa_pcm:playback_5, offset = 0
> registered port alsa_pcm:playback_6, offset = 0
> registered port alsa_pcm:playback_7, offset = 0
> registered port alsa_pcm:playback_8, offset = 0
> registered port alsa_pcm:playback_9, offset = 0
> registered port alsa_pcm:playback_10, offset = 0
> ++ jack_rechain_graph():
> client alsa_pcm: internal client, execution_order=0.
> -- jack_rechain_graph()
> 10801 waiting for signals
> load = 0.0164 max usecs: 7.000, spare = 21326.000
> load = 0.0363 max usecs: 12.000, spare = 21321.000
> load = 0.0393 max usecs: 9.000, spare = 21324.000
> load = 0.0360 max usecs: 7.000, spare = 21326.000
> load = 0.0368 max usecs: 8.000, spare = 21325.000
> load = 0.0489 max usecs: 13.000, spare = 21320.000
> load = 0.0432 max usecs: 8.000, spare = 21325.000
> load = 0.0614 max usecs: 17.000, spare = 21316.000
> 
> And on and on....

Jack is definitely running. 

Try the jack_lsp example client, I don't know if it comes with SuSE. If
it lists all the ports then you are fine with regards to jack (that is,
the server is running, and clients can connect to it). 

Have you installed jack manually? Or did it come with SuSE? Which
version? Same for the applications you are trying to use. Are they
packaged apps that came with SuSE? At this point I'd say that you are
either not using the apps that you think you are using, or in the case
of apps that support multiple audio i/o backends, they have not been
configured to work with jack and are trying alsa or oss. 

-- Fernando