How you deal with plugins - installers, license keys, website logins/passwords, etc.

[antic604]

A folder structure with developer name, installer and key file or serial number in it. There are some exceptions like Native Instruments, but I try to buy only plugin that are that simple to install and to activate with a key file or serial number.

That's not an answer to the quation I asked, but thanks

[Vladislav_Gronk]

Password managers are a game changer. It's so refreshing not having to worry about and remember passwords that just clogs up your mind.

1Password is amazing if you can pay the small yearly fee. Bitwarden is a great free alternative and it's the one I currently use.

[chk071]

Password managers are a game changer. It's so refreshing not having to worry about and remember passwords that just clogs up your mind.

Or... writing into 12 page text files, which I had done before. Can't believe I haven't tried KeePass earlier. Makes life so much easier and more comfortable.

[Vladislav_Gronk]

Password managers are a game changer. It's so refreshing not having to worry about and remember passwords that just clogs up your mind.

Or... writing into 12 page text files, which I had done before. Can't believe I haven't tried KeePass earlier. Makes life so much easier and more comfortable.

Yeah, remembering one master password is definitely easier.

I also like the secure notes feature for storing all kinds of important codes and notes, e.g. serial numbers.

[Scotty]

Probably the most unpopular opinion here but I like Ilok , elicenser and cloud based authorizations sytems such as plugin alliance and waves. It is easy to authorize a computer... remove a computer .. move licenses between machines etc. I have plenty of serial based software but I prefer the former.

[jamcat]

Why do you need so many plugins?

With a few notable exceptions, I use large collections from just a few vendors: Arturia, IK, Eventide, Slate. And I don't even use Slate anymore after getting a MacBook Pro with USB-C because of the iLok dongle dependency.

I can barely remember my "Big Four Three" even when things are running smoothly. No way I'd be able to keep track of a million one-off plugins. Besides I'd rather use just a few plugins on lots of projects each, rather than lots of plugins on just a few projects each. Jack-of-all-trades and master of none, and all that.

[antic604]

Why do you need so many plugins?

You're done feeling superior yet?

I never said how many plugins I have and for many here it would be a very modest collection. Also, I'm not interested in "large collections" by Slate, IK, Waves or Eventide. I prefer to support smaller, more specialised developers, that often can't afford (or it doesn't make economic sense for just a few plugins) to implement an installer / manager like that.

So please get off your high horse and move on if you can't contribute constructively

[Tj Shredder]

I have a NAS as archive, in there I store the latest installers with key files, serials etc. I also have a local folder for all related e-mails in my e-mail program... Most passwords are stored in the browsers password manager and synced to all machines or in the mac keychain...
Bitwigs browser is all I need to organize my collection...

Btw. I need all the plugins I don’t use, to feel better. It works, its a miracle and feeds some developers which isn’t bad either...
Don’t tell the alcoholic to stop drinkin’, it doesn’t work...

[Rivanni]

A folder structure with developer name, installer and key file or serial number in it. There are some exceptions like Native Instruments, but I try to buy only plugin that are that simple to install and to activate with a key file or serial number.

That's not an answer to the quation I asked, but thanks

Yes, it is what you asked. How to deal with installers etc.

I also save each plugin in a separate folders. The name consists of the developer name, the plugin name and the version number.
In each folder the installer, a link to the website where I can download updates and the serial/license numbers (encrypted) and other info if needed.
For passwords for websites I use Keepass.
Keeping track of all this in an spreadsheet is aredundant.

[antic604]

A folder structure with developer name, installer and key file or serial number in it. There are some exceptions like Native Instruments, but I try to buy only plugin that are that simple to install and to activate with a key file or serial number.

That's not an answer to the quation I asked, but thanks

Yes, it is what you asked. How to deal with installers etc.

I also save each plugin in a separate folders. The name consists of the developer name, the plugin name and the version number.
In each folder the installer, a link to the website where I can download updates and the serial/license numbers (encrypted) and other info if needed.
For passwords for websites I use Keepass.
Keeping track of all this in an spreadsheet is aredundant.

Oh, then I misunderstood - my bad, sorry @midi_transmission

[jamcat]

Why do you need so many plugins?

You're done feeling superior yet?

I never said how many plugins I have and for many here it would be a very modest collection. Also, I'm not interested in "large collections" by Slate, IK, Waves or Eventide. I prefer to support smaller, more specialised developers, that often can't afford (or it doesn't make economic sense for just a few plugins) to implement an installer / manager like that.

So please get off your high horse and move on if you can't contribute constructively

I was answering the question you asked, which was how you deal with keeping track of plugins. This was my answer: I keep them to a minimum and for the most part use only a few large collections with installers that take care of it for me. That's a totally legitimate answer, and it is in fact how I do it. You're the one who acted superior, saying you're "not interested in" my preferences, and that you "prefer to support smaller, more specialised developers" like that makes you a better, more globally conscious citizen who has more refined, boutique sensibilities than my McDonald's eating, Arturia using self.

I tend to avoid relying on small developers for my core plugins because as with all small businesses, 80% of them don't survive more than a year, and I got tired of having to find replacements that were still being developed and supported. Besides, it is a good idea to cull the plugins you don't actually use as part of your regular maintenance. It's better for your workflow and your state of mind. Just use a few plugins, and learn how to use them well.

Anyways, as part of my response I asked a general, rhetorical question which you took literally and personally and got way too butthurt. This seems to be a pattern with you. Maybe you just need a hug. It's all OK.

[Weasel-Boy]

Just on the subject of installers:

I have a habit of inspecting all installers before engaging them. I'm on a Mac and use a program called Pacifist to inspect the contents and pathways of installers... specifically to make a note of where everything but the actual plug-ins are to be distributed around my system. Sometimes, all I need is a specific form of the plug-in (VST2, VST3 or AU) and Pacifist lets me yank that out without disturbing (or launching) the installer itself.

[gentleclockdivider]

Making a folder with all my passwords /reg keys and installers , put it on a memorystick + another backup .
I tend to avoid anything ilok , pace

[antic604]

Anyways, as part of my response I asked a general, rhetorical question which you took literally and personally and got way too butthurt. This seems to be a pattern with you. Maybe you just need a hug. It's all OK.

You're probably right, sorry!

And I wasn't suggesting that me using smaller dev plugins makes me somehow better. I was just saying that those big bundles offer almost nothing that interests me, as they usually contain several types of traditional devices like EQs, compressors, limiters, amps/distortions, etc. and I don't really hear difference between them. I prefer getting more weird FX like stuff from Madrona, Sonic Charge, Sugar Bytes, Valhalla DSP, etc. because they better fit my music and how I make it

[kenny saunders]

When I buy a plugin I save a link to the website for that product. Installers are out of date by the time you need to re install anyway.

Also I just use Google Chrome as a password manager and it also suggests strong password for new logins.