[PATCH] Spectrum views enhancement & small eq fixes

On 27 Feb 2008, at 13:39, [email protected] wrote:
> On Wed Feb 27  9:34 , Raphaël Doursenaud  sent:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Jan Depner a écrit :
>>> On Wed, 2008-02-27 at 01:05 +0100, Raphaël Doursenaud wrote:
>>>> [...]
>>>>
>>>> 1) Relabeled geq sliders with correct frequency.
>>>>
>>>
>>>   I have no idea what the "correct" frequencies are.  Neither what  
>>> we
>>> have now nor what you have done matches any 31 band GEQ I've ever  
>>> seen.
>>> I'll wait for Steve to chime in on that one ;-)  One of the  
>>> reasons for
>>> not using 31.5 and 1k25 and 3k15, etc. was to save screen real  
>>> estate.
>>> We really don't need to be exact anyway.  I'm more concerned about
>>> completely eating up every square mm of screen space.
>>
>> Well "correct" might not be the word.
>>
>> Uncommenting this around line 169 in process.c :
>> //printf("band %d = %fHz\n", i, centre);
>> provides the hyper precise floating point frequencies.
>>
>> These are 1/3 octaves like on most professional geq in the market  
>> (See
>> for ex.
>> http://www.klarkteknik.com/images/content/products/product_shots/dn9331/dn9331-front.jpg) 
>> .
>> This is what we should expect from a third octave geq, anything  
>> else is
>> just distracting.
>
>   It's fine with me.  This doesn't match my hardware 31 band GEQ but  
> it makes
> sense to me as it is in the software one.

I don't quite remember how got what we did, but like Jan said the  
prime concern was screen realestate.
Due to the way it's measured the low frequencies are quite inaccurate,  
FWIW.

 From what I remember, I just read the ISO spec for EQ displays and  
implemented what it says.

- Steve


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/