On Fri Apr 17 17:25 , Clemens Ladisch sent:
immanuel litzroth wrote:
Apr 13 12:08:39 voodochile kernel: [ 169.622067] usb 2-10: new full speed
USB device using ohci_hcd and address 5
Apr 13 12:08:39 voodochile kernel: [ 169.844566] usb 2-10: configuration #1
chosen from 1 choice
Apr 13 12:08:39 voodochile kernel: [ 169.847594] snd-usb-audio: probe of
2-10:1.0 failed with error -5
Apr 13 12:08:39 voodochile kernel: [ 169.847616] snd-usb-audio: probe of
2-10:1.1 failed with error -5
Apr 13 12:08:44 voodochile kernel: [ 174.656857] usb 2-9: new full speed
USB
device using ohci_hcd and address 6
Apr 13 12:08:44 voodochile kernel: [ 174.879643] usb 2-9: configuration #1
chosen from 1 choice
Apr 13 12:08:44 voodochile kernel: [ 174.882987] snd-usb-audio: probe of
2-9:1.0 failed with error -5
Apr 13 12:08:44 voodochile kernel: [ 174.883013] snd-usb-audio: probe of
2-9:1.1 failed with error -5
What's up with that?
I'd guess the driver doesn't claim all the interfaces that the device
has. This shouldn't matter.
Then if I do and aplaymidi -l it lists the following ports:
40:0AMT8 AMT8 MIDI 1
40:1AMT8 AMT8 MIDI 2
40:2AMT8 AMT8 MIDI 3
40:3AMT8 AMT8 MIDI 4
40:4AMT8 AMT8 MIDI 5
40:5AMT8 AMT8 MIDI 6
40:6AMT8 AMT8 MIDI 7
40:7AMT8 AMT8 MIDI 8
40:8AMT8 AMT8 Broadcast
44:0AMT8 AMT8 MIDI 1
44:1AMT8 AMT8 MIDI 2
44:2AMT8 AMT8 MIDI 3
44:3AMT8 AMT8 MIDI 4
44:4AMT8 AMT8 MIDI 5
44:5AMT8 AMT8 MIDI 6
44:6AMT8 AMT8 MIDI 7
44:7AMT8 AMT8 MIDI 8
44:8AMT8 AMT8 Broadcast
Is it possible to have other names generated for these ports through
some magic?
You could add some entries to the snd_usbmidi_port_info array in the
driver source ...
Preferably each port would be named after the synth connected to it.
Changing port names at runtime isn't supported by the driver.
Then when I play the devices I get messages in /var/log/messages saying
Apr 11 23:03:56 voodochile kernel: [14700.085974] rtc: lost 28 interrupts
Apr 11 23:04:26 voodochile kernel: [14730.054964] rtc: lost 28 interrupts
Apr 11 23:04:56 voodochile kernel: [14760.023963] rtc: lost 28 interrupts
What's up with that?
Every thirty seconds, something on your computer eats some CPU and
disables all interrupts for about 27 milliseconds. If you have a laptop,
this it probably some fan control or power management stuff done by the
BIOS.
Best regards,
Clemens
I have one of these and a Unitor 8 MK II, I don't experience this problem at
all.. but it is on a desktop
--
Stay on top of everything new and different, both inside and
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today.
Use priority code J9JMT32. http://p.sf.net/sfu/p
___
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user
