From: Tanu Kaskinen <tanu.kaskinen@jollamobile.com>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org,
pulseaudio-discuss@lists.freedesktop.org
Subject: Re: [alsa-devel] Channel map API patches: to be 3.7 or not to be?
Date: Wed, 12 Sep 2012 20:20:10 +0300 [thread overview]
Message-ID: <1347470410.14342.3.camel@laptop> (raw)
In-Reply-To: <5050B91A.7020303@ladisch.de>
On Wed, 2012-09-12 at 18:32 +0200, Clemens Ladisch wrote:
> Takashi Iwai wrote:
> >> Clemens Ladisch wrote:
> >>> Takashi Iwai wrote:
> >>>> is it useful to add SND_CHMAP_MONO, or is it just redundant?
> >>>
> >>> What would it be used for?
> >
> > Looking at PulseAudio and gstreamer codes, they seem to have explicit
> > MONO channel definition.
> > [...]
> > So, defining MONO seems rather standard. Now I'm inclined to define
> > SND_CHMAP_MONO...
>
> Okay; if they want it, they can get it ...
Speaking as a PulseAudio developer, "wanting" is a bit strong word. I
initially wanted it, but I don't anymore think that it's necessary. I
don't think it will do any harm either, though...
--
Tanu
next prev parent reply other threads:[~2012-09-12 17:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 17:43 Channel map API patches: to be 3.7 or not to be? Takashi Iwai
2012-09-11 8:10 ` Raymond Yau
2012-09-11 8:22 ` Takashi Iwai
2012-09-11 12:14 ` Takashi Iwai
2012-09-11 12:19 ` Clemens Ladisch
2012-09-11 12:24 ` Takashi Iwai
2012-09-12 16:03 ` Takashi Iwai
2012-09-12 16:32 ` Clemens Ladisch
2012-09-12 17:20 ` Tanu Kaskinen [this message]
2012-09-12 1:35 ` Raymond Yau
2012-09-12 6:21 ` Takashi Iwai
2012-09-17 10:46 ` Raymond Yau
2012-09-17 10:49 ` Takashi Iwai
2012-09-17 9:39 ` 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=1347470410.14342.3.camel@laptop \
--to=tanu.kaskinen@jollamobile.com \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=pulseaudio-discuss@lists.freedesktop.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 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).