From: Carlo Florendo <subscribermail@gmail.com>
To: Clemens Ladisch <cladisch@fastmail.net>
Cc: alsa-devel@alsa-project.org, linux-audio-dev@lists.linuxaudio.org
Subject: Re: [LAD] How to get correct midi timings from ALSA using the library only
Date: Wed, 25 Jul 2007 17:16:28 +0800 [thread overview]
Message-ID: <46A714EC.10408@gmail.com> (raw)
In-Reply-To: <1185351898.28416.1201921883@webmail.messagingengine.com>
Clemens Ladisch wrote:
> Carlo Florendo wrote:
>> Clemens Ladisch wrote:
>>>> However, I wish to be able to make the sequencer or player work without the
>>>> use of the ALSA queue nor the workaround in (2).
>>> Why?
>> Because the queue output and draining, AFAICS, is implemented in a blocking
>> manner.
>
> When non-blocking mode is set (see snd_seq_nonblock()),
> snd_seq_drain_output() does not block but writes only as many events to
> the kernel buffer as fit inside (or returns -EAGAIN if the kernel buffer
> is completely full).
Bingo! My recent tests show that snd_seq_nonblock() is indeed a useful
function and enables me to have control of the sequencer every time it
outputs an event :)
Gee, I've read the ALSA lib doc for months and never came across this
function. Up to now, I've not seen the part of the doc that describes
snd_seq_nonblock so I went straight to the source code of alsa-lib under
src/seq/seq.c and grepped for snd_seq_block().
The alsa-lib docs have to be improved :)
Thank you for the pointers!
>
> Regards,
> Clemens
>
Best Regards,
Carlo
--
Carlo Florendo
Softare Engineer/Network Co-Administrator
Astra Philippines Inc.
UP-Ayala Technopark, Diliman 1101, Quezon City
Philippines
http://www.astra.ph
--
The Astra Group of Companies
5-3-11 Sekido, Tama City
Tokyo 206-0011, Japan
http://www.astra.co.jp
prev parent reply other threads:[~2007-07-25 9:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-24 9:01 How to get correct midi timings from ALSA using the library only Carlo Florendo
[not found] ` <46A5BFDF.4040906-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2007-07-24 10:06 ` [LAD] " Florian Schmidt
[not found] ` <200707241206.09991.mista.tapas-hi6Y0CQ0nG0@public.gmane.org>
2007-07-25 2:18 ` Carlo Florendo
[not found] ` <46A6B2DC.3030906-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2007-07-25 9:25 ` Florian Schmidt
2007-07-26 4:51 ` Carlo Florendo
2007-07-24 10:24 ` Clemens Ladisch
2007-07-25 0:54 ` Carlo Florendo
2007-07-25 8:24 ` [LAD] " Clemens Ladisch
2007-07-25 8:51 ` Carlo Florendo
2007-07-25 9:16 ` Carlo Florendo [this message]
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=46A714EC.10408@gmail.com \
--to=subscribermail@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=cladisch@fastmail.net \
--cc=linux-audio-dev@lists.linuxaudio.org \
/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