From: Raymond Yau <superquad.vortex2@gmail.com>
To: alsa-devel@alsa-project.org
Subject: Re: Verifying mixer dB data/Invalid dB data from USB cards, especially Aureon 5.1 MkII
Date: Wed, 24 Feb 2010 15:30:53 +0800 [thread overview]
Message-ID: <4f3252891002232330q15a67b2csc2c44ccb84ced3d1@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1002200938561.28127@eeebox2.perex-int.cz>
2010/2/20 Jaroslav Kysela <perex@perex.cz>
> On Fri, 19 Feb 2010, James Courtier-Dutton wrote:
>
> > On 19 February 2010 08:17, Jaroslav Kysela <perex@perex.cz> wrote:
> >> On Thu, 18 Feb 2010, Lennart Poettering wrote:
> >>
> >>>> For the Mic Boost +20dB case , how PA handle this +20dB switch in the
> "Flat
> >>>> Volume" model if you did not expost the Mic Boost switch to the user
> in the
> >>>> mixer control ?
> >>>>
> >>>> +20dB is quite significant in with the Capture Volume control
> >>>
> >>> We currently don't cover boost switches, simply because tehre is no dB
> >>> data queriable for them.
> >>>
> >>> I'd really prefer if those boost switches would be turned into binary
> >>> volume elements which carry normal dB information like any other
> >>> volume element. After all they are just a volume element, with only
> >>> two steps.
> >>
> >> I like this idea.
> >>
> >
> > Seems like a good idea but what should we call it.
> > If we already have a mic capture gain control, what shall we call the
> > mic boost gain control so as not to confuse it with each other?
> > Would keeping its current name be OK?
>
> I would keep the Boost suffix. It's easy to understand.
>
> Jaroslav
>
> -
Some HDA codec has Front Mic Boost and Mic Boost and three sets of input
sources
it is not easy to know the exact audio path
Card hw:1 'Intel'/'HDA Intel at 0xff9f4000 irq 22'
Mixer name : 'Analog Devices AD1988'
Components : 'HDA:11d41988'
Controls : 48
Simple ctrls : 26
control.25 {
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 3'
comment.dbmin 0
comment.dbmax 3000
iface MIXER
name 'Front Mic Boost'
value.0 0
value.1 0
}
control.26 {
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 3'
comment.dbmin 0
comment.dbmax 3000
iface MIXER
name 'Mic Boost'
value.0 0
value.1 0
}
control.27 {
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 54'
comment.dbmin -5850
comment.dbmax 2250
iface MIXER
name 'Capture Volume'
value.0 39
value.1 39
}
control.28 {
comment.access 'read write'
comment.type BOOLEAN
comment.count 2
iface MIXER
name 'Capture Switch'
value.0 false
value.1 false
}
control.29 {
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 54'
comment.dbmin -5850
comment.dbmax 2250
iface MIXER
name 'Capture Volume'
index 1
value.0 39
value.1 39
}
control.30 {
comment.access 'read write'
comment.type BOOLEAN
comment.count 2
iface MIXER
name 'Capture Switch'
index 1
value.0 false
value.1 false
}
control.31 {
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 54'
comment.dbmin -5850
comment.dbmax 2250
iface MIXER
name 'Capture Volume'
index 2
value.0 39
value.1 39
}
control.32 {
comment.access 'read write'
comment.type BOOLEAN
comment.count 2
iface MIXER
name 'Capture Switch'
index 2
value.0 false
value.1 false
}
control.33 {
comment.access 'read write'
comment.type ENUMERATED
comment.count 1
comment.item.0 'Front Mic'
comment.item.1 Line
comment.item.2 Mic
comment.item.3 CD
comment.item.4 Mix
iface MIXER
name 'Input Source'
value Mic
}
control.34 {
comment.access 'read write'
comment.type ENUMERATED
comment.count 1
comment.item.0 'Front Mic'
comment.item.1 Line
comment.item.2 Mic
comment.item.3 CD
comment.item.4 Mix
iface MIXER
name 'Input Source'
index 1
value 'Front Mic'
}
control.35 {
comment.access 'read write'
comment.type ENUMERATED
comment.count 1
comment.item.0 'Front Mic'
comment.item.1 Line
comment.item.2 Mic
comment.item.3 CD
comment.item.4 Mix
iface MIXER
name 'Input Source'
index 2
value 'Front Mic'
}
next prev parent reply other threads:[~2010-02-24 7:30 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-15 19:24 Verifying mixer dB data/Invalid dB data from USB cards, especially Aureon 5.1 MkII Lennart Poettering
2010-02-16 8:08 ` Clemens Ladisch
2010-02-16 8:24 ` Jaroslav Kysela
2010-02-16 14:32 ` Lennart Poettering
2010-02-16 14:40 ` Mark Brown
2010-02-16 15:40 ` Lennart Poettering
2010-02-16 15:49 ` Mark Brown
2010-02-16 16:29 ` Jaroslav Kysela
2010-02-16 21:07 ` Lennart Poettering
2010-02-16 22:39 ` Mark Brown
2010-02-16 22:42 ` Lennart Poettering
2010-02-16 23:38 ` Mark Brown
2010-02-16 23:56 ` Lennart Poettering
2010-02-17 11:17 ` Mark Brown
2010-02-17 13:01 ` Lennart Poettering
2010-02-17 13:15 ` Mads Kiilerich
2010-02-17 11:55 ` James Courtier-Dutton
2010-02-17 13:06 ` Mark Brown
2010-03-20 7:58 ` Raymond Yau
2010-02-18 1:48 ` Raymond Yau
2010-02-18 2:37 ` Lennart Poettering
2010-02-18 6:15 ` Raymond Yau
2010-02-18 10:11 ` James Courtier-Dutton
2010-02-18 18:13 ` Lennart Poettering
2010-02-19 8:17 ` Jaroslav Kysela
2010-02-19 9:40 ` Mark Brown
2010-02-19 10:57 ` Raymond Yau
2010-02-19 15:13 ` Lennart Poettering
2010-02-21 3:49 ` Raymond Yau
[not found] ` <20100221193933.GA31800@tango.0pointer.de>
2010-02-23 4:47 ` Raymond Yau
2010-02-23 22:20 ` Lennart Poettering
2010-02-24 1:52 ` Raymond Yau
2010-02-28 7:32 ` Raymond Yau
2010-02-23 5:12 ` Raymond Yau
2010-02-23 8:43 ` Raymond Yau
2010-02-21 4:01 ` Raymond Yau
[not found] ` <20100221192951.GD30380@tango.0pointer.de>
2010-02-23 10:08 ` Clemens Ladisch
2010-02-23 12:46 ` Raymond Yau
2010-02-23 22:32 ` Lennart Poettering
2010-02-24 0:57 ` Raymond Yau
2010-02-24 9:00 ` Clemens Ladisch
2010-02-24 11:49 ` Raymond Yau
2010-02-24 12:07 ` Raymond Yau
2010-02-24 1:12 ` Raymond Yau
2010-02-24 3:49 ` Raymond Yau
2010-02-20 8:38 ` Jaroslav Kysela
2010-02-25 3:34 ` Raymond Yau
2010-02-19 11:47 ` James Courtier-Dutton
2010-02-19 15:10 ` Lennart Poettering
2010-02-20 8:41 ` Jaroslav Kysela
2010-02-24 7:30 ` Raymond Yau [this message]
2010-02-25 13:14 ` Raymond Yau
2010-02-25 3:51 ` Raymond Yau
2010-02-26 3:17 ` Raymond Yau
2010-03-01 4:21 ` Raymond Yau
2010-02-16 23:47 ` Eliot Blennerhassett
2010-02-17 0:10 ` Lennart Poettering
2010-02-17 0:43 ` Mark Brown
2010-02-17 0:52 ` Eliot Blennerhassett
2010-02-17 11:50 ` Mark Brown
2010-02-17 9:04 ` Jaroslav Kysela
2010-02-17 12:06 ` Mark Brown
2010-02-17 13:15 ` Lennart Poettering
2010-02-17 13:32 ` Mark Brown
2010-02-17 13:06 ` Lennart Poettering
2010-02-17 13:55 ` James Courtier-Dutton
2010-02-17 14:12 ` Mark Brown
2010-02-17 14:35 ` Lennart Poettering
2010-02-17 16:17 ` James Courtier-Dutton
2010-02-26 9:38 ` Raymond Yau
2010-02-17 7:37 ` Raymond Yau
2010-02-18 2:11 ` Raymond Yau
2010-02-26 0:45 ` Raymond Yau
2010-02-20 7:24 ` Raymond Yau
2010-03-26 4:26 ` Raymond Yau
2010-02-16 21:48 ` James Courtier-Dutton
2010-02-17 8:08 ` Jaroslav Kysela
2010-06-14 3:30 ` Raymond Yau
2010-02-16 16:09 ` Jaroslav Kysela
2010-02-16 14:26 ` Lennart Poettering
2010-02-17 3:30 ` Raymond Yau
2010-02-17 15:19 ` Lennart Poettering
2010-03-08 9:06 ` Raymond Yau
2010-02-16 8:32 ` Jaroslav Kysela
2010-02-16 10:36 ` Jaroslav Kysela
2010-02-17 3:44 ` Raymond Yau
2010-02-17 12:54 ` Lennart Poettering
2010-02-26 5:18 ` Raymond Yau
2010-02-27 1:07 ` Raymond Yau
2010-03-01 0:51 ` Raymond Yau
2010-06-24 22:51 ` 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=4f3252891002232330q15a67b2csc2c44ccb84ced3d1@mail.gmail.com \
--to=superquad.vortex2@gmail.com \
--cc=alsa-devel@alsa-project.org \
/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).