All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Henningsson <david.henningsson@canonical.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: Shared volume control again
Date: Wed, 29 Oct 2014 20:47:59 +0100	[thread overview]
Message-ID: <5451446F.8020203@canonical.com> (raw)
In-Reply-To: <s5hbnou6bir.wl-tiwai@suse.de>



On 2014-10-29 18:17, Takashi Iwai wrote:
> At Wed, 29 Oct 2014 18:12:14 +0100,
> David Henningsson wrote:
>>
>>
>>
>> On 2014-10-29 18:02, Takashi Iwai wrote:
>>> Hi,
>>>
>>> thinking of the problem about shared volume controls again, I stumbled
>>> on a case where your suggested solution doesn't work well.  Namely,
>>> when a headphone volume is shared for two headphones (one on the
>>> laptop and one on the dock), how should it be named?  One is
>>> "Headphone" and another is "Dock Headphone".  That's a bit tricky.
>>>
>>> So, in the end, we need the mapping representation somehow more
>>> explicitly than the control name.
>>>
>>> Thoughts?
>>
>> In practice, it seems like we more often than not share DAC for all
>> headphones. Also it is very common today that a jack called "Front
>> Headphone" has a volume control called only "Headphone".
>>
>> That's the status quo. As a result we have only one headphone path in
>> PulseAudio for all types of headphones.
>
> OK, so "Headphone" volume should be handled by both "Headphone Jack"
> and "Dock Headphone Jack" detections?  Then it's fine.  I thought this
> wasn't the case (from my memory dealing with an old bug report).

Yes. The "Dock Headphone Jack" name was added quite recently though, so 
it's only in git master right now.

-- 
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic

  reply	other threads:[~2014-10-29 19:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-29 17:02 Shared volume control again Takashi Iwai
2014-10-29 17:12 ` David Henningsson
2014-10-29 17:17   ` Takashi Iwai
2014-10-29 19:47     ` David Henningsson [this message]
2014-10-30  1:18   ` Raymond Yau
2014-10-30  2:24     ` Hui Wang
2014-10-30  3:33       ` Raymond Yau
2014-10-30  4:23         ` Hui Wang

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=5451446F.8020203@canonical.com \
    --to=david.henningsson@canonical.com \
    --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.