From: Tanu Kaskinen <tanuk@iki.fi>
To: Raymond Yau <superquad.vortex2@gmail.com>
Cc: Tanu Kaskinen <tanu.kaskinen@digia.com>, alsa-devel@alsa-project.org
Subject: Re: How to define card specific pcm devices?
Date: Sat, 18 Aug 2012 07:09:13 +0300 [thread overview]
Message-ID: <1345262953.4864.12.camel@laptop> (raw)
In-Reply-To: <CAN8cciZH2SL7Dm0ykA+hfRoksngo9Z15pkTLHp+pXDYSKpm90w@mail.gmail.com>
On Sat, 2012-08-18 at 09:26 +0800, Raymond Yau wrote:
> 2012-8-17 下午10:51 於 "Tanu Kaskinen" <tanu.kaskinen@digia.com> 寫道:
> >
> > Ping?
> >
> > If card specific pcm definitions are not possible, would it be
> > acceptable to have a generic "front_left:CARD" or "first_channel:CARD"
> > pcm, which would transform "front:CARD" or "hw:CARD" into a mono device?
>
> As pulseaudio server use SND_PCM_NO_AUTO_CHANNEL which diable channel
> conversion, this left channel device only work with other alsa applications
> except pulseaudio when your sound card does not support mono.
So are you suggesting that Alsa doesn't need any changes, because all
other applications allow automatic channel conversion, and therefore
this is a PulseAudio specific problem and should be fixed in PulseAudio?
>
> http://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=ff4af902cf4ac07c5f1da3b6dacbb3195c7c222d
>
> the solution is to change the mixing in pulseaudio by using left channel
> for this mic and those stereo mic with inverted phase , and average for
> mono playback device . stereo mic and line-in
Sure this can be fixed in PulseAudio with card specific configuration,
but if at all possible, I want to avoid card specific configuration in
PulseAudio. I believe one of the main points of UCM is to avoid hardware
specific configuration in applications using Alsa.
This could be solved also by stating in the UCM configuration that only
the left channel of the stereo device contains useful data. This would
avoid having card specific configuration in applications, but handling
that information adds more complexity in applications. Having a proper
mono device in Alsa would avoid any changes in applications.
> how about the 4 channel mic?
What about it? The discussion stopped when I asked what should be the
name for the device. I asked whether "4channelinput" would be good, but
got no answers. At PulseAudio side we figured that "hw" works well
enough in practice, so there was not much pressure for me to keep the
discussion alive.
--
Tanu
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2012-08-18 3:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-10 11:25 How to define card specific pcm devices? Tanu Kaskinen
2012-08-17 14:50 ` Tanu Kaskinen
[not found] ` <CAN8cciYX4krbJvb9PWQFswAKq0AqiC_oh20n+NB2Ak=BF8Zgxw@mail.gmail.com>
2012-08-18 1:26 ` Raymond Yau
2012-08-18 4:09 ` Tanu Kaskinen [this message]
2012-08-24 4:20 ` Raymond Yau
2012-08-29 1:44 ` Raymond Yau
2012-09-05 5:41 ` Tanu Kaskinen
[not found] ` <CABS+qY3kEPr3aknPvTU+iRyGxSo2G_iDawv+fr7WBJrJQUO+2w@mail.gmail.com>
2012-09-06 17:18 ` Liam Girdwood
2012-09-07 9:03 ` Tanu Kaskinen
2012-09-07 9:35 ` Takashi Iwai
2012-09-08 8:04 ` Tanu Kaskinen
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=1345262953.4864.12.camel@laptop \
--to=tanuk@iki.fi \
--cc=alsa-devel@alsa-project.org \
--cc=superquad.vortex2@gmail.com \
--cc=tanu.kaskinen@digia.com \
/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.