On Sun, 2007-09-16 at 16:23 +0200, Svend-Erik Kjær Madsen wrote: > Does anyone know how to manage one of these cards, I've bought a used > one and put it in my computer without having the ADAT interface, I have > ordered one and hope to get it tomorrow, but I wasn't able to start Jack > and got the error message that jack couldn't find a propper recording > channel. I removed the card again so I can't give you the exact error > text. I have a similar problem with my 96/8 PAD, which is also second-hand. ALSA seems to work fine - I managed to use Hydrogen successfully with AlSA output. The card also worked recently in a Windows machine. >From a discussion on the PlanetCCRMA list, it seems likely that JACK settings need to be set to something unusual. > By the way I'm running UbuntuStudio. I'm running PlanetCCRMA on FC6. This is the message output that I get: 16:42:29.332 Startup script... 16:42:29.332 artsshell -q terminate JACK tmpdir identified as [/dev/shm] 16:42:29.756 Startup script terminated with exit status=256. 16:42:29.770 JACK is starting... 16:42:29.770 jackd -v -R -dalsa -r48000 -p1024 -n2 -D -Chw:1 -Phw:1 -H 16:42:29.772 JACK was started with PID=9326 (0x246e). getting driver descriptor from /usr/lib/jack/jack_alsa.so getting driver descriptor from /usr/lib/jack/jack_dummy.so getting driver descriptor from /usr/lib/jack/jack_freebob.so getting driver descriptor from /usr/lib/jack/jack_oss.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 loading driver .. Enhanced3DNow! detected SSE2 detected apparent rate = 48000 creating alsa driver ... hw:1|hw:1|1024|2|48000|0|0|hwmon|swmeter|-| 32bit control device hw:1 registered builtin port type 32 bit float mono audio registered builtin port type 8 bit raw midi clock source = system clock via clock_gettime new client: alsa_pcm, id = 1 type 1 @ 0x805b008 fd = -1 configuring for 48000Hz, period = 1024 frames, buffer = 2 periods ALSA: final selected sample format for capture: 32bit little-endian ALSA: use 8 periods for capture ALSA: final selected sample format for playback: 32bit little-endian ALSA: use 8 periods for playback 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() 9326 waiting for signals 16:42:31.788 Server configuration saved to "/home/nels/.jackdrc". 16:42:31.806 Statistics reset. 16:42:32.516 Client activated. 16:42:32.518 Audio connection change. 16:42:32.525 Audio connection graph change. JACK tmpdir identified as [/dev/shm] Enhanced3DNow! detected SSE2 detected new client: qjackctl-9322, id = 2 type 2 @ 0xb6c86000 fd = 15 ++ jack_rechain_graph(): client alsa_pcm: internal client, execution_order=0. client qjackctl-9322: start_fd=7, execution_order=0. client qjackctl-9322: wait_fd=11, execution_order=1 (last client). -- jack_rechain_graph() 16:42:32.549 XRUN callback (1). 16:42:34.533 XRUN callback (45 skipped). jackd watchdog: timeout - killing jackd 16:42:35.164 Shutdown notification. 16:42:35.165 Client deactivated. 16:42:35.166 JACK was stopped successfully. 16:42:35.166 Post-shutdown script... 16:42:35.166 killall jackd zombified - calling shutdown handler cannot send request type 7 to server cannot read result for request type 7 from server (Broken pipe) cannot send request type 7 to server cannot read result for request type 7 from server (Broken pipe) jackd: no process killed 16:42:35.418 Post-shutdown script terminated with exit status=256. Fernando at CCRMA suggested this: > Well, the message says "use 8 periods for capture and playback" so > that's what I would try. I seem to vaguely remeber something about the > 96/8 that was like this, it had a weird setting for periods or buffer or > something like that. Start with periods=8 and see what it tells you (you > may need to get the buffer down). When I tried this, JACK started successfully, but I got many xruns. Does anyone know the appropriate settings to use? Thanks Michael _______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/mailman/listinfo.cgi/linux-audio-user