All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Jochen Voss <voss@seehuhn.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: [RFC] Add dB scale information to AK4xxx codec
Date: Thu, 07 Sep 2006 12:33:18 +0200	[thread overview]
Message-ID: <s5hirk0klu9.wl%tiwai@suse.de> (raw)
In-Reply-To: <20060907102954.GA17846@localhost.localdomain>

At Thu, 7 Sep 2006 11:29:54 +0100,
Jochen Voss wrote:
> 
> Hi Takashi,
> 
> On Thu, Sep 07, 2006 at 12:09:05PM +0200, Takashi Iwai wrote:
> > > > > -- s1.sh -------------------------------------------------------------
> > > > > #! /bin/sh
> > > > > amixer set "PCM Capture Gain" 2
> > > > > amixer set "PCM Capture Gain" 0
> > > > > amixer set "PCM" 0
> > > > > amixer set "PCM" 80%
> > > > > ----------------------------------------------------------------------
> > > > > 
> > > > > -- s2.sh -------------------------------------------------------------
> > > > > #! /bin/sh
> > > > > amixer set "PCM Capture Gain" 0
> > > > > amixer set "PCM Capture Gain" 2
> > > > > amixer set "PCM" 0
> > > > > amixer set "PCM" 80%
> > > > > ----------------------------------------------------------------------
> 
> > > I used 'amixer set "PCM Capture Gain" 20' now in s2.sh only.  Was this
> > > the plan?  Result: there is now an audible crack when s2.sh is
> > > executed, but the volume before and after the cracks still seems to be
> > > the same.
> > 
> > The crack doesn't matter seriously, but just the volume.
> 
> The volume is the same.
> 
> Why is everything assigned twice (e.g. first 0 then 2) in this test?
> 
> > > I also tried something else: when I alternate between
> > > ----------------------------------------------------------------------
> > > amixer set "PCM Capture Gain" 0
> > > amixer set "PCM Capture Gain" 20
> > > amixer set "PCM" 0
> > > amixer set "PCM" 80%
> > > ----------------------------------------------------------------------
> > > and
> > > ----------------------------------------------------------------------
> > > amixer set "PCM" 0
> > > amixer set "PCM" 80%
> > > amixer set "PCM Capture Gain" 0
> > > amixer set "PCM Capture Gain" 20
> > > ----------------------------------------------------------------------
> > > the recording has alternating load and quiete stretches.  Whatever this
> > > might tell us about the ADC, it looks like a bug to me: the order of
> > > setting the two controls shouldn't matter.  Or am I confused again?
> > 
> > Well, assume that "PCM Capture" and "PCM Capture Gain" are
> > independent.  If so, the above two should result in the same state.
> > 
> > If it's not independent but the register 4 & 5 take single values
> > (that was the behavior of your original implementation), the above two
> > cases must make a clear difference: in the former case, the gain is
> > below 0dB, and in the latter it's +10dB.  Was it so through your
> > tests?
> 
> Yes, the recording had alternating load and quite stretches,
> corresponding to the two settings.
> 
> So both tests seem to indicate that for the AK5365 registers 4 and 5
> take only a single value.  Correct?

Yes.  Then we need to take the controls back to a single one.
Will do later.

I still wonder whether this is also true for AK4524...


> > Also, it's possible that I did make a silly mistake.  Put a debug
> > printk around ak->ops.write() in snd_akm4xxx_write() to check what
> > values are written to register 4 and 5.
> 
> I will try this in the evening.

Thanks,


Takashi

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

  reply	other threads:[~2006-09-07 10:33 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-28 11:38 [RFC] Add dB scale information to AK4xxx codec Takashi Iwai
2006-08-28 14:52 ` Takashi Iwai
2006-09-03 15:53 ` Jochen Voss
2006-09-04  9:58   ` Takashi Iwai
2006-09-04 11:13     ` Jochen Voß
2006-09-04 11:35       ` Takashi Iwai
2006-09-04 12:12         ` Jochen Voß
2006-09-04 17:41       ` Jochen Voss
2006-09-04 18:28         ` Takashi Iwai
2006-09-04 19:27           ` Jochen Voss
2006-09-05  9:36             ` Takashi Iwai
2006-09-05 19:24               ` Jochen Voss
2006-09-07 10:09                 ` Takashi Iwai
2006-09-07 10:29                   ` Jochen Voss
2006-09-07 10:33                     ` Takashi Iwai [this message]
2006-09-07 11:00                       ` Jochen Voss
2006-09-07 12:49                         ` Takashi Iwai
2006-09-07 14:52                           ` Takashi Iwai
2006-09-07 22:18                             ` Jochen Voss
2006-09-08 10:32                               ` Takashi Iwai
2006-09-10 22:38                                 ` Jochen Voss

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=s5hirk0klu9.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=voss@seehuhn.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.