Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: "Ronald S. Bultje" <R.S.Bultje@students.uu.nl>
Cc: ALSA development <alsa-devel@alsa-project.org>
Subject: Re: speaker configuration
Date: Fri, 23 Jul 2004 02:40:17 +0100	[thread overview]
Message-ID: <41006C81.7090900@superbug.demon.co.uk> (raw)
In-Reply-To: <1090522504.29769.29.camel@shrek.bitfreak.net>

Ronald S. Bultje wrote:
> Hi,
> 
> if I setup a sound playback stream using N channels, how do I find out
> what the speaker configuration is? For example, my SB Audigy 2 NX
> supports (using hw: access) 2, 4, 6 and 8 channels. 2 is stereo, 8 is
> probably 7.1 (3 front, 2 side, 2 rear, 1 lfe), 6 is probably 5.1 (same
> as 7.1, without side). What is 4? If I open the card using plughw:, I
> get 1-32 channels. What does each of those mean? And related to this,
> what is the speaker's position order? In other words, if I send 8
> interleaved channelsamples of sound (1 soundsample) to my channels=8
> soundcard, on what speaker will the first, second, ... channelsample be
> played?
> 
> Thanks,
> 
> Ronald
> 

The general speaker order is:
Channel
0 - Front Left
1 - Front Right
2 - Rear Left
3 - Rear Right
4 - Center
5 - LFE
6 - Side Left
7 - Side Right

alsa provides nicer names.
For X open with device name Y.
X        Y
2.0      "plug:front"
4.0      "plug:surround40"
5.1      "plug:surround51"
7.1      "plug:surround71"




-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click

      reply	other threads:[~2004-07-23  1:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-22 18:55 speaker configuration Ronald S. Bultje
2004-07-23  1:40 ` James Courtier-Dutton [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=41006C81.7090900@superbug.demon.co.uk \
    --to=james@superbug.demon.co.uk \
    --cc=R.S.Bultje@students.uu.nl \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox