I think the ability to disable/enable VSTs would also be a great feature.

One case I could definitely use would be to batch enable or disable VST2 plugins.
I always use VST3s but sometimes I receive projects to collab, mix or master which use VST2s so I would only enable them then.

 

As long as the data can be imported and exported as a table, and not in some proprietary file format that works with nothing else; you could do whatever you want with the data and bring the results back into it. Instead of trying to get all the details from the actual plugin files, it could auto-fill any details you want from an online master file. Like how an application can fetch one of the firewall ruleset blacklist subscriptions via github, or the dynamic updated nativeaccess.xml. Or auto-populate the table using AI to do all the lookups in various columns.

 

As I'd like to have such a software, I'm quite surpirsed to see that many people having found other way to sort their vsts etc.

It's been a nightmare since the beginning for me.

 

Last edited: Sep 24, 2025 at 12:46 AM

I was developing the exact same idea also with AI help: I really need it! Please DM in private to talk about it. Thank you

EDIT: There are DM here? let me know how I can contact you.

 

NEWS: Sonisto vst manager --> https://audiosex.pro/threads/sonisto-vst-manager.81836

Imagine a large library with all the books lying around in disarray—how would you possibly find anything there?
That's why libraries are organized by subject and A-Z.

It's the same with plugins, presets, and sound libraries. If you can't organize them yourself, you'll sink into chaos...!
You could perhaps start by creating 4 folders:
- My VSTi (Instruments)
- My VST (Effects)
- My Presets (FXB & FXP)
- My WAV, Kontakt

Move your files into them.

You can also take pictures of your plugins, see attachment for an example, always label everything.

 

Last edited: Sep 24, 2025 at 9:40 AM

The only thing you can do to make it really useful to someone is to create a plugin manager that can package installed VSTs into packages that can be installed on another system with a single click. The closest analogue is UniGet software, but in your case, the manager must be completely pirate friendly.



PS

I didn't read about “reasonably priced”

In general, this is not the best idea for monetizing your vibe coding hobby

 

The reason why I was developing is that audio professionals accumulate dozens or hundreds of plugins. Digital Audio Workstations (DAWs) offer rudimentary cataloging systems, often limited to the name and manufacturer. Finding the right plugin for a specific task (e.g., "a transparent VCA compressor for the drum bus") takes up memory, time, and interrupts the creative flow. There's no centralized tool that acts as a plugin sommelier.

 

Maybe they should specifically ask the AI - Enter question ~ 7 seconds later:

Spoiler: Source: Grok KI

I hear you—searching for the perfect plugin like a transparent VCA compressor for the drum bus can be a real workflow killer. To streamline things, consider these approaches:

1. Narrow Your Search: Use plugin databases like Plugin Boutique or Audio Plugin Deals, and filter by type (VCA compressor), style (transparent), and application (drum bus). For example, a transparent VCA compressor often means something clean like FabFilter Pro-C 2, Distressor emulations, or SSL-style bus compressors.
2. Favorites List: Most DAWs let you tag or favorite plugins. After testing, save go-to options (e.g., Slate Digital’s VBC or Waves API-2500) for quick access.
3. Plugin Managers: Tools like Plugin Alliance’s Installation Manager or iLok can organize your plugins, making it easier to find what you need without digging.
4. Preset Templates: Create a drum bus template in your DAW with a shortlist of trusted compressors pre-loaded. This saves time and keeps you in the creative zone.
5. Community Recommendations: Check real-time posts on X or forums like Gearspace for user suggestions on transparent VCA compressors. Search terms like “transparent VCA compressor drum bus” on X can pull up recent discussions.

For a specific recommendation, FabFilter Pro-C 2 is a versatile, transparent compressor with VCA-like behavior, perfect for gluing a drum bus without coloring the sound too much. If you want me to search X for recent chatter on this or analyze a specific plugin’s suitability, let me know!

Spoiler: Source: ChatGPT KI

You're absolutely right — hunting for the perfect plugin in the middle of a creative session can derail your momentum. Whether it's a transparent VCA compressor for your drum bus or a colorful saturator for vocals, that kind of technical decision-making pulls you out of the music and into the menu-diving.

Here are a few strategies to reduce that friction:

️ 1. Curate a Go-To Plugin Chain
Set up a few “default” signal chains per task. For example:

• Drum Bus – Transparent Compression:
  • Plugin: SSL Native Bus Compressor, Klanghelm DC8C, or FabFilter Pro-C 2 (in clean style mode)
• Drum Bus – Colorful Compression:
  • Plugin: UAD API 2500, Waves API 2500, Arturia Comp VCA-65

Save these chains as presets in your DAW for one-click recall.

2. Create a Cheat Sheet
Build a one-page PDF or notes doc titled:
"Go-To Plugins by Task"

Sample entries:

• Transparent VCA for drums → DC8C (mode: Clean, RMS detection, slow attack)
  
  
• Glue compression for mix bus → SSL Bus Comp
  
  
• Aggressive vocal compression → 1176 Rev A clone (All-buttons-in)

Print it or keep it open on a second monitor/iPad during sessions.

3. Pick One Plugin Per Category and Learn It Deeply
Instead of collecting 10 compressors, pick 1-2 per type:

• VCA → Klanghelm DC8C or Cytomic The Glue
  
  
• FET → Softube FET Compressor or UAD 1176
  
  
• Opto → TDR Molot GE or LA-2A (any flavor)

Knowing how to dial them in quickly is more valuable than having the "best" one.

4. Use Plugin Aliases or Renaming
Many DAWs (like REAPER, Logic, and Studio One) let you rename plugins or organize them into folders. You could name:

• "DC8C" → " VCA Clean Drum Bus"
  
  
• "Pro-C 2" → " VCA Clean (Sidechain Ready)"

So you don’t need to remember what does what — just search by task.

5. Set Up Templates with Plug-n-Play Inserts
Create a Drum Bus Template with your top 2–3 compressors already inserted but bypassed. That way, you just toggle on what sounds best without breaking flow.

Would you like help building a quick-reference chart like that, tailored to your plugins and mixing tasks?

 

i´ve made one in 2002, which offers a library for presets and help with building banks and such.

it also had a routine to get the VST ID from a plug and write it into a textfile (required for certain programming tasks) and one to identify which plug-in wrote a given preset file.

but in these days the basic management of plug-in documents was easier than today:
you could freely move plug-in folders around (and in my favorite host app also allowed to choose custom folders, use multiple folders, or use drag and drop), you could easily rename and sort the plug-ins right in the OS browser, copy protection was less cumbersome, too. and of course we were given the gift of resource editing, which allowed simple hacks such as renaming the actual plug-in ID or making an effect out of an instrument (for instrument slots were limited in some apps - if you make an effect out of ppg, you can run 100 copies of it in cubase like you would do in logic)