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

[antic604]

Most of us here have a constantly growing - sometimes enormous - collection of plugins that were purchased from different places: developer website, retailers like JRR, Audiodeluxe or Plugin Boutique, transferred from other users, etc.

How do you make sure that if things go south you know:
- which plugins you had (it's easy to forget some )
- you know where to d/l the installers (website, login, password)
- you have a copy of serial number or license file if applicable

I started building a spreadsheet with this information, but perhaps there's smarter way to do this?

Or do you don't care about it at all and hope backup, Google password (or whatever you use) and your memory will suffice?

[Psuper]

Keepass -- currently sitting at over 2000 entries having been in use since 2006.

Prior 2006, a windows stickypad.

Prior that, Palm Desktop.

Prior that, pen and paper.

[antic604]

Keepass -- currently sitting at over 2000 entries having been in use since 2006.

Thanks, I'll look into that, although the late 90's-styled website doesn't fill me with confidence

[dune_rave]

yeah, that kpass is good.

[Psuper]

Keepass -- currently sitting at over 2000 entries having been in use since 2006.

Thanks, I'll look into that, although the late 90's-styled website doesn't fill me with confidence

Open source will do that!

Best app I ever used for keeping pretty much any type of txt or information. I use the older portable that doesn't require any libraries, best one to use, I have it on 5 PCs, and copy and import the master every month or so.

[blizzard]

A simple table in OneNote works for me. However more importantly maybe you don't need that many plugins? That was one of the reasons I started to downsize my plugin library and consolidate the number of developers I support. You certainly don't need 30x different EQs or 15x simulations of 1176compressor. I'm going after creativity first without having to debate which emulation will sound the best on my snare drum.

[chk071]

Keepass -- currently sitting at over 2000 entries having been in use since 2006.

I use this for a while now. And, to synchronize my passwords on my 2 computers, I put the keyfile in the secured vault of OneDrive. Works great for me.

[fuzzlightyear]

Most of us here have a constantly growing - sometimes enormous - collection of plugins that were purchased from different places...

Step 1. First get a hold of your GAS problem.
Step 2. Then the other problems go away.

Solved.

[DJ Warmonger]

Less plugins => less problems. Go ask yourself - what do you need all these plugins for? Are you really gonna use them for any project at all?

[antic604]

However more importantly maybe you don't need that many plugins?

Step 1. First get a hold of your GAS problem.
Step 2. Then the other problems go away.

Solved.

Less plugins => less problems. Go ask yourself - what do you need all these plugins for? Are you really gonna use them for any project at all?

That's actually the point. I'm planning to uninstall - and perhaps eventually sell, if possible - those that I don't use, but I want to still keep stock of what I have and how to access it.

[blizzard]

That's actually the point. I'm planning to uninstall - and perhaps eventually sell, if possible - those that I don't use, but I want to still keep stock of what I have and how to access it.

I would first list all your plugins and perhaps slightly categorize them (type, sell/keep). I find spreadsheets work best for such task - you can sort them, filter, add columns etc.

[antic604]

That's actually the point. I'm planning to uninstall - and perhaps eventually sell, if possible - those that I don't use, but I want to still keep stock of what I have and how to access it.

I would first list all your plugins and perhaps slightly categorize them (type, sell/keep). I find spreadsheets work best for such task - you can sort them, filter, add columns etc.

Yeah, I know. I've been working spreadsheets for the last 20 years

[midi_transmission]

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.

[yellowmix]

I built a Google spreadsheet to track purchases a long time ago but it's become my inventory too. So I went back and added licensed freebies the past couple months. I considered a database but I didn't need such rigid structure and the data entry and pulling reports would be unnecessarily complex and a chore. Spreadsheet is plenty fast and the reports are auto-generated from live data. So you're on the right track. Mine evolved over time and yours probably will too so don't worry about getting everything "right" right away. It's easy enough to add columns.

My archival drive houses some software installers in a hierarchal folder structure by developer. If there are license files they go there too, if it's a serial I make a text file with relevant info. The archival drive also holds libraries where downloads expire (e.g., IK Multimedia). I actively avoid those products so they are mostly freebies.

For site logins, Firefox's password manager. They have an app for mobile called Lockwise which completes my needs. I enable 2-factor wherever I can (Authy). As for where to download, I have the developer name so I don't bother bookmarking an URL. The domain can change, the user area URL can change, etc.. Also, KVR's My KVR Updates often provides a download link for non-gated software, or at least the site. Easy-Peasy.

[gaf_thit]

I've lost count and forgot many. No system at all, except emails deep down in the history and account order overview... Need to cull the herd, but it is something I keep postponing.
Keep spending most of my life
living in a procrastinators paradise