From: Chris Cannam <cannam@all-day-breakfast.com>
To: Drake Wilson <drake@libcom.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Sequencer documentation follow-up
Date: Mon, 30 Jun 2003 16:12:12 +0100 [thread overview]
Message-ID: <3F00534C.7060706@all-day-breakfast.com> (raw)
In-Reply-To: s5hof0fljw0.wl@alsa2.suse.de
Takashi Iwai wrote:
> At Sun, 8 Jun 2003 22:06:30 -0400,
> Drake Wilson wrote:
>
>>... I have a draft, or part thereof. It is in similar spirit to the
>>module overviews in the API reference, and I hope it to be of some
>>use, if not optimal.
>>[...]
I missed this until now. Just to add that the meanings of the
various SND_SEQ_PORT_TYPE flags were covered in a discussion on
this list a few weeks ago.
It seems that the SND_SEQ_PORT_TYPE_* flags describe the sort of
events that a port understands and not necessarily what it does
with them. The discussion here arose from a desire to query
these flags in order to attempt to distinguish MIDI soft synths
and on-card hardware synths from other MIDI applications such as
sequencers: it turns out that this is not possible.
For example, I believe it turned out that PORT_TYPE_APPLICATION
indicates a port expecting application-specific events, not just
a port that happens to belong to a software application. That is,
a MIDI soft synth would not necessarily be expected to set this
flag. Similarly, PORT_TYPE_SYNTH indicates that the port has the
ability to do (non-MIDI) direct synthesis, and again a MIDI soft
synth or a driver for a soundcard MIDI synth would not be expected
to set this flag unless it was also capable of direct synthesis.
So "port is attached to a synthesizer device" is unfortunately an
inadequate and misleading description for PORT_TYPE_SYNTH, as
ports attached to MIDI synth devices will generally not have this
flag set. I found all this most confusing, but that's probably
because I don't really know anything about non-MIDI clients.
Look for the subject "Sequencer port type flags" in the archives
(in early May this year) for more details.
Chris
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
prev parent reply other threads:[~2003-06-30 15:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-09 2:06 Sequencer documentation follow-up Drake Wilson
2003-06-30 14:28 ` Takashi Iwai
2003-06-30 15:12 ` Chris Cannam [this message]
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=3F00534C.7060706@all-day-breakfast.com \
--to=cannam@all-day-breakfast.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=drake@libcom.com \
/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.