From: Takashi Iwai <tiwai@suse.de>
To: David Henningsson <david.henningsson@canonical.com>
Cc: hwang4 <hui.wang@canonical.com>, alsa-devel@alsa-project.org
Subject: Re: 2 speakers are assigned to the same DAC, this can't support 4.0/2.1 channles
Date: Fri, 12 Jun 2015 18:05:07 +0200 [thread overview]
Message-ID: <s5h4mmcj4jw.wl-tiwai@suse.de> (raw)
In-Reply-To: <557A7718.5070100@canonical.com>
At Fri, 12 Jun 2015 08:07:20 +0200,
David Henningsson wrote:
>
>
>
> On 2015-06-11 17:10, Takashi Iwai wrote:
> > At Wed, 10 Jun 2015 12:28:39 +0200,
> > Takashi Iwai wrote:
> >> 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?
> >
> > 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.
>
> Oh, this is an interesting trade-off.
>
> In the PulseAudio desktop scenario, we automute the speaker, and
> PulseAudio remembers the individual headphone and speaker volumes. So in
> this case, there is no benefit from having individual headphone and
> speaker volume at the ALSA level.
>
> However if a user wants to turn off automute, then there is a need for
> being able to adjust headphone and speaker volume individually.
>
> But it's not just a question of volume control for 2.1. Being able to
> send a different stream to the subwoofer could be useful too, especially
> if the hardware filter is bad or non-existing.
>
> So my gut feeling leans towards using the second DAC for the subwoofer
> speaker being the more useful default, but it's not a clear cut.
Right, this is indeed a difficult problem, and probably there is never
a clear answer.
Another interesting examples are:
A. 3 DACs, 2 HP, 2 speakers
B. 3 DACs, 2 HP, 1 mic, 1 speaker
C. 4 DACs, 2 HP, 1 mic, 2 speakers
For B and C, user expects the possible 5.1 outputs by retasking the
mic. But then you'll lose the individual volume control with the
speaker.
Takashi
next prev parent reply other threads:[~2015-06-12 16:05 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
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 [this message]
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=s5h4mmcj4jw.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=david.henningsson@canonical.com \
--cc=hui.wang@canonical.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox