Lee Revell wrote: >On Thu, 2005-01-20 at 17:00 +1100, Shayne O'Connor wrote: > > >>Lee Revell wrote: >> >> >> >>>QuickStart: >>> >>>$ jackd -R -v -d alsa -P hw:0,3 -C hw:0,2 -S >>> >>> >>> >>> >>here's what i get here: >> >>[mrmachine@localhost mrmachine]$ jackd -v -d alsa -P hw:0,3 -C hw:0,2 -S >>-i 2 -o 4 >> >> > >Lose the "-i 2 -o 4", and it will automatically open 16 capture and 16 >playback channels (like the default kX ASIO config). Unfortunately, >opening fewer channels than 16 is not supported yet. > > > still no go - [mrmachine@localhost mrmachine]$ jackd -v -d alsa -P hw:0,3 -C hw:0,2 -S getting driver descriptor from /usr/lib/jack/jack_oss.so getting driver descriptor from /usr/lib/jack/jack_alsa.so getting driver descriptor from /usr/lib/jack/jack_dummy.so jackd 0.99.36 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 JACK compiled with System V SHM support. server `default' registered loading driver .. registered builtin port type 32 bit float mono audio required capabilities not available capabilities: = cap_ipc_lock,cap_sys_nice,cap_sys_resource+e new client: alsa_pcm, id = 1 type 1 @ 0x8059a50 fd = -1 creating alsa driver ... hw:0,3|hw:0,2|1024|2|48000|0|0|nomon|swmeter|-|16bit ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode control device hw:0 configuring for 48000Hz, period = 1024 frames, buffer = 2 periods ALSA: cannot set period size to 1024 frames for capture ALSA: cannot configure capture channel cannot load driver module alsa starting server engine shutdown freeing shared port segments stopping server thread last xrun delay: 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' [mrmachine@localhost mrmachine]$ would my .asoundrc file be interfering? i have an sb live platinum, so maybe the device i need is different? >Also the wavetable problem is known and I am working on it. My goal is >basically the same as yours. Eventually the emu10k1 driver with ld10k1 >will offer all the features the kX driver does. > > is development of ld10k1 still happening? shayne
