юра00 wrote:The problem is solved by deleting pluginsettings.cfg. Thank you! There was another one file, you didn't say: pluginregistry.cfg, which I also had to remove for normal work.
I am glad the problem is solved. I have never known it necessary to delete pluginregistry.cfg as well as pluginsettings.cfg to correct errors loading the settings.
But if you are launching Audacity from different locations, so that you have more than one copy of each effect to choose from in the Effect menu, it is possible you will see the error loading settings when you choose the other copy of the effect in the newer version of 2.1.3-alpha. Deleting pluginregistry.cfg will remove duplicate Effect menu entries.
I think matters are not helped by only storing one set of settings for a plugin, even if the effect is registered with the same name in different locations. Each copy of the plugin can store different settings in memory while Audacity is open, but when you reopen Audacity, each copy of the plugin uses the same settings, as last saved to pluginsettings.cfg. This seems to defeat the object of supporting detection of the same plugin in different locations.
юра00 wrote:in next versions do so, that I did not need to delete anything!
We cannot fix anything until we see the problem happening ourselves.
I would suggest you if want to help us with this, please obtain each updated alpha build when it is made available every day or so. Try using the same folder for each build (just overwrite the previous contents of the folder with the contents extracted from the new alpha build). Let us know how that goes.
If that is no problem then you could experiment running each new alpha build from a separate folder. If that creates a problem then it is something to do with having multiple copies of the same effect.
юра00 wrote:You understand, after such deleting plugin list and effects settins are overthrowing to defaults and I must again form reflected plugin list and overset all my effect values!
Yes that is unfortunate, but let us see if this keeps happening when you update to each new alpha build.
Note that if you copy pluginsettings.cfg to another file name then you can at least see in that copied file what the old settings were.
юра00 wrote:And return "bass and treble" effect window so, that it did not have to press "close" after applying.
As I explained, Bass and Treble will not change back to a non-real time effect. Please reply to this post
http://forum.audacityteam.org/viewtopic ... 98#p314498 and tell us if you like the idea of an "Apply and Close" button.
Gale