From: Takashi Iwai <tiwai@suse.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: ALSA development <alsa-devel@alsa-project.org>,
Benjamin Berg <benjamin@sipsolutions.net>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: [Alsa-devel] [RFC] alsa integer control ranges
Date: Wed, 17 May 2006 14:35:40 +0200 [thread overview]
Message-ID: <s5hd5ec4yn7.wl%tiwai@suse.de> (raw)
In-Reply-To: <1147868218.15507.4.camel@johannes>
At Wed, 17 May 2006 14:16:58 +0200,
Johannes Berg wrote:
>
> On Wed, 2006-05-17 at 11:59 +0200, Takashi Iwai wrote:
>
> > We have several issuess regarding the conversion of dB <-> raw volume
> > values:
> >
> > - some codecs use linear volume
> > - some codecs have non-linear dB slopes
>
> And I made a huge table so that the slope is linear! Otherwise it'd have
> been logarithmic. Anything else is pretty user-unfriendly though.
It's not the question of user-friendliness. As the end result, the dB
expression would be the best for users. No doubt.
The question is where to implement a huge table or a complex
conversion function -- whether in the driver or in alsa-lib.
Takashi
next prev parent reply other threads:[~2006-05-17 12:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-16 12:02 [RFC] alsa integer control ranges Johannes Berg
2006-05-16 12:27 ` [Alsa-devel] " Takashi Iwai
2006-05-16 22:03 ` Benjamin Herrenschmidt
2006-05-17 9:59 ` Takashi Iwai
2006-05-17 12:16 ` Johannes Berg
2006-05-17 12:35 ` Takashi Iwai [this message]
2006-05-17 12:39 ` Johannes Berg
2006-05-17 21:41 ` Benjamin Herrenschmidt
2006-05-17 12:17 ` Johannes Berg
2006-05-17 12:37 ` Takashi Iwai
2006-05-16 12:31 ` Jaroslav Kysela
2006-05-16 22:04 ` Benjamin Herrenschmidt
2006-05-17 6:41 ` Jaroslav Kysela
2006-05-17 12:21 ` Johannes Berg
2006-05-17 9:47 ` Takashi Iwai
2006-05-17 12:24 ` Johannes Berg
2006-05-16 14:53 ` Lee Revell
2006-05-16 14:55 ` Johannes Berg
2006-05-17 15:38 ` Wolfgang Pfeiffer
2006-05-16 22:00 ` Benjamin Herrenschmidt
2006-05-16 22:04 ` [Alsa-devel] " Lee Revell
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=s5hd5ec4yn7.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=benjamin@sipsolutions.net \
--cc=johannes@sipsolutions.net \
--cc=linuxppc-dev@ozlabs.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).