VST Plugin Collection Database

Discussion in 'Software' started by Dalmation, Apr 29, 2025 at 3:51 AM.

  1. Dalmation

    Dalmation Producer

    Joined:
    Jun 7, 2011
    Messages:
    547
    Likes Received:
    88
    I have a growing hoard of VST plugin goodies and want to catalog them in a database.

    Wondering whether to use either a table in word.doc, an excel table or a simple access style database?

    The structure of columns would be eg.
    Developer | Product | Type | Version | WWW Dev. | WWW Source ... etc.
    The 'Type' would be limited to similar used in KVRaudio; Synth VA, Synth Additive, FX Chorus, FX Distortion,,,

    Searchable and sortable.

    Ideally to include a graphic of the GUI of each product in the dB.

    KVRaudio used to have a great big dB, sortable by Developer or Product Name but I cannot find it anymore :(

    Are there any database boffins here who can help me to whip up such a dB, in something like SQL, MS Access, OpenOffice Base ?

    Thanx ^_^
     
  2.  
  3. ziked

    ziked Producer

    Joined:
    Nov 30, 2019
    Messages:
    117
    Likes Received:
    112
    I just use spreadsheet for my personal plugs. One tab for Instruments, one tab for Effects.

    1st column: Plugin author + Plugin name (e.g. "Full Bucket Nabla")
    2nd column: Category (e.g. Synth/SynthMono/FM/ROMpler/Keys/Drum/SynthEdit/SynthMaker)
    3rd column: Type (kinda like Category but more specific)
    4th column: Free or Paid (to keep track since sometimes I forget :bleh:)
    5th column: Notes (any important info to note, like version, whether portable or installer, instructions, or bugs/issues, 32-bit only etc)

    For MySQL, I'm not that far gone yet:rofl:
     
  4. Balisani

    Balisani Kapellmeister

    Joined:
    Oct 16, 2014
    Messages:
    94
    Likes Received:
    68
    You don't need a relational, query-able database to catalog a few dozen, or even hundreds of VSTs.
    A google spreadsheet or an XLSX will do just fine.
     
Loading...
Loading...