Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Clemens Ladisch" <cladisch@fastmail.net>
To: Carlo Florendo <subscribermail@gmail.com>
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 10:24:58 +0200	[thread overview]
Message-ID: <1185351898.28416.1201921883@webmail.messagingengine.com> (raw)
In-Reply-To: <46A69F4D.7050002@gmail.com>

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).


Regards,
Clemens

  reply	other threads:[~2007-07-25  8:24 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     ` Clemens Ladisch [this message]
2007-07-25  8:51       ` [LAD] " Carlo Florendo
2007-07-25  9:16       ` Carlo Florendo

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=1185351898.28416.1201921883@webmail.messagingengine.com \
    --to=cladisch@fastmail.net \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-audio-dev@lists.linuxaudio.org \
    --cc=subscribermail@gmail.com \
    /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