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 10:54:06 +0100 [thread overview]
Message-ID: <3EBB7ABE.3000308@all-day-breakfast.com> (raw)
In-Reply-To: Pine.LNX.4.44.0305082159360.1435-100000@pnote.perex-int.cz
Jaroslav Kysela wrote:
> Note that the SYNTH ports should support SNDRV_SEQ_EVENT_SAMPLE* events.
> It means direct wavetable synthesis not MIDI event communication.
OK, now I'm confused again. 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?
My interpretation so far has been that most soft synths should set
SYNTH, APPLICATION and possibly SAMPLE if they're sample-based,
whereas a sequencer like Rosegarden should set APPLICATION and
nothing else. Do I have that wrong?
(And I don't know of any soft synths that are always GM devices,
so I'm doubtful -- as I mentioned in another email -- whether they
should be setting GM or not.)
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 9:54 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 ` Chris Cannam [this message]
2003-05-09 10:11 ` [Rosegarden-devel] " Chris Cannam
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=3EBB7ABE.3000308@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox