Audacity Forum

ensures that the configuration file has nothing in it other than the "uninitialized" line I don't think that it needs that "uninitialized" line any more (because Audacity no longer reads the 1.2.x preferences), so it could delete the file entirely. Here is an abbreviated look at a configuration fil...

To the best of my knowledge no settings are now "saved on close"; While Audacity is open, open audacity.cfg in a text editor, delete its contents, save it and close the editor. Then close Audacity. Then open audacity.cfg - lots of settings in there. Absolutely right. That is because the wxWidgets c...

+1 for "Mute" only affects (and exists on) tracks which produce audio. +1 for menu>"Mute all tracks" muting every track which produces audio, depressing their buttons, ignoring any track which is already muted and any track which does not produce audio (this would not be a "checked menu item"). +1 f...

The main problem as I see it is that just deleting the cfg file while Audacity is open is not enough - that would be simple, but does not work. :( Many settings are saved on-close and many settings are read on-launch. To get a clean reset, the cfg file can be reset (deleted) between the last "on cl...

I still don't understand the added convenience here. You can just do ctrl-a, ctrl-r if there is only one track in the project. Or click on the track label at left and then ctrl-r. <ctrl+r> is not very intuitive in this context as it implies "repeat the last effect on the current selection" and the ...

I just read this: Microsoft Takes .NET Open Source And Cross Platform http://www.tomsitpro.com/articles/microsoft-.net-open-source,1-2336.html The "open-source" is not so interesting but the ability to have the same Integrated Development Environment (IDE) work on all 3 platforms (Linux, Mac & Windo...

Not sure I understand the problem you are solving. A long time ago we had this discussion: http://forum.audacityteam.org/viewtopic.php?f=56&t=69791&hilit=noise+removal I contend that for the average user by far the most common workflow is: 1) Open the Noise R… Effect dialog 2) Inspect the values, c...

I bumped this because the issue (which started on –Manual and was then moved to -quality) and is now on –devel. Vaughan said "I've always said that. There ought to just be a 'Reset All' or 'Defaults' button in the Prefs dialog." In reply to Peter's "+1 for: http://wiki.audacityteam.org/w/index.php?t...

bump It really is easy to reset preferences programmatically from within Audacity. Not too far back one of the Developers went through and made sure that most, if not all, of the preference Writes were immediately flushed. Most, and I'm almost certain all, of the preferences Reads have built-in defa...

I'm not quite sure how this should work in a project with multiple audio tracks. The way I do it now (very ugly) takes the current selection as the Noise Profile, selects everything in the whole project (ugly but benign) then uses that profile on the Effect's list of tracks.