From: "Alfredo" <alfredo@vida-software.com>
To: "alsa-devel@lists.sourceforge.net" <alsa-devel@lists.sourceforge.net>
Subject: ALSA and event notification schemas
Date: Mon, 25 Jul 2005 19:09:14 +0200 [thread overview]
Message-ID: <0416c7e824e16a44987863eda70d4199@vida-software.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1460 bytes --]
Hello, I'm involved in a development project consisting of a
multimedia/networked component using event driven model in a C++ Linux
environment (1 thread than manages all the events using an event loop).
The events that the component must handle are:
1. Sockets events.
2. Timer events.
3. Audio events ( event = when the next buffer is filled with audio from
the user, notify the component. Then the component will transfer the
audio buffer using a udp socket to another distributed component).
4. Key press and release events (Push To Talk key)
What is the best way to handle all this events in a Linux environment?
I have found that libevent is a very interesting library:
http://www.monkey.org/~provos/libevent/
"The libevent API provides a mechanism to execute a callback function
when a specific event occurs on a file descriptor or after a timeout has
been reached".
This resolves the sockets and timer events. I'm not sure if this
approach works well with ALSA (for audio events). I have read that ALSA
provides asynch IO (and callbacks mechanishm), but I don't know if it
fits well with libevent approach.
Is there any way use ALSA to handle audio events (like buffer is filled
with audio from the microphone) and handle the rest of the events in the
same process in a Linux environment?
Another question: Does ALSA support AMR or GSM codecs?
Your help is really very apreciated.
[-- Attachment #2: Type: text/html, Size: 4742 bytes --]
next reply other threads:[~2005-07-25 17:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-25 17:09 Alfredo [this message]
2005-07-26 7:17 ` ALSA and event notification schemas Clemens Ladisch
2005-07-26 8:47 ` Alfredo
2005-07-26 10:01 ` 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=0416c7e824e16a44987863eda70d4199@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.