> The issues might be fixed, or worked aroud, but they might still be > unreleased. well, it's nice that this issue has been solved ... i was really annoyed by restarting alsa about a hundret times before i could perform ... but this is another problem ... using alsa's hw layer i get the following result: Sorry. The audio interface "hw:0" doesn't support any of the hardware sample formats that JACK's alsa-driver can use. using alsa's plug layer (asoundrc file from the alsa website) quattro1 / quattro2: Sorry. The audio interface "quattro1" doesn't support any of the hardware sample formats that JACK's alsa-driver can use. Sorry. The audio interface "quattro2" doesn't support any of the hardware sample formats that JACK's alsa-driver can use. quattro: ALSA: mmap-based access is not possible for the capture stream of this audio interface q4: bash-2.05b# jackd -v -d alsa -d q4 getting driver descriptor from /usr/lib/jack/jack_portaudio.so getting driver descriptor from /usr/lib/jack/jack_dummy.so getting driver descriptor from /usr/lib/jack/jack_alsa.so jackd 0.94.0 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 @ 0x8057f18 fd = -1 creating alsa driver ... q4|q4|1024|2|48000|0|0|nomon|swmeter|rt|32bit configuring for 48000Hz, period = 1024 frames, buffer = 2 periods You appear to be using the ALSA software "plug" layer, probably a result of using the "default" ALSA device. This is less efficient than it could be. Consider using a hardware device instead rather than using the plug layer. Usually the name of the hardware device that corresponds to the first soun You appear to be using the ALSA software "plug" layer, probably a result of using the "default" ALSA device. This is less efficient than it could be. Consider using a hardware device instead rather than using the plug layer. Usually the name of the hardware device that corresponds to the first soun ALSA lib pcm.c:1178:(snd_pcm_link) SNDRV_PCM_IOCTL_LINK failed: Operation already in progress new buffer size 1024 registered port alsa_pcm:capture_1, offset = 4096 registered port alsa_pcm:capture_2, offset = 8192 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() 32199 waiting for signals load = 0.2180 max usecs: 93.000, spare = 21240.000 new client: pure_data_0, id = 2 type 2 @ 0x40025000 fd = 14 registered port pure_data_0:input0, offset = 0 registered port pure_data_0:input1, offset = 0 registered port pure_data_0:output0, offset = 12288 registered port pure_data_0:output1, offset = 16384 ++ jack_rechain_graph(): client alsa_pcm: internal client, execution_order=0. client pure_data_0: start_fd=5, execution_order=0. client pure_data_0: wait_fd=13, execution_order=1 (last client). -- jack_rechain_graph() connect alsa_pcm:capture_1 and pure_data_0:input0 ++ jack_rechain_graph(): client alsa_pcm: internal client, execution_order=0. client pure_data_0: start_fd=5, execution_order=0. client pure_data_0: wait_fd=13, execution_order=1 (last client). -- jack_rechain_graph() connect alsa_pcm:capture_2 and pure_data_0:input1 ++ jack_rechain_graph(): client alsa_pcm: internal client, execution_order=0. client pure_data_0: start_fd=5, execution_order=0. client pure_data_0: wait_fd=13, execution_order=1 (last client). -- jack_rechain_graph() connect pure_data_0:output0 and alsa_pcm:playback_1 ++ jack_rechain_graph(): client alsa_pcm: internal client, execution_order=0. client pure_data_0: start_fd=5, execution_order=0. client pure_data_0: wait_fd=13, execution_order=1 (last client). -- jack_rechain_graph() connect pure_data_0:output1 and alsa_pcm:playback_2 ++ jack_rechain_graph(): client alsa_pcm: internal client, execution_order=0. client pure_data_0: start_fd=5, execution_order=0. client pure_data_0: wait_fd=13, execution_order=1 (last client). -- jack_rechain_graph() could not complete playback of 1024 frames: error = -32 cycle execution failure, exiting DRIVER NT: could not run driver cycle jack main caught signal 12 stopping driver detaching driver DIS-connect alsa_pcm:capture_1 and pure_data_0:input0 DIS-connect alsa_pcm:capture_2 and pure_data_0:input1 DIS-connect pure_data_0:output0 and alsa_pcm:playback_1 DIS-connect pure_data_0:output1 and alsa_pcm:playback_2 unloading driver q4b: Sorry. The audio interface "q4b" doesn't support any of the hardware sample formats that JACK's alsa-driver can use. the only way i am able to play a sound using jack is when i use jack in -R mode with q4 or plughw:0: but i've only got 2 channels and the output is heavily distorted ... using the portaudio layer, i can only access the first 2 channels (/dev/dsp0) but not the second 2 (/dev/adsp0) ... i must admit ... it's not that easy to handle the quattro with linux ... cheers... Tim mailto:TimBlechmann@xxxxxx ICQ: 96771783 -- The only people for me are the mad ones, the ones who are mad to live, mad to talk, mad to be saved, desirous of everything at the same time, the ones who never yawn or say a commonplace thing, but burn, burn, burn, like fabulous yellow roman candles exploding like spiders across the stars and in the middle you see the blue centerlight pop and everybody goes "Awww!" Jack Kerouac
