All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tanu Kaskinen <tanuk@iki.fi>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: [RFC] Channel mapping API (take 2)
Date: Wed, 05 Sep 2012 09:38:26 +0300	[thread overview]
Message-ID: <1346827106.3629.40.camel@laptop> (raw)
In-Reply-To: <s5hligpj8mv.wl%tiwai@suse.de>

On Wed, 2012-09-05 at 08:17 +0200, Takashi Iwai wrote:
> Well, this raises a question "What is mono".
> If this is supposed to be a channel position, then we should add the
> definition.  But is it really so?  If it's a mono stream mixed from
> front left and front right, isn't it a front center?

If it's a playback stream and alsa knows that it will be routed to a
center speaker on a surround system, then yes, it should be front
center. But if the audio ends up in a lone speaker, mixing left and
right doesn't really result in a center position.

I think mono means pretty much "single channel without defined
position", for which SND_CHMAP_UNKNOWN could be a useful choice, except
that I think PulseAudio will end up ignoring channels with
SND_CHMAP_UNKNOWN, because there's no sane definition for how channel
remapping should be done for such channels. But maybe the single channel
case could be treated as an exception - a single channel with
SND_CHMAP_UNKNOWN could be treated as a mono device, for which
downmixing (or upmixing in case of capture) is well defined.

-- 
Tanu

  reply	other threads:[~2012-09-05  6:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-04 15:47 [RFC] Channel mapping API (take 2) Takashi Iwai
2012-09-05  6:00 ` Tanu Kaskinen
2012-09-05  6:17   ` Takashi Iwai
2012-09-05  6:38     ` Tanu Kaskinen [this message]
2012-09-05  6:49 ` David Henningsson
2012-09-05  6:59   ` Takashi Iwai
2012-09-05  8:32 ` David Henningsson
2012-09-05 10:34   ` Takashi Iwai
2012-09-06 11:47 ` Raymond Yau
2012-09-06 11:56   ` Takashi Iwai
2012-09-07  9:16 ` Tanu Kaskinen
2012-09-07  9:43   ` Takashi Iwai

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=1346827106.3629.40.camel@laptop \
    --to=tanuk@iki.fi \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    /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.