From: David Olofson <david@olofson.net>
To: alsa-devel@lists.sourceforge.net
Subject: Re: Sequencer Note events...?
Date: Thu, 30 Jan 2003 14:15:23 +0100 [thread overview]
Message-ID: <200301301415.23730.david@olofson.net> (raw)
In-Reply-To: <s5h3cnalrxz.wl@alsa2.suse.de>
On Thursday 30 January 2003 13.53, Takashi Iwai wrote:
> At Thu, 30 Jan 2003 13:14:13 +0100,
>
> David Olofson wrote:
> > I've noticed that there is a Note event type (the one with
> > duration and Off velocity), and means for sending it.
> >
> > Does this mean I should also expect to receive such events? I've
> > never seen an example program handle this event, so I initially
> > assumed that it's actually a macro event that will be turned into
> > separate Note On and Note Off events by the sequencer.
>
> yes, exactly. the sequencer core resents the note-off event
> replaced from the original note event after the given duration.
...and it also replaces the Note event with a Note On event, so I
don't have to see the actual Note event at all...?
//David Olofson - Programmer, Composer, Open Source Advocate
.- The Return of Audiality! --------------------------------.
| Free/Open Source Audio Engine for use in Games or Studio. |
| RT and off-line synth. Scripting. Sample accurate timing. |
`---------------------------> http://olofson.net/audiality -'
--- http://olofson.net --- http://www.reologica.se ---
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
next prev parent reply other threads:[~2003-01-30 13:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-30 12:14 Sequencer Note events...? David Olofson
2003-01-30 12:53 ` Takashi Iwai
2003-01-30 13:15 ` David Olofson [this message]
2003-01-30 13:19 ` 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=200301301415.23730.david@olofson.net \
--to=david@olofson.net \
--cc=alsa-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