New subject: [Alsa-devel] [Alsa-user] [linux-audio-user] Re: More Midisport 2x2 troubles (help from the Alsa developers is greatly appreciated!)

3 Apr 2003

Hmm, I've tried running the alsa-lib/test/ramidi test and tried using it
as:

rawmidi -i hw:2,0

This starts it up but I don't get any events in. Can anyone tell me why?

Any other setting (i.e. hw:2,1) reports an error that such a device was
not found.

Interesting thing is that when I do ./rawmidi -o hw:2,0 I get the
note-on/off signal on the midisport, which means that the send part of
it works ok.

However, when I do -i nothing comes into the cpu.
Same is with the ./rawmidi -I /dev/midi2 (there are no errors, but no
input either).

cat /dev/midi2 works just fine.

My /dev/snd/ only has 1 midi device (midiC2D0), so it does seem like
it's a problem with Alsa.

Running latency in the same dir freezes the machine with a loud sound
going on.

I am using MDK 9.1 on Inspiron 8200. Any help is greatly appreciated!

Any other suggestions?

Ico

...
  -----Original Message-----
 From: aezr4(a)studcom.urz.uni-halle.de [mailto:aezr4@studcom.urz.uni-
 halle.de] On Behalf Of Clemens Ladisch
 Sent: Thursday, April 03, 2003 9:50 AM
 To: Ivica Bukvic
 Cc: alsa-devel(a)lists.sourceforge.net
 Subject: Re: [Alsa-devel] Re: More Midisport 2x2 troubles

 Ivica Bukvic wrote:
 > However, I am a bit confused, since this feature with /dev/midi stuff
...
   worked like a
charm just a couple weeks ago (ver. 0.9.1). So, did
 something change dramatically since?  
 No. The USB MIDI driver has behaved in this way since 0.9.0rc4.

 > Can you also point me in the right direction where I can see a simple
...
   ALSA code to
accessing the both of the MIDI raw ports?  
 alsa-lib/test/rawmidi.c does some operations with both OSS and ALSA ports.
...
  When using two ports, you'd call
snd_rawmidi_open() twice and then have
...
  two handles, similar to two file handles.
 alsa-lib/test/control.c enumerates rawmidi devices.

 BTW: Are you soure you want to use rawmidi ports? Many software
 synthesizers create sequencer ports only.

 > P.S. One thing I just realized is that there is something rather unclear
...
  > to me in the explanation generously provided by
Clemens:
 >
 > > /dev/midi0  -> card 0, device 0, subdevice 0
 > > /dev/amidi0 -> card 0, device 1, subdevice 0
 > > /dev/midi1  -> card 1, device 0, subdevice 0
 > > /dev/amidi1 -> card 1, device 1, subdevice 0
 > > /dev/midi2  -> card 2, device 0, subdevice 0
 > > /dev/amidi2 -> card 2, device 1, subdevice 0
 >
 > since none of the amidi devices does not work on my setup (see my last
...
   e-mail for
more info) and it seems as if it should.  
 Your two ports are subdevices 0 and 1 of card 1, device 0.
 /dev/amidi1 points to device 1 which doesn't exist.

 > Furthermore, what happens when the midi interface has more than 2 I/O
...
   ports? 

 If the ports are subdevices of one device, only the first can be accessed
...
  with the OSS /dev/midiX file.
 If each port is a seperate device, the first two ports can be accessed
 with /dev/midiX and /dev/amidiX.

 Drivers for multiport interfaces usually use the first alternative (one
...
  device with subdevices) because there is a limit of 8
rawmidi devices per
...
  card.

 HTH
 Clemens