Hello!

So, I’m kind of stuck here with a specific workflow problem, and I’m trying to build something to fix it.

Basically, the goal is to create a simple app called Preset Browser. It lets you browse and load any preset from any heavy plugin (like Kontakt, Omnisphere, Nexus, UVI, Arturia, etc.) directly into an active StudioVerse Instruments slot inside Pro Tools. The best part is that it all happens completely behind the scenes, so you never have to leave the native Pro Tools preset list.

Since I’ve already gotten this to work perfectly with Arturia inside Analog Lab—and it even works with completely standalone plugins outside of Analog Lab (like a dedicated piano plugin or whatever)—the logic is solid. If it works smoothly for those, there’s no reason it won't work for everything else.

Instead of trying to map tens of thousands of individual presets directly into Pro Tools (which would be a total nightmare), the system uses a clever workaround with fixed slots. The StudioVerse preset bar in Pro Tools will only ever show a fixed list of about 30 entries. These aren't specific presets; they are instrument families (like Acoustic Piano, Acoustic Guitar, Synth Lead, Bell, Rhodes, etc.).

Each of these 30 family slots connects to a .tfx file sitting inside the WaveShell AAX folder, and we can swap the contents of these files whenever we want. The actual massive library (we're talking 50,000+ presets pre-converted to .tfx, organized, and tagged by instrument type) lives safely outside of Pro Tools, managed by this Preset Browser app.

When you double-click a preset inside the Preset Browser app, SoundFlow instantly does a silent file swap in the background. It replaces the old .tfx file for that instrument type in the WaveShell folder with your newly selected preset file. So, clicking the "Acoustic Guitar" slot inside Pro Tools will instantly load whatever patch was last swapped into it—a Kontakt guitar one second, or an Omnisphere guitar on the fly—completely seamlessly right inside the Pro Tools dropdown menu.

To be totally transparent about how I build things: I don't actually know how to code traditionally. I'm just a vibe coder. I basically do a ton of back-and-forth between Claude.ai and Claude Code to figure out the structure, write the scripts, and fix errors until the workflow just works. For example, for the file-swapping script that I attached, it took at least 30 versions of pure trial and error with Claude before we finally hit on the script that actually works perfectly.

The reason I'm bothering to build this is to solve a massive headache in the studio. If I'm working on a track and have an acoustic guitar patch I love inside Kontakt, but want to quickly compare it to an Omnisphere guitar patch to see which fits better, switching between them usually breaks the whole creative flow. You have to open heavy plugin windows, wait for UIs to load, and click around. This app removes all that friction so you can flip between entirely different underlying instruments instantly without losing the vibe of the session.

I've attached the final script (the one that took about 30 failed attempts before working!). It’s the core of the whole swapping logic. Take a look :
https://www.swisstransfer.com/d/6a84cdc5-d922-48f5-9551-076fda796546

 

have a plug-in which can host plug-ins. give it 2000 parameters to match all possible cases. on load, it will preload all the plug-ins which come into question. turn processing off for all of them.

no idea about AAX, but in VST preset files there is usually a signature by plug-in who wrote it. so when loading a preset, first spool to the signature, then load the preset into the slot which has the right plug-in, then turn it on.

 

Don't just upload a random file to some sketchy file host, please use GitHub instead. (Ideally with things split into many files. Use Claude Fable 5 and tell it to organize and structure things like a professional programming project would.)