13 Dec
2004
13 Dec
'04
4:07 p.m.
Stefan Turner wrote:
Since this has been mentioned, my US-122 doesn't
work
AT ALL using usx2y, but is fine with alsa. I am using
qjackctl 0.2.13 and Jack 0.99.0 (the most recent
versions AFAIK). All I get is:
17:47:12.866 JACK is starting...
17:47:12.867 /usr/bin/jackstart -R -dusx2y -dhw:1
-r44100 -p512 -n3 -H -M
17:47:12.873 JACK was started with PID=6369 (0x18e1).
back from read, ret = 1 errno == Success
jackd: unknown driver 'usx2y'
17:47:12.885 JACK was stopped with exit status=1.
17:47:14.885 Could not connect to JACK server as
client.
This doesn't bother me, unless there are meant to be
advantages of using usx2y?
Try using -p128 -n2, and tell us whether you can't notice any aural
difference, let alone if you can ignore a XRUN storm =:)
You need both the specific 'usx2y' backend driver patched into jackd,
*and* the new hwdep pcm (aka "rawusb") interface available on the
sand-usb-usx2y alsa kernel module. As Uwe did, you can look under
http://www.rncbc.org/usx2y/ for what fits you and try this out.
Cheers.
--
rncbc aka Rui Nuno Capela
rncbc(a)rncbc.org