From: Frank van de Pol <fvdpol@home.nl>
To: Brian Victor <bhv1@psu.edu>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: General Guidelines? (MIDI)
Date: Sun, 19 Jan 2003 23:21:56 +0100 [thread overview]
Message-ID: <20030119222156.GC5697@obelix> (raw)
In-Reply-To: <20030116223735.GB32330@bhv1.adelphia.net>
On Thu, Jan 16, 2003 at 05:37:35PM -0500, Brian Victor wrote:
>
> Likewise, I was under the impression that queues handled sequencing
> events by timestamp if they arrived in non-sequential order. Is that
> so?
Yes, the sequencer's priority queues automatically order the events enqueued
by timestamp.
> Do I just need to stay ahead of the queue for this to work? Does
> that mean, I can't reliably send the queue all events for one voice,
> followed by all events for another voice?
Because of memory sizes for the event pool, this depends on the number of
events you want to enqueue. Of course you'll need to stay ahead of the queue
or the event wil be emitted immediately (when T[scheduled] < T[queue head]).
Yes, you can enqueue all events for one voice followed by next voices as
long as you do not exceed the size of the queue. In practice you'll enqueue
the events for a (small) timeframe, eg. one bar, and let the sequencer
handle the scheduling.
Frank.
--
+---- --- -- - - - -
| Frank van de Pol -o) A-L-S-A
| FvdPol@home.nl /\\ Sounds good!
| http://www.alsa-project.org _\_v
| Linux - Why use Windows if we have doors available?
-------------------------------------------------------
This SF.NET email is sponsored by: FREE SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
next prev parent reply other threads:[~2003-01-19 22:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E18ZGLH-0005nh-00@sc8-sf-list2.sourceforge.net>
2003-01-16 21:27 ` General Guidelines? (MIDI) Pedro Lopez-Cabanillas
2003-01-16 22:37 ` Brian Victor
2003-01-19 22:21 ` Frank van de Pol [this message]
2003-01-11 18:31 Brian Victor
2003-01-13 9:25 ` Clemens Ladisch
2003-01-13 10:02 ` Takashi Iwai
2003-01-14 21:20 ` Brian Victor
2003-01-15 11:43 ` Clemens Ladisch
2003-01-16 3:27 ` Brian Victor
2003-01-16 7:39 ` Clemens Ladisch
2003-01-16 13:41 ` Brian Victor
2003-01-16 15:32 ` Tim Goetze
2003-01-16 17:23 ` Brian Victor
2003-01-16 18:14 ` 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=20030119222156.GC5697@obelix \
--to=fvdpol@home.nl \
--cc=alsa-devel@lists.sourceforge.net \
--cc=bhv1@psu.edu \
/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.