Am Donnerstag 06 April 2006 23:01 schrieben Sie: >Please keep the bugreport in CC. > >On Thu, 2006-04-06 at 20:41 +0200, Ralf Philipp wrote: >> jackd -R -v -d alsa usx2y -d hw:1 >> Sorry. The audio interface "hw:1" doesn't support any of the hardware >> sample formats that JACK's alsa-driver can use. > >Ok. What does > >jackd -dalsa -dhw:1 -r44100 -p1024 -n2 > >result in? Or another rate that is definitely supported by the card >(maybe even 96000).
I've done all of this. No success. > >> I also tried the cvs-version of jackd without better doing. >> >> Maybe I do silly things at the command-line or there are problems with >> the architecture. > >Maybe. > >If the above command results in the same problem, you might want to try >the patch mentioned in: >http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=331420 >But I'm not really sure it will help you at all. > >What you might want to do as an alternative of looking the correct >sampling rate is putting a alsa plughw plugin in between the device and >jack. Options sound like "-dalsa -dplughw:1 -r48000". This one is working with different sampling rates, i.e. 44100 and 48000. Best with ardour is ... jackd -v -dalsa -dplughw:1 -r44100 -p512 getting driver descriptor from /usr/lib/libjack0.100.0-0/jack_alsa.so getting driver descriptor from /usr/lib/libjack0.100.0-0/jack_dummy.so getting driver descriptor from /usr/lib/libjack0.100.0-0/jack_oss.so jackd 0.100.7 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 loading driver .. apparent rate = 44100 creating alsa driver ... plughw:1|plughw:1|512|2|44100|0|0|nomon|swmeter|-| 32bit control device hw:1 configuring for 44100Hz, period = 512 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 nperiods = 2 for capture 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 nperiods = 2 for playback registered builtin port type 32 bit float mono audio required capabilities not available capabilities: = cap_ipc_lock,cap_sys_nice,cap_sys_resource+ep new client: alsa_pcm, id = 1 type 1 @ 0x10023a88 fd = -1 new buffer size 512 registered port alsa_pcm:capture_1, offset = 2048 registered port alsa_pcm:capture_2, offset = 4096 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() But there are some cracklings. The same with -dhw:1 did not work. jackd -v -dalsa -dhw:1 -r44100 -p512 getting driver descriptor from /usr/lib/libjack0.100.0-0/jack_alsa.so getting driver descriptor from /usr/lib/libjack0.100.0-0/jack_dummy.so getting driver descriptor from /usr/lib/libjack0.100.0-0/jack_oss.so jackd 0.100.7 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 loading driver .. apparent rate = 44100 creating alsa driver ... hw:1|hw:1|512|2|44100|0|0|nomon|swmeter|-|32bit control device hw:1 configuring for 44100Hz, period = 512 frames, buffer = 2 periods Note: audio device hw:1 doesn't support a 32bit sample format so JACK will try a 24bit format instead Note: audio device hw:1 doesn't support a 24bit sample format so JACK will try a 16bit format instead Sorry. The audio interface "hw:1" doesn't support any of the hardware sample formats that JACK's alsa-driver can use. ALSA: cannot configure capture channel cannot load driver module alsa registered builtin port type 32 bit float mono audio required capabilities not available capabilities: = cap_ipc_lock,cap_sys_nice,cap_sys_resource+ep new client: alsa_pcm, id = 1 type 1 @ 0x10023a88 fd = -1 starting server engine shutdown freeing shared port segments stopping server thread last xrun delay: 0.000 usecs max delay reported by backend: 0.000 usecs freeing engine shared memory max usecs: 0.000, engine deleted no message buffer overruns cleaning up shared memory cleaning up files unregistering server `default' Is this case hopeless? Thanks for your help. Ralf > >Otherwise I'm out of suggestions. You might want to try asking the >jackit developers. > > Robert. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
