I think i have too much plugins

VST, AU, AAX, CLAP, etc. Plugin Virtual Effects Discussion
Post Reply New Topic
RELATED
PRODUCTS

Post

I'll trade you some of your plugins for a couple rolls of toiletpaper :P

Post

Plugins are like pokemon, collecting them can be somewhat addicting I think. Might seem like it's just
a little money here and there, but after a while that can add up to obscene amounts of coin. I make
pretty good money myself, but I never had so much extra cash lying around until I (for the most part)
quit buying plugins. This at the same time as spending $15k on hardware in 1 year.

Post

That's true. I'm totally afraid to calculate how much I spend on plug-ins and of the question if I better had bought hardware with this money :D

Post

... or a house.
This is the same method MJ used when he was working on Anthony Marinelli's Thriller.

Post

The house question is rather something for the eurorack modular synth folks, isn't it? :hihi:

Post

Aloysius wrote: Wed Apr 08, 2020 11:24 pm ... or a house.
I can't hear you over the sound of all the avocado toast plugins I'm going to buy with my Coronavirus stimulus money
The life you have, the life you need, is not the same as the one in your dreams

Post

:hihi:
This is the same method MJ used when he was working on Anthony Marinelli's Thriller.

Post

Mushy Mushy wrote: Sat Apr 04, 2020 12:11 pm Is it possible to export the contents of a folder to a TXT/XLS file? (Windows10)
It is possible, but you'll need to use the command promt as far as I know.

Open the command promt (CMD.EXE) and navigate to the folder you want exported (if there are spaces in folder names you need to quote it, for example [cd "Program Files"].

Then use the dir command to list the folder and send the output of the command to a textfile with the ">" command, for example [dir > "c:\log files\dir of Program Files.txt".
Hint: TAB is your friend when you start to type filepaths, works as autocomplete and adds needed quotes.

You should then have a textfile with the same output that the dir command presents which you then can open in excel.

Post

kevvvvv wrote: Fri Apr 03, 2020 2:25 pm I'm a Plugin Slimmer these days.

I good quality plug per job.

2 at a stretch.

eg Valhalla verbs & delays, neutron eq & compression, ozone for master outs.

Life's simpler and I can get on with writing my synth masterpieces :) :D :lol:
That's the ideal situation, but it's so hard to say goodbye to so many of the plugins (and samples and impulse responses too). I'm trying to slim down based on reasonable considerations (eg plugins that do essentially the very same, than I get rid of the one that doesn't require copy protections or authorization managers, since it's easier to re-install in case of crash etc).

Post

midi_transmission wrote: Wed Apr 08, 2020 11:22 pm That's true. I'm totally afraid to calculate how much I spend on plug-ins and of the question if I better had bought hardware with this money :D
I'm glad that I mostly use freeware and only buy 2 - 3 inexpensive (think Klanghelm, Tokyo Dawn etcetera) plugins per year. But even with the mostly freeware and magware plugins in my collection, I have way to many for an efficient workflow without 'decision fatigue'.

Post

vmood wrote: Tue Apr 14, 2020 1:58 pm
Mushy Mushy wrote: Sat Apr 04, 2020 12:11 pm Is it possible to export the contents of a folder to a TXT/XLS file? (Windows10)
It is possible, but you'll need to use the command promt as far as I know.

Open the command promt (CMD.EXE) and navigate to the folder you want exported (if there are spaces in folder names you need to quote it, for example [cd "Program Files"].

Then use the dir command to list the folder and send the output of the command to a textfile with the ">" command, for example [dir > "c:\log files\dir of Program Files.txt".

This, but you might want to use the /B option with dir; it'll strip out the extra info you don't want, and just give you the file name.

You can restrict the list to *.dll or *.vst3 to exclude other file types. You might end up with a few DLLs that aren't actually plugins in some cases.

You can also use /S to include sub-directories. You will get the full path if you do this. I can't remember if there's an easy way to strip that out with "dir", but it should be easy with something like grep, or using regex in Word/Excel/Open Office (remove everything up to and including the last '\' character). You can strip the extension the same way (everything after the final '.').

Examples:
VST2

Code: Select all

dir /B /S *.dll >> VST2.txt
VST3

Code: Select all

dir /B /S *.vst3 >> VST3.txt
dir /? will list the available options that you may want to investigate.


(Yes, I know I'm replying to an older post, but this could well be useful to others).

Post

I realized years ago that I could do a lot worse than collect plugins so considering what I could be into, I think I'll just let them be. 8)

Post

Kazi7 wrote: Fri Jun 11, 2021 12:12 pm
midi_transmission wrote: Wed Apr 08, 2020 11:22 pm That's true. I'm totally afraid to calculate how much I spend on plug-ins and of the question if I better had bought hardware with this money :D
I'm glad that I mostly use freeware and only buy 2 - 3 inexpensive (think Klanghelm, Tokyo Dawn etcetera) plugins per year. But even with the mostly freeware and magware plugins in my collection, I have way to many for an efficient workflow without 'decision fatigue'.
Well you have two choices.

1. Decide upfront on a project which plug ins you will limit yourself to, and stick to it.
2. Buy Bitwig where you can create folders of plug ins that you want to use and easily just pick the plug ins you want from more concise folders

Post

I take over all plugins you do not use actually (and herewith release you from your psychic pain and despair) and send you a dozen rolls of toilet paper:
Deal?

Post

Too much, too young...

Post Reply

Return to “Effects”