From: "Sebastian H." <vand2@gmx.de>
To: alsa-devel@alsa-project.org
Subject: Re: Mixer volume/decibel mapping
Date: Thu, 20 May 2010 11:41:28 +0200 [thread overview]
Message-ID: <201005201141.28755.vand2@gmx.de> (raw)
In-Reply-To: <AANLkTilKqn_X3FUdDmCqy3YKdYeT47oIGGaqUitzruDk@mail.gmail.com>
Am Donnerstag, 20. Mai 2010 10:53:14 schrieb Raymond Yau:
> 2010/5/20 James Courtier-Dutton <james.dutton@gmail.com>
>
> > On 19 May 2010 17:34, Sebastian H. <vand2@gmx.de> wrote:
> > > Hello everyone
> > >
> > > I'm working on an ALSA-Mixer application for C++/Qt4 and stumbled over
> > > volume and decibel mapping for sliders.
> > > My question: Is there always an 1 to 1 mapping from volume to decibel
> > > and
> >
> > vice
> >
> > > versa or can there be decibel values in between two volume steps?
> >
> > There should be a one to one mapping.
> > If the hardware has 200 steps on the volume scale, and those 200 steps
> > are published to the user.
> > With the dB scale, there will still be the same 200 steps in the dB
> > scale. The dB information simply helps the user interface convert each
> > step into a dB value.
>
> a stepping function is not continuous and this is why
> snd_mixer_selem_set_playback_dB() cannot set decibel values in between two
> volume steps
That's clear.
I imagined that maybe the dB scale could be the "real thing" and the volume
steps would be a convenient but possibly coarse mapping into a denser
stepped dB space provided by the hardware/driver.
This was unlikely but I wanted to ask anyway ;-).
next prev parent reply other threads:[~2010-05-20 9:41 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 16:34 Mixer volume/decibel mapping Sebastian H.
2010-05-20 7:34 ` Clemens Ladisch
2010-05-20 8:01 ` James Courtier-Dutton
2010-05-20 8:53 ` Raymond Yau
2010-05-20 9:41 ` Sebastian H. [this message]
2010-05-20 16:13 ` James Courtier-Dutton
2010-05-21 0:35 ` Raymond Yau
2010-05-21 1:30 ` Raymond Yau
2010-05-21 8:18 ` Sebastian H.
2010-06-07 3:37 ` Raymond Yau
2010-06-07 9:19 ` Sebastian H.
2010-06-08 1:03 ` Raymond Yau
2010-06-08 6:02 ` Sebastian Holtermann
2010-06-08 15:31 ` Raymond Yau
2010-06-09 10:26 ` Sebastian H.
2010-06-08 6:08 ` Sebastian H.
2010-06-09 5:39 ` Raymond Yau
2010-06-09 7:34 ` Sebastian H.
2010-06-10 0:08 ` Raymond Yau
2010-06-09 5:55 ` Raymond Yau
2010-06-08 2:23 ` Raymond Yau
2010-05-21 6:35 ` Clemens Ladisch
2010-05-21 6:51 ` Peter Ujfalusi
2010-05-21 9:56 ` Clemens Ladisch
2010-05-24 2:52 ` Raymond Yau
2010-05-25 8:38 ` Clemens Ladisch
2010-05-25 8:43 ` James Courtier-Dutton
2010-05-25 8:49 ` Clemens Ladisch
2010-05-25 23:24 ` Raymond Yau
2010-05-27 13:32 ` Colin Guthrie
2010-05-29 3:54 ` Raymond Yau
2010-05-29 1:57 ` Raymond Yau
2010-05-29 18:46 ` Colin Guthrie
2010-06-04 23:46 ` Raymond Yau
[not found] ` <AANLkTik7mD1DAVWkOwM7sNu0EfgGApvzX9WRXWBOO4PI@mail.gmail.com>
2010-05-25 8:45 ` Clemens Ladisch
2010-05-25 13:51 ` Raymond Yau
2010-05-25 14:36 ` Clemens Ladisch
2010-05-25 23:00 ` Raymond Yau
2010-05-27 0:20 ` Raymond Yau
2010-05-28 13:04 ` Raymond Yau
2010-05-28 14:10 ` Clemens Ladisch
2010-05-29 1:31 ` Raymond Yau
2010-05-21 13:16 ` James Courtier-Dutton
2010-05-25 8:21 ` Clemens Ladisch
2010-06-09 6:19 ` Raymond Yau
2010-05-22 9:24 ` Raymond Yau
2010-05-20 9:20 ` Sebastian H.
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=201005201141.28755.vand2@gmx.de \
--to=vand2@gmx.de \
--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).