From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: James Courtier-Dutton <james.dutton@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Verifying mixer dB data/Invalid dB data from USB cards, especially Aureon 5.1 MkII
Date: Wed, 17 Feb 2010 13:06:23 +0000 [thread overview]
Message-ID: <20100217130623.GD2032@sirena.org.uk> (raw)
In-Reply-To: <ad2655cb1002170355n7d2df930ha6cf036b6e00218@mail.gmail.com>
On Wed, Feb 17, 2010 at 11:55:17AM +0000, James Courtier-Dutton wrote:
> On 16 February 2010 23:56, Lennart Poettering <mznyfn@0pointer.de> wrote:
> >
> > The reason I was asking how Jaroslav chose the 0dB position for his
> > measurements was purely because I wanted to do my own measurements for
> > that Aureon card. The dbmeasure tool I wrote for stuff like that puts
> > 0dB at max amplification, however Jaroslav didn't, so I was wondering
> > how he chose 0dB then.
> >
> > Lennart
> >
>
> I think the digital side is clear. So I will not go into that.
>
> I think we need to separate the analogue side into a number of categories:
> 1) Standard consumer line-out levels.
> 2) Standard pro line-out levels.
> 3) Consumer line-in levels.
> 4) Pro line-in levels.
> 5) Consumer mic levels.
> 6) Pro mic levels.
> 7) Consumer speaker levels.
> 8) Pro speaker levels.
There's also headphones there, though for both speakers and headphones
it's questionable if we want to do anything.
> On the analogue side, I believe the 0dB gain point is intended to be
> the point at which one can be fairly sure that the distortion will be
> low for a sensible full scale input.
Generally 0dB is pass through (which does also tend to be the optimal
performance point). Actual expected gain levels will vary depending on
application - for example, a microphone input will usually need an
amplifier with fairly high gain in the path to get the signal to a level
usable by the rest of the system.
next prev parent reply other threads:[~2010-02-17 13:06 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 [this message]
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
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=20100217130623.GD2032@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=james.dutton@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;
as well as URLs for NNTP newsgroup(s).