Return-Path: Received: from mx1.suse.de (ns.suse.de [195.135.220.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mx1.suse.de", Issuer "Thawte Premium Server CA" (verified OK)) by ozlabs.org (Postfix) with ESMTP id 517F767A5C for ; Wed, 17 May 2006 22:35:46 +1000 (EST) Date: Wed, 17 May 2006 14:35:40 +0200 Message-ID: From: Takashi Iwai To: Johannes Berg Subject: Re: [Alsa-devel] [RFC] alsa integer control ranges In-Reply-To: <1147868218.15507.4.camel@johannes> References: <1147780945.29795.110.camel@johannes> <1147817023.6753.5.camel@localhost.localdomain> <1147868218.15507.4.camel@johannes> MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: ALSA development , Benjamin Berg , linuxppc-dev list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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