I'd like to update this with a few additional changes which will
I think be of interest to the average user. This also fixes the remaining
typo and inconsistent use of "." at ends of sentences. I suggest this
same text is used for the website (as we did for 1.3.3). Will do this
unless anyone suggests further changes.
Changes in 1.3.5:
Recording / Playback
* Several bugs fixed so that latency correction should be better,
and more devices work correctly. Problems with sample
rates under Linux should now be much rarer.
* Newer version of Portaudio library.
Import / Export
* Updated versions of Libogg, Libvorbis, Libflac, Libsndfile and Twolame
libraries.
* Handling of unsupported file formats more informative.
* Handling of file names with slashes in on OS X improved. New dialog
allows replacement of illegal file name characters on all platforms.
Interface
* Improved scaling and layout for rulers and VU meters.
* Envelope fixes/improvements including full control of undo/redo.
* New keyboard shortcuts and improved menu navigation.
* Preferences: More intuitive tab arrangement. New options for
mute/solo and Metadata Editor behavior. Language can now
be changed without restart.
* Expanded Build Information tab.
Effects
* New Vocal Remover plug-in, improvements for Generate effects.
Compilation:
* Fixes when building Audacity with libraries disabled.
* Improvements to make Mac and Solaris builds easier.
Security:
* Full fix for issue CVE-2007-6061 on systems where temporary directories can
be changed by other users (thanks to Michael Schwendt).
Miscellaneous:
* Updated translations for many locales.
* Several stability improvements.
There are a few more active "Known Issues" online:
http://audacityteam.org/wiki/index.php?title=Known_Issuesthan we have in the readme text. Add them or link to them?
Would it help reduce this file if older change log items were archived
online (probably Wiki) and just a link provided? I think Martyn
suggested this.
Might it be better if the credits/licence/libraries were moved to the
bottom? We could mention what we need to say in a couple of sentences
and people could go to the bottom for details if they want to. Might help
them get to the Compilation Instruction/Known Issues/Changelog easier.
Thanks
Gale
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone_______________________________________________
Audacity-devel mailing list
Audacity-devel@...
https://lists.sourceforge.net/lists/listinfo/audacity-devel