Audacity Forum

Tapehead wrote:the M F shortcut is very handy, is there also a shortcut for User Presets?

After pressing M, access any available item in the Manage menu by typing the first letter of its menu item.

So, type M U for user presets or M I for Import Presets, and so on.

Tapehead wrote:Talking of which - I just noticed with concern that my numerous User Presets in Toneboosters EQ saved whilst using Audacity 2.1.0 (installer) are listed but no longer work in 2.1.1. They don't load graphically or change the audio. Presets made since installing 2.1.1 do work.

I'm on Windows 7 with 2.1.1. installer.

Thanks for the report. I did not know this was a problem myself.

The parameters for saved presets are stored in the "pluginsettings.cfg" file in Audacity's folder for application data. Where the plugin saves presets in a "chunk", each preset has a reference to that chunk saved in pluginsettings.cfg, as before. So presets saved in Audacity 2.1.0 by such a plugin will still work in 2.1.1 and later, and settings saved in 2.1.1 and later will still work in 2.1.0.

Where the plugin does not use a chunk for presets we store the parameters as plain text in pluginsettings.cfg. The syntax used to store parameters in plain text changed in 2.1.1. So presets saved in 2.1.0 by plugins that don't store presets in a chunk will not work in 2.1.1 and later (and vice-versa).

As an example, this is what the stored 2.1.0 preset looks like in pluginsettings.cfg if in Kjaerhus "Classic Chorus" we set all controls to maximum, except for the fourth control "Depth" which we set to 52%: Here is how 2.1.1 stores the same parameters, giving each parameter a name and storing the value with greater accuracy: So I'm afraid without saving a preset in 2.1.1 or later to find the control names, then inserting these names into the values of the 2.1.0 preset (taking into account the changed order) you can't easily use presets saved in 2.1.0 in current Audacity.

FWIW, you can use the old six digit values when changing the syntax to that for 2.1.1 and later. And you can read what the old settings were (as 0 to 1 values), adjust the plugin controls to match and save as a new preset.

I'll raise this problem after 2.1.2 has been released but I can't guarantee we will want to go back to the old syntax.


Gale

Thanks for further shortcut info.

Here's what I see in the plugins cfg for one Tb-EQ User Saved Preset
I think in the circumstances the easiest option for me could be to use a 2.1.0 or earlier portable version to apply a preset I want in the short term and take screenshots of each preset and then visually match in 2.1.1 + for the long term.

Tapehead wrote:Here's what I see in the plugins cfg for one Tb-EQ User Saved Preset

Yes, that is the old plain text syntax.

Tapehead wrote:I think in the circumstances the easiest option for me could be to use a 2.1.0 or earlier portable version to apply a preset I want in the short term and take screenshots of each preset and then visually match in 2.1.1 + for the long term.

Yes that might be easiest if you don't mind having 2.1.0 and the current version.

If you run 2.1.0 and 2.1.1 from different folders, this will give you two entries in the Effect menu for any plugins that are in both Audacity "Plug-Ins" folders. If that is very annoying it should be OK to put a renamed Audacity 2.1.0 executable in the 2.1.1 installation folder then run one executable or the other from there.

When you install 2.1.2 (when it's released), it uses different wx*30*.DLL's. The old wx*28*.DLL's don't get cleaned out by the 2.1.2 installer, but the 2.1.3 installer will do that clean up. So at that point (if you were to run 2.1.0 from the 2.1.3 installation folder) you would need to bring in the old wx*28*.DLL's that 2.1.0 needs.


Gale

Thanks for the tips and upcoming 2.1.3 warning Gale.

Not wanting any double entries I opted for the renamed exe in the 2.1.1 folder. That worked fine.

I'll copy in the old wx dll's in a 2.1.3 future.

(edited because I wrote double twice )