From: Lee Revell <rlrevell@joe-job.com>
To: Clemens Ladisch <cladisch@fastmail.net>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Rawmidi device naming
Date: Thu, 09 Nov 2006 15:36:37 -0500 [thread overview]
Message-ID: <1163104597.16030.6.camel@mindpipe> (raw)
In-Reply-To: <1158948259.1036.271601876@webmail.messagingengine.com>
On Fri, 2006-09-22 at 20:04 +0200, Clemens Ladisch wrote:
> Lee Revell wrote:
> > # aplaymidi -l
> > Port Client name Port name
> > 64:0 Dreamchip MPU interface 1 Dreamchip MPU interface 1
> > 64:32 Dreamchip MPU interface 1 Dreamchip MPU interface 2
> >
> > Why do both ports get "Dreamchip MPU interface 1" for the client name?
>
> Because there is only one client.
>
> The client name comes from the card's shortname.
Sorry, but you are wrong - the client name does not come from the card's
shortname. The client gets the name of the first port registered.
I changed my code to:
212
213 if ((err = snd_dream_midi_init(dream, midi2, 1, "MIDI Out")) < 0)
214 return err;
215 midi2->port = MPU1_DATA;
216
217 if ((err = snd_dream_midi_init(dream, midi1, 0, "GM Synth")) < 0)
218 return err;
219 midi1->port = MPU1_DATA;
220
And now I get:
Port Client name Port name
64:0 GM Synth GM Synth
64:32 GM Synth MIDI Out
How can I name the client independently from the ports?
Lee
-------------------------------------------------------------------------
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
next prev parent reply other threads:[~2006-11-09 20:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-22 17:38 Rawmidi device naming Lee Revell
2006-09-22 18:04 ` Clemens Ladisch
2006-09-22 18:13 ` Lee Revell
2006-11-09 20:36 ` Lee Revell [this message]
2006-11-09 20:39 ` Lee Revell
2006-11-10 8:25 ` Clemens Ladisch
2006-11-10 17:54 ` Lee Revell
2006-11-10 19:08 ` Clemens Ladisch
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=1163104597.16030.6.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=cladisch@fastmail.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox