From: Takashi Iwai <tiwai@suse.de>
To: Jaroslav Kysela <perex@suse.cz>
Cc: Pedro Lopez-Cabanillas <plcl@telefonica.net>,
"alsa-devel@lists.sourceforge.net"
<alsa-devel@lists.sourceforge.net>,
Clemens Ladisch <clemens@ladisch.de>
Subject: Re: MIDI port names
Date: Thu, 20 Feb 2003 15:38:53 +0100 [thread overview]
Message-ID: <s5h8ywbf24i.wl@alsa2.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0302201514060.1266-100000@pnote.perex-int.cz>
At Thu, 20 Feb 2003 15:14:45 +0100 (CET),
Jaroslav wrote:
>
> If there is a way to determine the connection between sequencer port and
> rawmidi device, I'm ok with any solution. Otherwise, please, solve this
> problem.
one of the advantages of the sequencer is that it hides the lowlevel
implementations, regardless of mpu401 or wavetable. hence, there
is no explicit link between the lowlevel device and the sequencer
client/port, so far. there are only bit flags indicating what kind of
functions are supported by the port.
it's not bad to have such an attribute, though. but if we have that,
it will be an addition.
Takashi
-------------------------------------------------------
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
next prev parent reply other threads:[~2003-02-20 14:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E18lUe8-0003K3-00@sc8-sf-list2.sourceforge.net>
2003-02-19 23:46 ` MIDI port names Pedro Lopez-Cabanillas
2003-02-20 8:55 ` Jaroslav Kysela
2003-02-20 10:57 ` Takashi Iwai
2003-02-20 14:14 ` Jaroslav Kysela
2003-02-20 14:38 ` Takashi Iwai [this message]
2003-02-20 20:19 ` Jaroslav Kysela
2003-02-25 16:11 ` Takashi Iwai
2003-02-20 19:55 ` Pedro Lopez-Cabanillas
2003-02-19 12:40 Paul Davis
2003-02-19 13:46 ` Takashi Iwai
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=s5h8ywbf24i.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=clemens@ladisch.de \
--cc=perex@suse.cz \
--cc=plcl@telefonica.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 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.