[linux-audio-user] USB midi Setup

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Strange. Is the snd-seq-midi module loaded?

[root@Kesh linux]# lsmod
Module                  Size  Used by
snd_virmidi             3968  0 
snd_seq_virmidi         8672  1 snd_virmidi
snd_seq_midi_event      8896  1 snd_seq_virmidi
snd_seq                71480  2 snd_seq_virmidi,snd_seq_midi_event
evdev                  11680  2 
snd_usb_audio          81632  0 
snd_rawmidi            30592  2 snd_seq_virmidi,snd_usb_audio
snd_seq_device         10184  2 snd_seq,snd_rawmidi

Do the UM-2's ports appear in /proc/asound/UM2/midi0?
[root@Kesh linux]# cat /proc/asound/UM2/midi0 
UM-2

Output 0
  Tx bytes     : 0
Output 1 
  Tx bytes     : 0
Input 0
  Rx bytes     : 0
Input 1
  Rx bytes     : 0

In /proc/asound/seq/clients?
[root@Kesh linux]# cat /proc/asound/seq/clients
Client info
  cur  clients : 5
  peak clients : 5
  max  clients : 192

Client   0 : "System" [Kernel]
  Port   0 : "Timer" (Rwe-)
  Port   1 : "Announce" (R-e-)
Client  80 : "Virtual Raw MIDI 2-0" [Kernel]
  Port   0 : "VirMIDI 2-0" (RWeX)
Client  81 : "Virtual Raw MIDI 2-1" [Kernel]
  Port   0 : "VirMIDI 2-1" (RWeX)
Client  82 : "Virtual Raw MIDI 2-2" [Kernel]
  Port   0 : "VirMIDI 2-2" (RWeX)
Client  83 : "Virtual Raw MIDI 2-3" [Kernel]
  Port   0 : "VirMIDI 2-3" (RWeX)

In the output of "aplaymidi -l"?

[root@Kesh linux]# aplaymidi -l
 Port    Client name                      Port name
 80:0    Virtual Raw MIDI 2-0             VirMIDI 2-0
 81:0    Virtual Raw MIDI 2-1             VirMIDI 2-1
 82:0    Virtual Raw MIDI 2-2             VirMIDI 2-2
 83:0    Virtual Raw MIDI 2-3             VirMIDI 2-3


Does this answer any questions ?

Thanks,
Elias

---------------------------------------------------------------------------------------------
Clemens Ladisch wrote:

>Elias Kesh (P) wrote:
>  
>
>>I'm trying to get my Roland UM-2 usb to midi interface working on the
>>2.6.4 kernel. I have the kernels usb midi and usb audio turned off. The
>>alsa usb audio driver is a module.
>>I can access the device via /dev/midi01 meaning if I cat a midi file the
>>lights on the interface blink.
>>    
>>
>
>The /dev/midi0X files are for raw MIDI data. To play midi files, use
>some program like aplaymidi or playmidi or pmidi.
>
>  
>
>>Mar 14 07:55:09 Kesh kernel: ALSA sound/usb/usbmidi.c:782: created 2
>>output and 2 input ports
>>    
>>
>
>Fine.
>
>  
>
>>[root@Kesh /]# cat /proc/asound/oss/sndstat
>>...
>>Card config:
>>EDIROL UM-2 at usb-0001:01:1b.0-1
>>...
>>Midi devices:
>>1: UM-2
>>    
>>
>
>OK.
>
>  
>
>>[root@Kesh src]# aconnect -lo
>>client 80: 'Virtual Raw MIDI 2-0' [type=kernel]
>>    0 'VirMIDI 2-0     '
>>client 81: 'Virtual Raw MIDI 2-1' [type=kernel]
>>    0 'VirMIDI 2-1     '
>>client 82: 'Virtual Raw MIDI 2-2' [type=kernel]
>>    0 'VirMIDI 2-2     '
>>client 83: 'Virtual Raw MIDI 2-3' [type=kernel]
>>    0 'VirMIDI 2-3     '
>>    
>>
>
>Strange. Is the snd-seq-midi module loaded?
>Do the UM-2's ports appear in /proc/asound/UM2/midi0?
>In /proc/asound/seq/clients?
>In the output of "aplaymidi -l"?
>
>
>Regards,
>Clemens
>
>
>  
>

[Index of Archives]     [Linux Sound]     [ALSA Users]     [Pulse Audio]     [ALSA Devel]     [Sox Users]     [Linux Media]     [Kernel]     [Photo Sharing]     [Gimp]     [Yosemite News]     [Linux Media]

  Powered by Linux