CRASH - Too many plugins?

[plyall]

Folks -

When I use the latest BETA, I always get a crash (can post if useful). I can only assume that this is due to the number of plugins I have (hundreds). The 'stable' version seems to work, but the complaint I always get is that files were created with a later version (laptop with less plugins). How can I get a version that both deals with my plug-ins and processes my files?

Thanks!

Pete

[kozikowski]

In random order...

Files are perfectly compatible between all versions of Audacity. It's Projects that don't work backwards. Export a nice WAV file from any version and it will open on any other version.

Never do production in MP3. Ever.

It's not Plugins that cause Audacity instability, it's the one or two plugins -- or group -- that are very badly written. Find the group. Take out half and see how Audacity acts. Take out the other half. Start with none and add them back group at a time.

And finally, you don't want to be the editor who smashed in all the plugins he could reach just because it's cool. I finally got rid of all my production fonts because I only ever used six. Maybe seven. I bet you can't even name half of your plugins much less use them.

Koz

[steve]

A quick and easy way to determine if it's your plug-ins that are causing the problem.
Edit menu > Preferences > Effects
Disable all plug-ins
Restart Audacity.

Does Audacity still crash?
If not, go back into Preferences and re-enable ONE TYPE of plug-in (for example "Nyquist") and restart Audacity.

Work through the plug-in types one at a time to find which type of plug-in is causing the problem.

[plyall]

Folks -

Much appreciated on the feedback. I will go through the disabling exercise in a bit. Question: how do I disable the plugins if I can't get Audacity to start?

I don't recall mentioning MP3, but I do use it occasionally when I want to take a composition of mine to the car for listening.

Pete

[steve]

Question: how do I disable the plugins if I can't get Audacity to start?

You didn't mention that it wouldn't start.
In that case you need to find the file "audacity.cfg" (it's in a hidden folder, so enable search for hidden files and folders)
Normally it will be in ~/Library/Application Support/audacity

I don't use Macs so I'm not sure exactly what effects they have, but you will find some entries similar to this:

Code: Select all

[Ladspa]
Enable=1
[Nyquist]
Enable=1
[VAMP]
Enable=1
[VST]
Enable=1

In the square brackets is the type of effect, and the following line enables/disables that type of effect. (1= Enabled, 0=Disabled)
If you have trouble working out what to do, give a shout and we can get one of the Mac people to advise.

[billw58]

In that case you need to find the file "audacity.cfg" (it's in a hidden folder, so enable search for hidden files and folders)
Normally it will be in ~/Library/Application Support/audacity

Actually, that folder is not hidden. And "~" means "your home".

Once you open the audacity.cfg file in TextEdit, you'll find (in a default installation)

Code: Select all

[AudioUnits]
Enable=1
GUI=1
[Ladspa]
Enable=1
[Nyquist]
Enable=1
[VAMP]
Enable=1
[VST]
Enable=1
GUI=1
Rescan=0

You should probably start by setting "Enable=0" and "GUI=0" for AudioUnits and VST effects. Also make sure the "Rescan=0" under VST.

-- Bill

[steve]

Thanks Bill.

[kozikowski]

And then, assuming Audacity starts working, you still get to figure out which plugins are causing problems. It's possible you can get a condition where two plugins interfere with each other -- the problems only happen when both are installed at once.

You may decide you don't need thousands of plugins.

Koz