All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Henningsson <david.henningsson@canonical.com>
To: "Nathanael D. Noblet" <nathanael@gnat.ca>
Cc: alsa-devel@alsa-project.org
Subject: Re: Internal Mic Boost channel is unused
Date: Thu, 10 Oct 2013 15:33:07 +0200	[thread overview]
Message-ID: <5256AC93.6050400@canonical.com> (raw)
In-Reply-To: <5255B550.6070001@gnat.ca>

On 10/09/2013 09:58 PM, Nathanael D. Noblet wrote:
> On 10/09/2013 01:46 PM, Nathanael D. Noblet wrote:
>> On 09/16/2013 03:57 PM, David Henningsson wrote:
>>> Matching this with your alsa-info, we can see that 'Mic Jack'
>>> corresponds to 0x1b and 'Mic Jack', index=1 corresponds to 0x1a.
>>>
>>> Hence you could try turning pin 0x1a to "not connected" in
>>> hda-jack-retask. (I don't know how/if hda-jack-retask is packaged in
>>> Fedora, but it is part of alsa-tools.)
>>>
>>> If this resolves your problem, we could then try making that the default
>>> in upcoming kernels, but the question is we really dare to do that,
>>> without clear confirmation that 0x1a is actually useless. In current
>>> state it's a bit buggy, but if the headphone jack is actually a headset
>>> jack turning that off would make the headset mic go from "needs manual
>>> adjustment to work" to "completely unusuable".
>>
>> So that adjustment allows the internal microphone to be useable. However
>> the mic in jack is now completely unusable. With a headset or a plain
>> microphone.
>>
>> Thoughts?
> 
> 
> Actually I was wrong. I plugged it into the wrong jack. With that retask
> everything seems to work now. Plugging in a microphone into the mic jack
> picks up that audio, unplugging it uses the built in mic. So that's
> good. What's the next step?

Ok, so I made a patch (just sent it) that properly names the headset mic
as such, so we don't end up with "Mic" and "Mic 1" but "Mic" and
"Headset Mic" instead.

It is a step in the right direction and I encourage you to test it - but
it does not solve the more difficult problem with the parser: that all
three inputs go through node 0x17, and that node gets a control "xxx
Boost" that's named after one of them, without indication that it
actually controls boost for all three of them.


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

  reply	other threads:[~2013-10-10 13:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-12 15:52 Internal Mic Boost channel is unused Nathanael D. Noblet
2013-09-12 18:43 ` David Henningsson
2013-09-12 19:17   ` Nathanael D. Noblet
2013-09-13  3:23 ` Raymond Yau
2013-09-13 16:04 ` Nathanael D. Noblet
2013-09-14  0:34   ` David Henningsson
2013-09-16 15:14     ` Nathanael D. Noblet
2013-09-16 21:57       ` David Henningsson
2013-09-18 15:28         ` Nathanael D. Noblet
2013-10-09 19:46         ` Nathanael D. Noblet
2013-10-09 19:58           ` Nathanael D. Noblet
2013-10-10 13:33             ` David Henningsson [this message]
2013-09-14  2:23   ` Raymond Yau
2013-09-14  4:14   ` 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=5256AC93.6050400@canonical.com \
    --to=david.henningsson@canonical.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=nathanael@gnat.ca \
    /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.