From: Clemens Ladisch <clemens@ladisch.de>
To: Henning Thielemann <alsa@henning-thielemann.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: sending a sequencer event to a delayed queue
Date: Mon, 12 Mar 2012 09:21:14 +0100 [thread overview]
Message-ID: <4F5DB1FA.9030802@ladisch.de> (raw)
In-Reply-To: <alpine.DEB.2.00.1203112200370.12766@anubis.informatik.uni-halle.de>
Henning Thielemann wrote:
> On Sun, 11 Mar 2012, Clemens Ladisch wrote:
>> Yes; whether an event is delivered depends only on its scheduled time,
>> not whether the queue is running.
>
> That is, if the queue time is zero and the event time is zero, then
> the event is sent, independent of whether the queue is running or not.
Yes.
> Since we are at documentation. seq.h states:
>
> #define SND_SEQ_PORT_CAP_SYNC_READ (1<<2) /**< allow read subscriptions */
> #define SND_SEQ_PORT_CAP_SYNC_WRITE (1<<3) /**< allow write subscriptions */
> ...
> #define SND_SEQ_PORT_CAP_SUBS_READ (1<<5) /**< allow read subscription */
> #define SND_SEQ_PORT_CAP_SUBS_WRITE (1<<6) /**< allow write subscription */
>
> So are the comments for SYNC_READ and SYNC_WRITE correct?
No, they should say "obsolete; no effect".
Regards,
Clemens
next prev parent reply other threads:[~2012-03-12 8:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-10 18:20 sending a sequencer event to a delayed queue Henning Thielemann
2012-03-10 20:51 ` Clemens Ladisch
2012-03-11 15:41 ` Henning Thielemann
2012-03-11 20:40 ` Clemens Ladisch
2012-03-11 21:08 ` Henning Thielemann
2012-03-11 22:14 ` Henning Thielemann
2012-03-12 8:21 ` Clemens Ladisch [this message]
2012-03-14 20:01 ` Henning Thielemann
2012-03-14 20:22 ` Henning Thielemann
2012-03-14 21:36 ` Clemens Ladisch
2012-03-13 22:33 ` Henning Thielemann
2012-03-14 8:22 ` Clemens Ladisch
2012-03-14 17:37 ` Henning Thielemann
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=4F5DB1FA.9030802@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=alsa@henning-thielemann.de \
/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.