mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "Daniel J Blueman" <daniel.blueman@gmail.com>
Cc: "Vegard Nossum" <vegard.nossum@gmail.com>,
	"Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: ALC883 recording troubles...
Date: Thu, 12 Jun 2008 17:18:58 +0200	[thread overview]
Message-ID: <s5h4p7yr89p.wl%tiwai@suse.de> (raw)
In-Reply-To: <6278d2220806120758y38d9b431td3996a3cef73bb50@mail.gmail.com>

At Thu, 12 Jun 2008 15:58:30 +0100,
Daniel J Blueman wrote:
> 
> On Thu, Jun 12, 2008 at 3:23 PM, Takashi Iwai <tiwai@suse.de> wrote:
> > At Thu, 12 Jun 2008 16:18:14 +0200,
> > Vegard Nossum wrote:
> >>
> >> On Thu, Jun 12, 2008 at 4:02 PM, Takashi Iwai <tiwai@suse.de> wrote:
> >> > At Thu, 12 Jun 2008 15:55:45 +0200,
> >> > Vegard Nossum wrote:
> >> >>
> >> >> On Thu, Jun 12, 2008 at 3:52 PM, Takashi Iwai <tiwai@suse.de> wrote:
> >> >> > At Thu, 12 Jun 2008 15:48:32 +0200,
> >> >> > Vegard Nossum wrote:
> >> >> >>
> >> >> >> The external mic:
> >> >> >>
> >> >> >> Node 0x18 [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out
> >> >> >>   Amp-In caps: ofs=0x00, nsteps=0x02, stepsize=0x4f, mute=0
> >> >> >>   Amp-In vals:  [0x00 0x00]
> >> >> >
> >> >> > The input volume is zero.  Try to raise "Mic Boost" (if present)?
> >> >>
> >> >> They're already all up.
> >> >>
> >> >> Line In Boost = 100
> >> >> Mic Boost = 100
> >> >> Internal Mic Boost = 100
> >> >>
> >> >> Right after changing all these to max, I've read the value from
> >> >> card0/codec#0 again:
> >> >>
> >> >> Node 0x18 [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out
> >> >>   Amp-In caps: ofs=0x00, nsteps=0x02, stepsize=0x4f, mute=0
> >> >>   Amp-In vals:  [0x00 0x00]
> >> >>
> >> >> There doesn't seem to be any difference. Even when changing them all
> >> >> to 0 in alsamixer, this output stays the same.
> >> >
> >> > Weird.  What happens if you execute the verb directly via hda-verb
> >> > program like below?
> >> >        hda-verb /dev/snd/hwC0D0 0x18 SET_AMP 0x7002
> >> >
> >>
> >> Yep, this has the same effect has changing the "Mic Boost" control in
> >> the Playback section of alsamixer.
> >>
> >> What I discovered now, though, is that I get a much wider range of
> >> values from the external mic (so playback of the captured data
> >> actually sounds correct). It actually works, but there is still a very
> >> strong DC offset that seems dependent on the level of the "Capture"
> >> control. This offset still makes it unusable for recording, since even
> >> slightly louder noises will clip the samples.
> >>
> >> It also seems that this control is reset each time I start Audacity
> >> (even though the "Mic boost" level in alsamixer doesn't change). But I
> >> guess this unrelated to the DC offset issue.
> >>
> >> Changing the voltage level now (0x21, 0x22, 0x24, with Mic Boost at
> >> 0x02) doesn't change the DC offset, but has the same effect as before
> >> (the values fluctuate, but eventually stabilize at the same level).
> >
> > Hmm, then it's all what I can guess right now.
> > There might be some vendor-specific settings I don't know of.
> 
> Maybe. I can readily dump the PCI config space of the Intel HD-audio
> controller in Windows and list differences; the datasheet from Intel
> allows us to decode the registers. Will this help us any? Of course,
> we really need to dump the target behind the HD-bus, but that's
> another matter...

I don't think it's an issue of PCI register but rather codec setups.
PCI registers cannot influence on an analog thing like DC offset.
So, we need to peek the HD-audio codec registers if really doing so.


Takashi

  reply	other threads:[~2008-06-12 15:19 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-09 19:59 Daniel J Blueman
2008-06-10  5:59 ` Takashi Iwai
2008-06-11 19:00   ` Daniel J Blueman
2008-06-11 21:37     ` Daniel J Blueman
2008-06-12 10:45       ` Takashi Iwai
2008-06-12 10:49     ` Takashi Iwai
2008-06-12 13:03       ` Vegard Nossum
2008-06-12 13:12         ` Takashi Iwai
2008-06-12 13:48           ` Vegard Nossum
2008-06-12 13:52             ` Takashi Iwai
2008-06-12 13:55               ` Vegard Nossum
2008-06-12 14:01                 ` Vegard Nossum
2008-06-12 14:13                   ` Takashi Iwai
2008-06-12 14:02                 ` Takashi Iwai
2008-06-12 14:18                   ` Vegard Nossum
2008-06-12 14:23                     ` Takashi Iwai
2008-06-12 14:58                       ` Daniel J Blueman
2008-06-12 15:18                         ` Takashi Iwai [this message]
2008-06-12 16:55                       ` Vegard Nossum
2008-06-12 17:29                         ` Vegard Nossum
2008-06-12 17:53                           ` Takashi Iwai
2008-06-12 18:31                             ` Vegard Nossum
2008-06-12 21:50       ` Daniel J Blueman
2008-06-13 10:38         ` Romano Giannetti
2008-06-28  0:05       ` Daniel J Blueman
     [not found]         ` <19f34abd0806280311s115062e6vc6d0f304cb744934@mail.gmail.com>
     [not found]           ` <6278d2220806280329j2f77c52dp8fbae78420c136c1@mail.gmail.com>
2008-06-28 12:29             ` Daniel J Blueman
2008-06-28 12:39               ` Vegard Nossum
2008-06-28 13:24                 ` Daniel J Blueman
2008-06-28 13:46                   ` Vegard Nossum
2008-06-29 17:29                   ` Romano Giannetti
2008-06-29 21:33                     ` Daniel J Blueman
2008-08-14 19:10             ` Daniel J Blueman
2008-08-15 14:42               ` Takashi Iwai
2008-08-15 22:01                 ` Daniel J Blueman
2008-08-16  8:38                   ` Takashi Iwai
2008-08-16 13:37                     ` Daniel J Blueman
2008-08-16 17:00                       ` Takashi Iwai
2008-08-16 17:33                         ` Daniel J Blueman
2008-08-17  8:04                           ` Takashi Iwai
2008-06-10 12:22 ` Romano Giannetti
2008-06-10 12:53   ` Vegard Nossum

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=s5h4p7yr89p.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=daniel.blueman@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vegard.nossum@gmail.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

all inboxes | Powered by JetHome®