All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@attbi.com>
To: Alsa-Devel <alsa-devel@lists.sourceforge.net>,
	Linux-Audio-User <linux-audio-user@music.columbia.edu>
Subject: Please explain Alsa Interface MIDI numbering PLEASE!
Date: 16 Feb 2003 10:52:23 -0800	[thread overview]
Message-ID: <1045421543.1370.15.camel@Godzilla> (raw)

[-- Attachment #1: Type: text/plain, Size: 1872 bytes --]

Hi,
   I'm having a great deal of confusion about how Alsa is handling my
MIDI hardware. This is spilling over into unintended consequences in
Rosegarden that I think none of us understand. Couple someone with some
background in this please explain? Thanks.

   I have two 2-port MIDI devices on this system. One is an RME HDSP
9652 with two MIDI ports, and the other is a hot pluggable MidiSport
2x2. I attach two screen shots of kaconnect, one with and one without
the 2x2 plugged in.

   My questions:

1) In the screen shot "without_2x2.png" I see two read ports and two
write ports. Please explain why they are called 

64:0 External MIDI 0
64:32 External MIDI 0

Why is my HDSP given the apparent name '64'? Why the :0 and :32? I would
have thought :0 and :16 would make more sense from a channel numbering
point of view, or :0 and :1 from an interface point of view. What's
going on?

2) In the screen shot "with_2x2.png" I've plugged in the MidiSport 2x2.
New devices show up in kaconnect. However, instead of showing 2 read
ports and 2 write ports, I am getting 4 read ports and no write ports.
Please explain why the MidiSport is given the names 

72:0 External MIDI 1
72:1 External MIDI 1
72:2 External MIDI 1
72:3 External MIDI 1

Shouldn't this be just :0 and :1 for both the read and write ports?

I get the feeling that BOTH of the drivers for these devices are hosed.
What's up with these things?

   I do not understand why Alsa gives these devices numbers in the first
place, nor how the numbers are assigned.

   How can I change the names that are displayed so that 

"64:0 External MIDI 0" shows the name "HDSP 9652 Port 1"

"64:32 External MIDI 0" shows the name "HDSP 9652 Port 2"

"72:0 External MIDI 1" shows the name "MidiSport 2x2 Port A"

"72:1 External MIDI 1" shows the name "MidiSport 2x2 Port B"

Thanks very, very much in advance,
Mark




[-- Attachment #2: with_2x2.png --]
[-- Type: image/png, Size: 5055 bytes --]

[-- Attachment #3: without_2x2.png --]
[-- Type: image/png, Size: 4698 bytes --]

             reply	other threads:[~2003-02-16 18:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-16 18:52 Mark Knecht [this message]
2003-02-17  9:21 ` Please explain Alsa Interface MIDI numbering PLEASE! Clemens Ladisch
2003-02-17 16:29   ` [linux-audio-user] " Mark Knecht
2003-02-17 18:07     ` Paul Davis
2003-02-17 20:40       ` Mark Knecht
     [not found] <E18kTvV-0001Ti-00@sc8-sf-list2.sourceforge.net>
2003-02-16 19:43 ` Pedro Lopez-Cabanillas
2003-02-16 19:46   ` Mark Knecht
2003-02-16 19:57     ` Mark Knecht
2003-02-16 20:33     ` Pedro Lopez-Cabanillas
2003-02-16 23:03       ` Mark Knecht
2003-02-16 23:30         ` Pedro Lopez-Cabanillas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1045421543.1370.15.camel@Godzilla \
    --to=markknecht@attbi.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=linux-audio-user@music.columbia.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.