Re: [Audacity-devel] Added VBR and joint stereo/stereo to MP3 export
A free multi-track audio editor and recorder
Brought to you by:
aosiniao
|
From: <ga...@au...> - 2007-03-22 06:39:31
|
| From Leland <aud...@ho...>
| Thu, 22 Mar 2007 00:37:02 -0500
| Subject: [Audacity-devel] Added VBR and joint stereo/stereo to MP3 export
| On 3/20/07 3:28 AM, "Leland" <aud...@ho...> wrote:
| >
| > Option 2:
| >
| > 1) Check preferences for a previously found library
| > If found, use it. Otherwise, continue.
| > 2) Attempt to load the library through default search order
| > If found, use it. Otherwise, continue.
| > 3) Attempt to load the library from the compiled in path
| > If found, use it. Otherwise, continue.
| > 4) Ask the user to find the library
| >
| I've just committed changes to re-add the Blade API usage on Windows while
| updating it to support the channel mode support and VBR.......
This is a good result I think.....
| Gale, I know you didn't what the dialog to pop up if you click "Find
| Library" in preferences. I believe you wanted to go directly to the file
| selector dialog. But, I got to thinking about it and realized that if we do
| that, the user would (possibly) never ee the "Download" button.
Yes, I did not think we needed the dialogue when you go to Find Library in
Preferences, if we could put the download link (or button, if it's a button)
in the MP3 Export Setup panel in Prefs. That's what I meant when I said
"Is this dialogue needed at all when you click "Browse" or "Find Library" in
Preferences i.e. if it says there "not found" perhaps the user could just click
"browse for library" or on the link if we could put it there in the Preferences
tab?"
If we can put the download button in the Prefs, seems a lot neater to me
and less irritating if the user has had to be spoon fed about how to go to
Prefs to locate lame, and then he clicks "Find Library" and next has to click
"browse" in the dialogue as well? I do agree they need to see the download
button somewhere if they go in via Prefs.
| Dominic, have you decided on ".so" or ".dylib" yet? :-)
If that means 1.3.2/1.2.5 need "dylib", and we can change the
libmp3lame-osx-universal-3.97.zip, then surely it has to contain ".dylib"
doesn't it, for backwards compatibility? Otherwise everyone who has
1.3.2/1.2.5 will have to update to 1.3.3/1.2.6 (and until those come out,
the library does not work at all).
Gale
Outbound message virus free.
Tested on: 3/22/2007 6:39:29 AM
|