From: Clemens Ladisch <clemens@ladisch.de>
To: Irfan Shaikh <irfan.shaikh@sasken.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: ALSA mixer query
Date: Fri, 28 Jan 2011 14:00:23 +0100 [thread overview]
Message-ID: <4D42BDE7.5000606@ladisch.de> (raw)
In-Reply-To: <16F32A3F9AF4E441B752BCD79C151ACA69CF0CF4EA@EXGMBX01.sasken.com>
Irfan Shaikh wrote:
> I am rendering audio to a PCM playback device (hw:0,0). I also need
> to render the same audio data to second PCM playback device (hw:0,1).
>
> 1) Can i use ALSA mixer APIs so that i give PCM audio data to 1
> playback device or some common interface, but the PCM audio data
> is rendered to both devices (hw:0,0 and hw:0,1)
The mixer API ist just an interface to the hardware, so this would
depend on the hardware's capabilities.
However, you could use the plugin mechanism to create a virtual PCM
device that routes its data to two actual devices. See
<http://www.alsa-project.org/alsa-doc/alsa-lib/pcm_plugins.html#pcm_plugins_multi>.
> SASKEN BUSINESS DISCLAIMER: This message may contain bla bla bla ...
This e-mail contains public information intended for any subscriber of
this mailing list and for anybody else who bothers to read it; it will
be copied, disclosed and distributed to the public. If you think you
are not the intended recipient, please commit suicide immediately.
These terms apply also to any e-mails quoted in, referenced from, or
answering this e-mail, and supersede any confidentiality notices in
those e-mails. Additionally, confidentiality notices in those e-mails
will incur legal processing fees of $42 per line; you have agreed to
this by reading this confidentiality notice.
Regards,
Clemens
prev parent reply other threads:[~2011-01-28 13:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 14:09 ALSA mixer query Irfan Shaikh
2011-01-28 13:00 ` Clemens Ladisch [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=4D42BDE7.5000606@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=irfan.shaikh@sasken.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;
as well as URLs for NNTP newsgroup(s).