From: Manuel Jander <manuel.jander@mat.utfsm.cl>
To: Alsa Devel list <alsa-devel@lists.sourceforge.net>,
Openvortex <openvortex-dev@nongnu.org>
Subject: A few ideas about environmental audio...
Date: Wed, 17 Mar 2004 10:58:52 -0400 [thread overview]
Message-ID: <1079535532.1993.28.camel@localhost> (raw)
Hi,
So far i'm following this list, there are some people interested in
environmental audio, and advanced effect processing support. Regarding
this i would like to share some thoughts about and hopefully collect
some critics and comments.
How i visualize environmental audio for the common user:
Context: The user has a Soundboard with several audio outputs (most of
them do). He/She may connect just a headphone or 2 speakers or a 5.1
setup, 7.1, or whatever the card supports.
Problem: It's up to the application to support either 5.1, headphones
or whatever. You may end up not hearing some channels (your soundcard
has 6 outputs, but you just have headphones, or you have 6 speakers and
your are hearing a stereo stream on just 2 speakers). There is a lot of
duplicated code in different applications, and there is no standard
about how this down or up mix should be done. It may be impossible to
exploit any advanced hardware feature (see Advantage).
Idea: Support any audio channel arrangement, and mix it in hardware or
software (plugins, dmix ?) to the actual number of speaker/headphones
channels. Define a standard how channel formatting should be
converted/mixed, etc.
Requirements: The user has to tell ALSA what kind of
speakers/headphones is she/he using (not a big deal).
Advantage: We could support 7.1 or 5.1 environmental audio on
headphones, by using hardware HRTF filters to put each stream at the
desired spatial position. On some soundcards this is trivial (just a
matter of routing).
Caveats: It involves work obviously. I'm willing to volunteer on this.
Any comments are gladly welcome.
Best Regards
Manuel
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
reply other threads:[~2004-03-17 14:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1079535532.1993.28.camel@localhost \
--to=manuel.jander@mat.utfsm.cl \
--cc=alsa-devel@lists.sourceforge.net \
--cc=openvortex-dev@nongnu.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.