From: Chris Cannam <cannam@all-day-breakfast.com>
To: alsa-devel <alsa-devel@lists.sourceforge.net>
Cc: rosegarden-devel <rosegarden-devel@lists.sourceforge.net>
Subject: Re: [Rosegarden-devel] Re: Sequencer port type flags
Date: Fri, 09 May 2003 11:11:59 +0100 [thread overview]
Message-ID: <3EBB7EEF.5060908@all-day-breakfast.com> (raw)
In-Reply-To: 3EBB7ABE.3000308@all-day-breakfast.com
Chris Cannam wrote:
> Are you saying that a soft synth that
> can only be driven via MIDI should not describe itself as a SYNTH?
> If so, how do I know it's a synth?
I suppose (replying to myself) that it's all about what these flags
are intended to be used for. I had assumed they were basically
informational flags for identifying classes of device, and as I've
only had to deal with MIDI clients (and then only very naively),
I've only really thought about clients that are already assumed to
understand MIDI.
I suppose the alternative is that these flags are necessary to
distinguish between different modes of communication -- different
sorts of events that a particular client understands. So once
I've found out that a device is a MIDI device, how I find out that
it's then a synth is entirely my problem -- the API doesn't care,
because MIDI is all the same to it anyway.
If that's so, then these flags are of no use to Rosegarden.
Chris
-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com
next prev parent reply other threads:[~2003-05-09 10:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-07 23:42 Sequencer port type flags Pedro Lopez-Cabanillas
2003-05-08 17:51 ` Frank van de Pol
2003-05-08 20:00 ` Jaroslav Kysela
2003-05-09 9:54 ` [Rosegarden-devel] " Chris Cannam
2003-05-09 10:11 ` Chris Cannam [this message]
2003-05-09 10:54 ` Jaroslav Kysela
2003-05-09 10:43 ` Jaroslav Kysela
2003-05-09 12:00 ` Chris Cannam
2003-05-10 17:15 ` Pedro Lopez-Cabanillas
2003-05-12 10:02 ` 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=3EBB7EEF.5060908@all-day-breakfast.com \
--to=cannam@all-day-breakfast.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=rosegarden-devel@lists.sourceforge.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.