alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Tim <terminator356@users.sourceforge.net>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: ice1712 IPGA and ADC controls
Date: Tue, 30 Jan 2007 12:14:23 +0100	[thread overview]
Message-ID: <s5hac00ojg0.wl%tiwai@suse.de> (raw)
In-Reply-To: <loom.20070130T064723-509@post.gmane.org>

At Tue, 30 Jan 2007 06:18:38 +0000 (UTC),
Tim wrote:
> 
> John Rigg <aldev <at> sound-man.co.uk> writes:
> 
> > If a single volume bar is implemented, does it leave the analog
> > attenuation at zero and adjust the digital attenuation, or does
> > it leave the digital attenuation at zero and adjust the analog
> > attenuation? 
> There is no such thing as analog attenuation on these chips.
> Only an analog gain stage from 0db to +18, followed by a digital 
>  attenuation stage from 0db down to infinity (mute).
> Both of these functions are accessed through the same register,
>  as a continous range from 0 to 164. The first 127 steps
>  'activate' the digital attenuator, with 127 being 0db, while the
>  last 37 steps 'activate' the analog gain.
> In other words, from 0-127 ONLY the digital attenuation stage is
>  activated. From 128 to 164, ONLY the analog gain stage is activated.
> It was intended to be one control.

Exactly.  Thanks for correction.

> Anyways, I say we add some type of 'decorations' to envy24control.
> Some type of markings. Two end-to-end 'braces' along the side spanning the 
>  length of sliders, one labeled "digital att." meaning that the range from 
>  0-127 is digital attenuation, and the other labeled "analog gain" meaning 
>  the range 127-164 is analog gain. It would be a great visual reminder of 
>  this underlying technical detail we have discussed here, so everyone  
>  should understand it.
> And of course all values in db's as well as integers.

Yes.  It's the way to go, IMO.
Make the API simple.  Improve the usability in another part.

A question from usability viewpoint is what is the good way to handle
two linked volumes.  For example,

1) two volume bars can be changed at any time.  If one of them is
   changed, another is automatically set (jumps) to zero.
2) when one volume is set to non-zero, another is visiblly disabled.
   to zero and cannot be changed.  Once after both are set to zero,
   both become accessible.

I think the latter is less confusing, at least.  The jump of volume
bar always annoyed me.

Comments?  Other suggestsion?


Takashi

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

  reply	other threads:[~2007-01-30 11:14 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-20  0:39 Need help: My .asoundrc no longer works Tim
2007-01-20 14:01 ` John Rigg
2007-01-20 22:06   ` Tim
     [not found]   ` <75b66ecd0701200846q5499ccb0o5ba10c6a301d7b73@mail.gmail.com>
2007-01-21 20:02     ` John Rigg
2007-01-27  1:04       ` Tim
2007-01-22 14:06 ` Takashi Iwai
2007-01-26  1:28   ` Tim
2007-01-26 23:26     ` ice1712 IPGA and ADC controls Alan Horstmann
2007-01-27  0:42       ` Tim
2007-01-27 12:38       ` John Rigg
2007-01-28 20:54         ` Tim
2007-01-29  9:09           ` Alan Horstmann
2007-01-29  9:47             ` Fons Adriaensen
2007-01-29 16:36               ` Takashi Iwai
2007-01-28 22:59         ` Alan Horstmann
2007-01-29 12:16           ` Takashi Iwai
2007-01-29 17:07             ` Alan Horstmann
2007-01-29 17:12               ` Takashi Iwai
2007-01-29 19:15             ` John Rigg
2007-01-30  6:18               ` Tim
2007-01-30 11:14                 ` Takashi Iwai [this message]
2007-01-30 23:01                   ` Tim
2007-01-31  8:48                     ` Takashi Iwai
2007-01-31 10:33                       ` Takashi Iwai
2007-01-31 21:48                         ` Fons Adriaensen
2007-02-01 11:32                           ` Takashi Iwai
2007-02-01  5:01                         ` Tim
2007-02-01 10:08                           ` Alan Horstmann
2007-02-01 10:10                   ` Alan Horstmann
2007-02-01 12:10                     ` Takashi Iwai
2007-01-31 10:42                 ` John Rigg
2007-01-30 23:23     ` Need help: My .asoundrc no longer works Tim

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=s5hac00ojg0.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=terminator356@users.sourceforge.net \
    /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;
as well as URLs for NNTP newsgroup(s).