From: Pierre Ossman <ossman@cendio.se>
To: alsa-devel@alsa-project.org
Subject: Non-continous channel map?
Date: Thu, 27 Apr 2006 07:52:35 +0200 [thread overview]
Message-ID: <44505C23.30109@cendio.se> (raw)
Hi!
ALSA uses a rather strict default channel map, just a simple list. This
is insufficient for the polypaudio plug-in I wrote, as the polypaudio
server might have an output of e.g. just the center channel and a
subwoofer. I'm wondering how to properly represent this in ALSA.
For the PCM, there is no problem as we as clients decide which channels
are to be set up. The server will then need to map these to actual hardware.
For mixer, however, we're modifying the server hardware so we will need
to adapt to whatever channels it has. So provided I have a device with
channels "left", "right", "center" and "subwoofer", should I:
a) Just expose "left" and "right" since "rear left" isn't present (the
next in ALSA's list).
b) Expose all channels until I can cover my four and simply filter out
the ones that aren't present on the server.
c) Ignore ALSA's list completely and leave it to the user to figure
out what the channel map is.
d) Something else?
Input appreciated.
--
Pierre Ossman Telephone: +46-13-21 46 00
Cendio AB Web: http://www.cendio.com
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
next reply other threads:[~2006-04-27 5:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-27 5:52 Pierre Ossman [this message]
2006-05-03 12:06 ` Non-continous channel map? Clemens Ladisch
2006-05-03 12:43 ` Pierre Ossman
2006-05-03 12:52 ` Takashi Iwai
2006-05-03 12:56 ` Takashi Iwai
2006-05-03 14:00 ` Pierre Ossman
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=44505C23.30109@cendio.se \
--to=ossman@cendio.se \
--cc=alsa-devel@alsa-project.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.