Re: [linux-audio-user] USX2Y rawusb mode

Ok, scratch what I said about it not crashing anymore. It's still
quite less than stable. I was using qjackctl, and it was fine
until I started pd, at which point my computer froze. So I
rebooted, and started jackd without qjackctl

sudo jackd -R -dalsa -dhw:0,0 -p1024 -n2 -i2 -o2

and was using it fine for a while, I started pd without problems,
then I was trying to figure out how to connect to the midi port
of PD when the following appeared on /var/log/mesages:

Feb 26 22:26:10 slingshot kernel: ALSA /usr/src/alsa/ \
alsa-driver-1.0.8/alsa-kernel/usb/usx2y/usbusx2yaudio.c:199: \
usb_submit_urb() returned -11

and at about the same time, jackd reported a bunch of xruns and
then:

subgraph starting at pure_data_0 timed out (subgraph_wait_fd=9, \
status = 0, state = Triggered)

**** alsa_pcm: xrun of at least 17.389 msecs

jackd watchdog: timeout - killing jackd
Killed

apon closer reading of the responses to my earlier question about
getting capture channels 3 and 4 to work, it looks like there're
2 different usx2y drivers? I'm using whatever came with alsa
1.0.8, and the changelog says that they include rawusb support,
so I think I'm using the correct one. But it'd be kinda nice if
I'm not, cause that's an easy fix.

-spencer

On Sat, Feb 26, 2005 at 09:55:59PM -0500, Spencer Russell wrote:
> So my US428 was working pretty well on my rackmount computer, but
> with that motherboard fried, I'm now back to using my laptop. For
> some reason my US428 doesn't like my laptop very much. One thing
> that seemed to be a problem was that here was some sort of
> qjackctl conflict with the non-multithreaded QT libs, so I
> installed the multithreaded ones, recompiled, and at least my
> computer is no longer crashing whenever I start start jackd from
> qjackctl with my us428. However, I'm getting more xruns than I
> think I should, and it might be beacuse I think I'm not using the
> rawusb mode. Seems that I need to use -dhw0,2 to use rawusb mode,
> but when I try that, I get
>
> ALSA/USX2Y: Cannot open hwdep device "hw:0,1"
>
> It should be located at hw:0,0, I think, but I'm not sure how to
> specify that. Any ideas?
>
> thanks,
> spencer
Received on Sun Feb 27 08:15:07 2005