Re: [Audacity-devel] [Audacity-quality] Bug 243 -- Default EQCurves.xml should be populated and added to Windows and Mac installers

[Martyn S. <mar...@gm...>]

On 01/12/2010 14:53, Gale Andrews wrote:
>
> | From Vaughan Johnson<va...@au...>
> | Tue, 30 Nov 2010 17:48:27 -0800
> | Subject: [Audacity-quality] Bug 243 – Default EQCurves.xml should be
> | populated and added to Windows and Mac installers
>> http://bugzilla.audacityteam.org/show_bug.cgi?id=243
>>
>> Is this bug resolved? I fixed it on Windows, and I think Peter resolved
>> it for Mac. Linux gets it in tarball?
>
> Not resolved, because needs more testing and deciding what priority
> to give to any remaining issues.

So please get to that Gale.  This testing is more important than 
responding to feedback@, which only affects one user at a time.  P2s 
affect the world user base (millions?), feedback@ just affects a few 
dozen nincompoops a week, from what I've seen.  Each nincompoop is an 
important person, but we should use our best resources effectively, 
not let them suck-up our time which we could use for the greater good.

I don't think the issue of where to
> place EQCurves.xml on Linux after compilation and installation of
> Audacity has received any discussion yet by a Linux developer.
>
> I assume by "Peter" you mean Paul Livesey, as per this thread:
> http://audacity.238276.n2.nabble.com/Mac-build-td5640929.html
>
> Clearly Bill has highlighted Mac-specific issues with EQCurves.xml
> in this -quality list thread:
> http://tinyurl.com/2u253ho

which he mostly retracted as a misunderstanding: "This appears to
simply be an issue of better instructions on the wiki page".

> e.g. Audacity does not seem to be looking in the application dir for
> EQCurves.xml. The issue can't be considered properly for Mac until
> it can be tested in the Mac Nightly Build. I'm including EQCurves.xml
> in the Win "Nightlies".

Good.  This was a misunderstanding.  From what I see from Bill it 
should work fine.

> More generally, I'm not convinced what happens for user when they
> upgrade from 1.3.12 to 1.3.13 (or start as a new user with 1.3.13)
> and come across EQCurves.xml is an easy-to-understand experience.

Evidence?

> One reason I haven't moved this issue along is because I want to test
> this properly. As an example, if EQCurves.xml in the app dir is
> read-only in usage, why allow Audacity to overwrite it?

See http://audacity.238276.n2.nabble.com/Mac-build-td5640929.html. 
Audacity won't overwrite the default file, so it doesn't matter if it 
is r/w or not.

> Personally I think it highly confusing to have two files with the same
> name in the app dir and the data dir,

You are not the average/below average user that you generally quote.

  but I'm not going to say any more
> until I can test it and see if any detail improvements can be made to
> the current implementation.

Thanks!  Good luck with those tests!  I'm sure you'll detail test 
methodology and reasoning when you report back.

  I understand the expediency of not
> writing and testing more code, but what we have now seems clunky
> and non-trivial to test to me. Yes, not building the curves in allows
> "easy updates to the defaults, without a re-compile", but that isn't
> really a user benefit.
>
> Finally (although possibly not now P2), issues with what exact curves
> to include and their properties isn't finalised IMO. Bill has issues I
> think with the Treble/Bass Cut/Boost which I believe he will post to:
> http://wiki.audacityteam.org/wiki/Default_EQCurves

and I have responded there

> and I'm not convinced we should have no 78 rpm curves at all. There
> is definitely a problem that to be useful, there probably needs to be
> at least three 78 rpm curves, but I don't think that's an excessive
> number.

So which ones?  http://wiki.audacityteam.org/wiki/Default_EQCurves 
would be a good place to discuss / propose them.

TTFN
Martyn

> Gale
>
>
> ------------------------------------------------------------------------------
> Increase Visibility of Your 3D Game App&  Earn a Chance To Win $500!
> Tap into the largest installed PC base&  get more eyes on your game by
> optimizing for Intel(R) Graphics Technology. Get started today with the
> Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
> http://p.sf.net/sfu/intelisp-dev2dev
> _______________________________________________
> audacity-devel mailing list
> aud...@li...
> https://lists.sourceforge.net/lists/listinfo/audacity-devel