Howdies Just to let you all know that I finally found the problem. The unit mysteriously stopped responding again, and in amongst rebooting, starting, stopping, rmmodding, tearing my hair out, cursing, modprobing, plugging it into a windows box, trying to find a windows program to do the equivalent of "cat /dev/snd/midiC2D0 >aaaaaargh.mid" I discovered that if the metal sleeve around the USB plub for the device touched the metal around the USB socket in the device, it would restart itself. Hmm. Odd.
Then I noticed that in some cases I got a small shock if I touched the metal on the usb cable plug. So it looks like my hardware somehow develops a charge on the usb cable which prevents the unit from receiving data, and as soon as I discharge it the unit reacts to incoming messages. OTOH, I've been thinking that if ALSA can't send a message to a usb device, surely it should do something more, er, catastrophic than logging "urb status -32" to the kernel log? Should I log this as an ALSA bug? bye John Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Alsa-user mailing list Alsa-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/alsa-user
