From: John Rigg <aldev@sound-man.co.uk>
To: alsa-devel@lists.sourceforge.net
Subject: Re: ice1712 IPGA and ADC controls
Date: Mon, 29 Jan 2007 19:15:51 +0000 [thread overview]
Message-ID: <20070129191551.GA2673@localhost.localdomain> (raw)
In-Reply-To: <s5h7iv61116.wl%tiwai@suse.de>
On Mon, Jan 29, 2007 at 01:16:05PM +0100, Takashi Iwai wrote:
> At Sun, 28 Jan 2007 22:59:52 +0000,
> Well, the ice1712 hardware is somehow strange. On this chip, both the
> analog attenuation and the IPGA are connected with each other, and can
> _not_ be controlled separately. That is, when you set analog
> attenuation to non-zero, you cannot set IPGA at all. Similarly, if
> you set IPGA non-zero, analaog attenuation must be zero. Hence,
> recent implementation is the straightforward implementation from the
> hardware perspective.
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? If I had to choose one or the other it would usually
be the latter. Digital and analog attenuation are not the same in
terms of quality, especially when the digital attenuation acts on
integer samples as opposed to floating point.
I can see the argument for making it simple for the non-technical
user, but the quality level required by the pro/semi-pro user must
still be attainable. Personally I'd rather see both sets of controls
in the driver, even if only one volume bar appears in the mixer app.
At least then there's still the option of controlling one or the other
(even if it means patching envy24control ;-)).
John
-------------------------------------------------------------------------
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
next prev parent reply other threads:[~2007-01-29 19:15 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 [this message]
2007-01-30 6:18 ` Tim
2007-01-30 11:14 ` Takashi Iwai
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=20070129191551.GA2673@localhost.localdomain \
--to=aldev@sound-man.co.uk \
--cc=alsa-devel@lists.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).