From: Colin Guthrie <gmane@colin.guthr.ie>
To: alsa-devel@alsa-project.org
Subject: Re: wrong decibel data?
Date: Tue, 08 Jun 2010 16:40:22 +0100 [thread overview]
Message-ID: <hulo7u$oe7$1@dough.gmane.org> (raw)
In-Reply-To: <AANLkTil4q611GLiV-k1vO2Svepg_kioyUypp2rWNslxR@mail.gmail.com>
'Twas brillig, and Raymond Yau at 08/06/10 05:01 did gyre and gimble:
> According to your email , you mention than your hardware has a cutoff at 14%
> in PA
It's actually closer to about 16%... but in that area yes.
> the mixer application programmer can select any kind of scaling in the
> slider
Indeed, but pulseaudio exposes a pa_volume_t which is basically a linear
scale. This upper bound is exposed via a constant: PA_VOLUME_MAX
pulse/volume.h:113:#define PA_VOLUME_MAX ((pa_volume_t) UINT32_MAX-1)
And the "100%" aka 0dB point is represented by another constant,
PA_VOLUME_NORM:
pulse/volume.h:107:#define PA_VOLUME_NORM ((pa_volume_t) 0x10000U)
The scale between 0 and PA_VOLUME_NORM is linear via pa_volume_t but
this is mapped via the cubic mapping internally when controling the
volume of the alsa device.
So volume control GUIs and the ALSA plugin use this scale in a linear
fashon to represent the rand 0% (pa_volume_t = 0) to 100% (pa_volume_t =
PA_VOLUME_NORM).
> do you mean 14% in pavucontrol or Master volume control of "pulse" device ?
Both. They both use the range 0 ... PA_VOLUME_NORM to represent 0% -
100% and thus they correspond with each other fine[1]
> but pavucontrol did not provide any dB value at any point
It doesn't display the dB value, but perhaps it should? It's more of a
developer tool anyway (tho' used by a lot of users until desktop
provided tools catch up) so exposing dB here would make sense IMO. I'll
cook up a patch.
Col
1. Note that this may change at some point in the future as we define
how much to show the user as an "overdrive" of volume. As you may know,
gnome-volume-control allows a setting up to 150%, but this isn't
refelected in the alsa plugin. Ultimately we decided to define a new
constant "PA_VOLUME_OVERDRIVE" (or similar, I can't remember the exact
name) and set this to be +11dB (via the current cubic mapping function).
This approximates to the 150% offered in g-v-c.
--
Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/
Day Job:
Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
Mandriva Linux Contributor [http://www.mandriva.com/]
PulseAudio Hacker [http://www.pulseaudio.org/]
Trac Hacker [http://trac.edgewall.org/]
next prev parent reply other threads:[~2010-06-08 15:39 UTC|newest]
Thread overview: 100+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-02 18:21 wrong decibel data? Nicolo' Chieffo
2010-04-02 20:25 ` Nicolo' Chieffo
2010-04-03 10:09 ` Colin Guthrie
2010-04-03 10:48 ` Nicolo' Chieffo
2010-04-05 0:15 ` Raymond Yau
2010-04-05 8:29 ` Stereo Support in APLAY Reddy, MR Swami
2010-04-08 6:47 ` Clemens Ladisch
2010-04-04 0:09 ` wrong decibel data? Raymond Yau
2010-04-04 1:31 ` Raymond Yau
2010-04-06 0:07 ` Raymond Yau
2010-04-08 1:35 ` Raymond Yau
2010-04-16 13:48 ` Raymond Yau
2010-04-17 9:31 ` Colin Guthrie
2010-04-21 2:32 ` Raymond Yau
2010-04-21 8:06 ` Colin Guthrie
2010-04-22 1:16 ` Raymond Yau
2010-05-27 13:30 ` Colin Guthrie
2010-05-27 13:48 ` Clemens Ladisch
2010-05-27 14:43 ` Colin Guthrie
2010-05-27 17:21 ` Colin Guthrie
2010-06-06 0:12 ` Raymond Yau
2010-06-07 9:03 ` Colin Guthrie
2010-06-08 0:47 ` Raymond Yau
2010-06-08 15:30 ` Colin Guthrie
2010-06-10 3:16 ` Raymond Yau
2010-06-10 16:11 ` Colin Guthrie
2010-06-13 13:53 ` Lennart Poettering
2010-06-14 0:25 ` Raymond Yau
2010-06-14 8:33 ` Colin Guthrie
2010-06-14 8:38 ` Raymond Yau
2010-06-14 8:45 ` Raymond Yau
2010-06-14 10:17 ` Colin Guthrie
2010-06-14 18:38 ` Lennart Poettering
2010-06-14 8:56 ` James Courtier-Dutton
2010-06-14 9:54 ` Raymond Yau
2010-06-14 10:07 ` James Courtier-Dutton
2010-06-15 6:57 ` Raymond Yau
2010-06-14 18:46 ` Lennart Poettering
2010-06-14 10:22 ` Colin Guthrie
2010-06-14 10:46 ` James Courtier-Dutton
2010-06-14 11:03 ` Colin Guthrie
2010-06-14 11:29 ` Alan Horstmann
2010-06-14 12:36 ` Raymond Yau
2010-06-14 14:17 ` Colin Guthrie
2010-06-14 15:27 ` James Courtier-Dutton
2010-06-14 15:44 ` Colin Guthrie
2010-06-14 16:09 ` Mark Brown
2010-06-15 0:11 ` Raymond Yau
2010-06-22 2:31 ` Raymond Yau
2010-06-22 9:15 ` Colin Guthrie
2010-06-22 15:29 ` Raymond Yau
2010-06-22 17:05 ` Colin Guthrie
2010-06-23 1:15 ` Raymond Yau
2010-06-23 9:12 ` Colin Guthrie
2010-06-28 1:47 ` Raymond Yau
2010-06-28 8:18 ` Colin Guthrie
2010-07-01 15:03 ` Raymond Yau
2010-06-14 18:54 ` Lennart Poettering
2010-06-14 18:49 ` Lennart Poettering
2010-06-14 23:43 ` Raymond Yau
2010-06-15 16:10 ` Colin Guthrie
2010-06-14 18:41 ` Lennart Poettering
2010-06-08 4:01 ` Raymond Yau
2010-06-08 15:40 ` Colin Guthrie [this message]
2010-05-28 2:37 ` Raymond Yau
2010-05-28 2:04 ` Raymond Yau
2010-04-06 1:46 ` Raymond Yau
2010-04-06 8:01 ` Nicolo' Chieffo
2010-04-07 0:34 ` Raymond Yau
2010-04-07 8:17 ` Nicolo' Chieffo
2010-04-07 12:17 ` Nicolo' Chieffo
2010-04-07 23:38 ` Raymond Yau
2010-04-08 2:05 ` Raymond Yau
2010-04-08 12:42 ` Nicolo' Chieffo
2010-04-08 23:11 ` Raymond Yau
2010-04-09 7:30 ` Nicolo' Chieffo
2010-04-09 11:37 ` Raymond Yau
2010-04-09 11:40 ` Raymond Yau
2010-04-09 12:27 ` Nicolo' Chieffo
2010-06-24 9:53 ` Raymond Yau
2010-04-09 13:49 ` Raymond Yau
2010-04-09 13:59 ` Nicolo' Chieffo
2010-04-09 18:35 ` Nicolo' Chieffo
2010-04-10 0:27 ` Raymond Yau
2010-04-10 9:27 ` Raymond Yau
2010-04-10 9:41 ` Nicolo' Chieffo
2010-04-10 23:32 ` Raymond Yau
2010-04-11 0:02 ` Raymond Yau
2010-04-11 9:00 ` Nicolo' Chieffo
2010-04-15 3:38 ` Raymond Yau
2010-04-14 1:39 ` Raymond Yau
[not found] ` <4BBF5F81.1010205@yellowcouch.org>
2010-04-09 23:32 ` Raymond Yau
2010-04-10 6:56 ` Werner Van Belle
2010-04-10 7:23 ` Raymond Yau
2010-04-10 4:25 ` Raymond Yau
2010-04-10 6:59 ` Werner Van Belle
2010-04-10 0:11 ` Raymond Yau
2010-04-17 0:40 ` Raymond Yau
2010-04-09 0:49 ` Raymond Yau
2010-04-09 1:35 ` 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='hulo7u$oe7$1@dough.gmane.org' \
--to=gmane@colin.guthr.ie \
--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).