From: "Ryan Cassidy" <rcassidy@stanford.edu>
To: alsa-devel@lists.sourceforge.net
Cc: ryanc@ieee.org
Subject: Interrupt-driven (or callback/handler?), Full-duplex (simultaneous capture/playback) without using JACK
Date: Sat, 8 Nov 2003 16:18:46 -0800 [thread overview]
Message-ID: <000b01c3a657$0b150b80$264440ab@roboserv1> (raw)
Hi all,
I am trying to write an application that uses ALSA interrupt-driven
(which I guess is obtained by adding PCM handler(s) in ALSA?),
full-duplex (simultaneous capture/playback) using the ALSA PCM API
directly (i.e. not using JACK).
My question: do I only need to register one callback/handler function to
take care of both capture and playback? My hope is that when I link the
capture and playback streams, and register a single handler with either
capture or playback, this handler will be called whenever there is BOTH
capture data to be read and a free playback buffer to be written (?).
Is this the case?
Any help, info., or advice GREATLY appreciated.
Cheers, rjc.
--
Ryan Cassidy
Electrical Engineering Graduate Student, CCRMA Researcher
Stanford University
E-mail: ryanc@ieee.org
-------------------------------------------------------
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn firsthand the latest
developments in Apache, PHP, Perl, XML, Java, MySQL,
WebDAV, and more! http://www.apachecon.com/
next reply other threads:[~2003-11-09 0:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-09 0:18 Ryan Cassidy [this message]
2003-11-09 3:42 ` Interrupt-driven (or callback/handler?), Full-duplex (simultaneous capture/playback) without using JACK Paul Davis
2003-11-09 4:33 ` Ryan Cassidy
2003-11-09 8:37 ` Jaroslav Kysela
2003-11-10 10:57 ` Ryan Cassidy
2003-11-10 11:05 ` Jaroslav Kysela
2003-11-10 12:26 ` Paul Davis
2003-12-30 1:57 ` Ryan Cassidy
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='000b01c3a657$0b150b80$264440ab@roboserv1' \
--to=rcassidy@stanford.edu \
--cc=alsa-devel@lists.sourceforge.net \
--cc=ryanc@ieee.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 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.