All of lore.kernel.org
 help / color / mirror / Atom feed
* Shared volume control again
@ 2014-10-29 17:02 Takashi Iwai
  2014-10-29 17:12 ` David Henningsson
  0 siblings, 1 reply; 8+ messages in thread
From: Takashi Iwai @ 2014-10-29 17:02 UTC (permalink / raw)
  To: alsa-devel; +Cc: David Henningsson

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?


Takashi

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Shared volume control again
  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-30  1:18   ` Raymond Yau
  0 siblings, 2 replies; 8+ messages in thread
From: David Henningsson @ 2014-10-29 17:12 UTC (permalink / raw)
  To: Takashi Iwai, alsa-devel



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.
And it kind of works as long as we *always* share DAC between the 
different headphones. And when we don't, they're usually both controlled 
by a vmaster anyway. I haven't seen anything else recently, are you 
planning to make "headphone" and "dock headphone" have separate volume 
controls?

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

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Shared volume control again
  2014-10-29 17:12 ` David Henningsson
@ 2014-10-29 17:17   ` Takashi Iwai
  2014-10-29 19:47     ` David Henningsson
  2014-10-30  1:18   ` Raymond Yau
  1 sibling, 1 reply; 8+ messages in thread
From: Takashi Iwai @ 2014-10-29 17:17 UTC (permalink / raw)
  To: David Henningsson; +Cc: alsa-devel

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).

> And it kind of works as long as we *always* share DAC between the 
> different headphones. And when we don't, they're usually both controlled 
> by a vmaster anyway. I haven't seen anything else recently, are you 
> planning to make "headphone" and "dock headphone" have separate volume 
> controls?

No, splitting is impossible with vmaster.


thanks,

Takashi

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Shared volume control again
  2014-10-29 17:17   ` Takashi Iwai
@ 2014-10-29 19:47     ` David Henningsson
  0 siblings, 0 replies; 8+ messages in thread
From: David Henningsson @ 2014-10-29 19:47 UTC (permalink / raw)
  To: Takashi Iwai; +Cc: alsa-devel



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

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Shared volume control again
  2014-10-29 17:12 ` David Henningsson
  2014-10-29 17:17   ` Takashi Iwai
@ 2014-10-30  1:18   ` Raymond Yau
  2014-10-30  2:24     ` Hui Wang
  1 sibling, 1 reply; 8+ messages in thread
From: Raymond Yau @ 2014-10-30  1:18 UTC (permalink / raw)
  To: David Henningsson; +Cc: Takashi Iwai, ALSA Development Mailing List

>>
>> 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.
> And it kind of works as long as we *always* share DAC between the
different headphones.

it is unlikely that dual headphone jacks share DAC on those Dell XPS
notebook with 8 channels hda codec

Surround 40 should not be supported when headphone and dock headphone
always share DAC

Are there any difference when dock station has dock line out instead of
dock headphone?

Another ad hoc case is asus g75 with vt1802 which have speaker and
subwoober,  headohone and speaker share DAC so that the subwoofer can have
volume control

For Dell alienware notebook with alc668,  headset and headphone jack, mic
jack internal 2.1 speaker

User expect the headset jack default to be used as headset since the
notebook has another headphone jack

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Shared volume control again
  2014-10-30  1:18   ` Raymond Yau
@ 2014-10-30  2:24     ` Hui Wang
  2014-10-30  3:33       ` Raymond Yau
  0 siblings, 1 reply; 8+ messages in thread
From: Hui Wang @ 2014-10-30  2:24 UTC (permalink / raw)
  To: Raymond Yau, David Henningsson
  Cc: Takashi Iwai, ALSA Development Mailing List

On 10/30/2014 09:18 AM, Raymond Yau wrote:
>>> 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.
>> And it kind of works as long as we *always* share DAC between the
> different headphones.
>
> it is unlikely that dual headphone jacks share DAC on those Dell XPS
> notebook with 8 channels hda codec
>
> Surround 40 should not be supported when headphone and dock headphone
> always share DAC
>
> Are there any difference when dock station has dock line out instead of
> dock headphone?
>
> Another ad hoc case is asus g75 with vt1802 which have speaker and
> subwoober,  headohone and speaker share DAC so that the subwoofer can have
> volume control
Hi Raymond,


It seems like you are familiar with hardware configuration for different 
machines, BTW do you know any Lenovo/Dell/HP laptops which have 
subwoofer on them?


Thanks,
Hui.

> For Dell alienware notebook with alc668,  headset and headphone jack, mic
> jack internal 2.1 speaker
>
> User expect the headset jack default to be used as headset since the
> notebook has another headphone jack
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Shared volume control again
  2014-10-30  2:24     ` Hui Wang
@ 2014-10-30  3:33       ` Raymond Yau
  2014-10-30  4:23         ` Hui Wang
  0 siblings, 1 reply; 8+ messages in thread
From: Raymond Yau @ 2014-10-30  3:33 UTC (permalink / raw)
  To: Hui Wang; +Cc: Takashi Iwai, ALSA Development Mailing List, David Henningsson

BTW do you know any Lenovo/Dell/HP laptops which have subwoofer on them?
>

https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/log/sound/pci/hda?qt=grep&q=subwoofer

https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1302090

Those dell alienware 14,17 and 18

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Shared volume control again
  2014-10-30  3:33       ` Raymond Yau
@ 2014-10-30  4:23         ` Hui Wang
  0 siblings, 0 replies; 8+ messages in thread
From: Hui Wang @ 2014-10-30  4:23 UTC (permalink / raw)
  To: Raymond Yau
  Cc: Takashi Iwai, ALSA Development Mailing List, David Henningsson

On 10/30/2014 11:33 AM, Raymond Yau wrote:
>
>
> BTW do you know any Lenovo/Dell/HP laptops which have subwoofer on them?
> >
>
> https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/log/sound/pci/hda?qt=grep&q=subwoofer
>
> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1302090
>
> Those dell alienware 14,17 and 18
>
Got it, thanks.

^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2014-10-30  4:23 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
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

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.