All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alfredo" <alfredo@vida-software.com>
To: "alsa-devel@lists.sourceforge.net" <alsa-devel@lists.sourceforge.net>
Subject: Little question about ALSA callbacks
Date: Wed, 27 Jul 2005 11:28:26 +0200	[thread overview]
Message-ID: <a6ad962c7a723f49966db2fe23f87517@vida-software.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1647 bytes --]

Hello, I have read the article "Introduction to Sound Programming with
ALSA from Linux Journal. This article explains:



// Starts here:
------------------------------------------------------------------------
-------------------------------------------

"In the previous examples, the PCM streams were operating in blocking
mode, that is, the calls would not return until the data had been
transferred. In an interactive event-driven application, this situation
could lock up the application for unacceptably long periods of time.
ALSA allows opening a stream in nonblocking mode where the read and
write functions return immediately. If data transfers are pending and
the calls cannot be processed, ALSA returns an error code of EBUSY.

Many graphical applications use callbacks to handle events. ALSA
supports opening a PCM stream in asynchronous mode. This allows
registering a callback function to be called when a period of sample
data has been transferred."

// Finishes here:
------------------------------------------------------------------------
-------

I'm developing an event driven Linux server that will use ALSA library.
Please, could you point me to some resources in order to learn how to
use alsa in asynchronous mode (the event driven mechanism will be based
in poll()).

Clemens Ladisch helped me suggesting that I must use poll to wait for
events in different file descriptors. I need to be notified when audio
buffer has been recorded. I need to learn how to use ALSA in conjunction
with poll.

I'm a Linux developer beginner and I'm glad to use ALSA.

Thank you very much ;-)




[-- Attachment #2: Type: text/html, Size: 4258 bytes --]

             reply	other threads:[~2005-07-27  9:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-27  9:28 Alfredo [this message]
2005-07-27  9:48 ` Little question about ALSA callbacks Takashi Iwai
2005-07-27 11:21   ` Alfredo
2005-07-27 10:05 ` Joern Seger
2005-07-27 14:30   ` Alfredo

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=a6ad962c7a723f49966db2fe23f87517@vida-software.com \
    --to=alfredo@vida-software.com \
    --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 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.