From: Hui Wang <hui.wang@canonical.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org,
David Henningsson <david.henningsson@canonical.com>
Subject: Re: 2 speakers are assigned to the same DAC, this can't support 4.0/2.1 channles
Date: Fri, 12 Jun 2015 09:07:24 +0800 [thread overview]
Message-ID: <557A30CC.6030601@canonical.com> (raw)
In-Reply-To: <s5hoakmjn6i.wl-tiwai@suse.de>
On 06/11/2015 11:10 PM, Takashi Iwai wrote:
> At Wed, 10 Jun 2015 12:28:39 +0200,
> Takashi Iwai wrote:
>>>>> A cleaner way would be to prepare a different badness table for the
>>>>> speaker, and increase the value for shared_surr. An untested patch is
>>>>> below.
>>>> Got it, I will test it soon. Thanks.
>>>>
>>> Hi Takashi,
>>>
>>> Your patch can fix the problem, it works very well.
>> OK, good to know. I'd like to test a bit more via hda-emu whether
>> this gives any ill effects. So far, this seems fixing a few other
>> machines, too, so it's a good thing to have in general.
> This change alone results in regressions on machines that are capable
> of 4.0/5.1 surrounds. For avoiding it, the badness for multi-io has
> to be increased as well. It's damn sensitive.
>
> But, now I wonder now whether blindly applying this is good. Suppose
> a machine with 2.1 speaker and one headphone, but the codec has only
> two DACs. With this setup, now the headphone and the speaker share
> the same DAC, as the cost of having individual 2.1 speaker volume.
> Is this more useful than having individual volumes for speaker and
> headphone?
If having individual volumes for speaker and headphone (the speakers
share the same DAC), there will be no "Front Speaker" and "Bass
Speaker", as a result, in the userspace, pulseaudio can't regard the 2.1
channels is a valid profile.
>
> Maybe the machine you're trying to support has a different situation.
> So applying the new rule to limited devices is fine. But if so, it's
> not necessarily to be an adjustment of badness table, but just you can
> provide the simple DAC/pin preference map explicitly in the fixup.
This is a good idea, so far this machine is the only one with this
problem, it is suitable to use a machine specific fixup. If in future,
we have more machines with this problem, then we will think about a
general way to fix it.
>
>
> Takashi
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>
next prev parent reply other threads:[~2015-06-12 1:07 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-09 9:38 2 speakers are assigned to the same DAC, this can't support 4.0/2.1 channles hwang4
2015-06-09 11:50 ` Raymond Yau
2015-06-09 13:20 ` Hui Wang
2015-06-10 1:30 ` Raymond Yau
2015-06-10 3:18 ` hwang4
2015-06-11 1:15 ` Raymond Yau
2015-06-11 2:15 ` Hui Wang
2015-06-11 7:37 ` Raymond Yau
2015-06-11 8:33 ` Hui Wang
2015-06-11 16:44 ` Raymond Yau
2015-06-10 4:59 ` Raymond Yau
2015-06-10 6:42 ` hwang4
2015-06-12 1:34 ` Raymond Yau
2015-06-12 3:32 ` Hui Wang
2015-06-09 11:51 ` Takashi Iwai
2015-06-09 13:26 ` Hui Wang
2015-06-10 4:19 ` hwang4
2015-06-10 10:28 ` Takashi Iwai
2015-06-11 15:10 ` Takashi Iwai
2015-06-12 1:07 ` Hui Wang [this message]
2015-06-12 1:22 ` Raymond Yau
2015-06-12 3:25 ` Hui Wang
2015-06-12 4:42 ` Raymond Yau
2015-06-12 6:07 ` David Henningsson
2015-06-12 9:40 ` Raymond Yau
2015-06-12 16:05 ` Takashi Iwai
2015-06-13 2:43 ` Raymond Yau
2015-06-14 6:48 ` Raymond Yau
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=557A30CC.6030601@canonical.com \
--to=hui.wang@canonical.com \
--cc=alsa-devel@alsa-project.org \
--cc=david.henningsson@canonical.com \
--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