Way too many plugins and choices - Need advice to fight GAS/Huge plugin folder

[anoise]

Thanks to GAS the plugin economy is kept alive and discounts are almost constant. Keep it up people! Cheaper prices for the rest of us who buy sensibly.

[dblock]

Just listen to your mix after you try cramming every recent plugin on the buses and channels just so you can feel like you didn't waste your money. lol!

[Zeisner]

Using a spreadsheet helped me a lot to reduce the amount of plugins, especially combined with benchmarks (CPU/RAM/disk usage, aliasing, architecture etc). If two plugins are basically the same but one needs more resources or has higher aliasing it's easy to decide which one has to go. I also dropped all plugins with bad GUIs (Menus with submenus, impractical controller layout etc) and everything overcomplicated like modular synths/effects which takes too much time to program (and only features mediocre built-in effects in many cases). All "vintage" and "signature" plugins had to go as well (because what's the point of a Pultec clone if you can replicate the Pultec trick with an ordinary parametric EQ anyway). A project I'm also working on is making SoundFonts out of romplers which has a lot of advantages aside from shortening the plugin list.

Planning is important. Sit down without your DAW and think about your optimal workflow environment. Then drop everything that doesn't fit.

[TechHaus]

Using a spreadsheet helped me a lot to reduce the amount of plugins, especially combined with benchmarks (CPU/RAM/disk usage, aliasing, architecture etc). If two plugins are basically the same but one needs more resources or has higher aliasing it's easy to decide which one has to go. I also dropped all plugins with bad GUIs (Menus with submenus, impractical controller layout etc) and everything overcomplicated like modular synths/effects which takes too much time to program (and only features mediocre built-in effects in many cases). All "vintage" and "signature" plugins had to go as well (because what's the point of a Pultec clone if you can replicate the Pultec trick with an ordinary parametric EQ anyway). A project I'm also working on is making SoundFonts out of romplers which has a lot of advantages aside from shortening the plugin list.

Planning is important. Sit down without your DAW and think about your optimal workflow environment. Then drop everything that doesn't fit.

I have a Notion database with all of my plugins (and some that I don't have, that I am researching).

I drop my license info in there, my own notes, any links and quotes from threads worth remembering, any Youtube videos that are relevant or helpful, download links, installation notes, etc.

Beyond plugin category / types, I also have checkboxes for plugins that I keep on my desktop or laptop, and also a checkbox called "A-list" which are my most important plugins to reinstall if I want to get a system up and running quickly.

When I started making this database few years ago, I didn't know if it would be worth it, but I am almost always thankful I do a project like this afterwards.

You can embed the databases anywhere in Notion and pick how you want to view it and filter what you want to view, so I have separate category pages set up for like Reverb, Delay, Synths, Samplers, Compressors, etc. etc. etc.

When GAS hits, there are lots of ways to talk myself out of something new with this setup. And it is also helpful to identify the gaps in my setup, like right now I need some toneboosters mix plugins. But not from GAS, just from knowing my actual needs.

[Zeisner]

When I started making this database few years ago, I didn't know if it would be worth it, but I am almost always thankful I do a project like this afterwards.

Me too. It makes everything a lot easier, not just reducing the anount of plugins. I have a column just for latency, enabling me to take care that two plugins align perfectly in time without relying on delay compensation (which is pointless anyway because not all plugins report it properly). It's impossible to tell how many times this spreadsheet has saved me from running into issues. It's absolutely worth the time and effort to set up such a database.

[dexrow]

I use subfolders but with stuff like voltage modular, vcv rack and reaktor my instrument library started getting big enough where I am ignoring alot of releases.. If I had my way I would have all the modular stuff show up in the index as well under different colors so I could tell them apart. I also exclude plugins that cause trouble on my lower end stuff..

[jobinho]

The size of your plugin folder is what matters, not what you do with it

[djanthonyw]

because what's the point of a Pultec clone if you can replicate the Pultec trick with an ordinary parametric EQ anyway

I’d say character is the point.

[Zeisner]

I’d say character is the point.

The character can easily be imitated. There is nothing special about the Pultec if you view it as a combination of filters, waveshaping and added noise.

[Zeisner]

I use subfolders but with stuff like voltage modular, vcv rack and reaktor my instrument library started getting big enough where I am ignoring alot of releases..

Do you keep track of how often you actually use a module?

[jamcat]

Develop a working philosophy to how you approach audio engineering.

As the saying goes, “If you don't stand for something, you will fall for anything,” (‘anything’ being the latest flashy plugin.)

[BLUEsunny]

The size of your plugin folder is what matters, not what you do with it

thats why you just collecting and not making any as... tunes

[BBFG#]

Another saying for this;

"Better to own a synth and not need it than need a synth and not own it."
Edit/add: Because that's a joke.

Just stay away from the companies in employing abuse cycles as their marketing plan.

[Zeisner]

Size does matter. It makes quite a difference if you have to backup 1 GB or 1 TB of plugins...

[JerGoertz]

You’re going to have to spend some dedicated time on shooting out plugins in each sub category and only keep 1 to 4.

You should be shooting out in this order for:

1. Sound (tone /quality)
2. Features
3. How well you click with the interface

Get rid of the rest.

To OP: I don't have the self-discipline or care enough to do it, but if you're really serious about paring down your plugin list, this is almost certainly THE WAY.