16 Mar
2008
16 Mar
'08
6:01 p.m.
On Sun, 16 Mar 2008 14:15:43 -0400
Bill Allen <lau(a)ballen.fastmail.fm> wrote:
Bill Allen wrote:
I can't tell you how to verify anything, but the interface works
perfectly well with ubuntu (studio) gutsy and hardy as well. I also
tested it with musix, dyne:bolic and pure:dyne. The dynes require that
you type 'modprobe snd-usb-audio' afair.
I had some kind of problem with dyne:bolic but can't remember what it
was.
I really don't know what the problem could be.
I usually run this card at advanced and 48kHz, sound and midi works
fine.
I think my current standard parameters for jack are something like that:
/usr/bin/jackd -R -P70 -p128 -dalsa -dhw:1 -r48000 -p1024 -n3 -Xseq
This line is on gutsy with jack 0.109, I'd try it without -Xseq on
plain gutsy.
Best,
Philipp
I've got the Edirol UA20 and I am happy with
it as an audio device
(only 44.1 however), or as a midi device, but not both, sadly. If I
run it in "Advanced" mode, jack won't start up, but it shows up as
a midi device. If I run it with "Advanced" driver off, I can use it
as a midi device, but jack won't start up.
I've attached the lsusb -v for the device in advanced off and
advanced on modes. I'm not an expert, but in advanced off mode the
lsusb has several lines that indicate an audio streaming device,
where in advanced on it doesn't.
Regards,
Bill
After doing some googling, I see that this has been discussed on this
list before. It seems that Clemens put a fix in for it. I would
assume that any recent alsa has gotten that fix (usbquirks.h). I've
tried this on two very recent distros (Ubuntu rt and dyne:bolic) and
it exhibits the same problem. Maybe I've got a defective device. Is
there anything that I can check to verify that my distros have the
fix in them?
Regards,
Bill