Export plugin list to csv or text file?

[MartinC]

Years ago someone posted a tool either here or on the old presonus forums that would export a list of installed plugins?
Does anyone have a method or link (I don't want to rely on screenshots)?

How do you all migrate from pc to pc? Is there something less time consuming than installing everything from scratch?
Do you keep track of your custom presets and macros (maybe save them all to a NAS or mounted cloud share?)

 

[Lukas]

Well, you're almost there already - it's my website

First link in my signature

Studio One Toolbox (Fender Studio Pro)

Studio One Toolbox - Free online tools and scripting add-ons for Studio One and Fender Studio Pro users. Our Tutorial Database includes more than 500 free Studio One video tutorials!

s1toolbox.com

Here's the video Gregor and I made:

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

How do you all migrate from pc to pc? Is there something less time consuming than installing everything from scratch?

No, that’s basically how it works. There isn’t really a faster way than reinstalling all plug-ins from scratch and backing up the presets for each one. I usually saved my plug-in presets as Studio One/Studio Pro presets, so at least I only had to migrate (copy) the Studio Pro preset folder. For this to work, you typically need to install the plug-ins in the same format (e.g., VST2 vs. VST3). Some VST3 plug-ins can load presets from their VST2 versions, but that depends on how well the plug-in developer implemented this.

Unfortunately, it’s not a completely straightforward process, and depending on the number of plug-ins you have, it will likely take a few afternoons.

 

[OutrageProductions]

Years ago someone posted a tool either here or on the old presonus forums that would export a list of installed plugins?
Does anyone have a method or link (I don't want to rely on screenshots)?

How do you all migrate from pc to pc? Is there something less time consuming than installing everything from scratch?
Do you keep track of your custom presets and macros (maybe save them all to a NAS or mounted cloud share?)

There is a 3rd party tool for Wintel machines that can find all VST's and fix issues with NI/Kontakt plugs for example: UltimatePluginTool - https://ultimateoutsider.com/downloads/

 

[Vocalpoint]

Better yet - run a Studio Pro "diagnostics" report from the Help menu:

This is what I do to get complete csv of ALL installed plugins - ideal for new builds...

BONUS: Also gives you a complete list of installed "extensions" as well.

VP

 

[Lukas]

This is what I do to get complete csv of ALL installed plugins - ideal for new builds...

That's actually what I show in the video, too. Only that s1toolbox helps with unpacking and formatting the plug-in list (group by instruments and effects, hide the plug-in version, etc.) from the exported Diagnostics Report.

 

[Vocalpoint]

That's actually what I show in the video, too. Only that s1toolbox helps with unpacking and formatting the plug-in list (group by instruments and effects, hide the plug-in version, etc.) from the exported Diagnostics Report.

View attachment 3428

The giant issue with S1toolbox is that the file created (or pasted) does not contain separators - making it a tad unruly for use in Excel etc.

If S1Toolbox offered a comma delimited option - I would be all in.

And ironically - the file contained IN the Diagnostic bundle - is already comma delimited - yet you choose to strip this completely - which does not make a lot of sense for anyone trying to manage their data in anything but Notepad.

VP

 

[Lukas]

The idea was to have something nicely formatted and easy to read to be stored in text format. If you want it structured and with all the metadata, you can just take the CSV in the diagostics report:

Bakuage,MinusDelay64,VST3,1.0.0,5 years ago
Best Service,Engine 2,VST2,1.0.0.0,5 years ago
BestService,Halls of Fame,VST2,3.1.0.0,7 years ago
Cableguys,ShaperBox-64bit,VST2,1.0.1.0,9 years ago
Celemony,Melodyne,VST3,5.3.1,7 years ago
Cherry Audio,Blue3 Organ,VST2,1.0.9.0,Last year
CWITEC,TX16Wx,VST2,3.0.7.0,8 months ago
Deskew Technologies. LLC,GP Relayer,VST3,1.0.22,Last year
Digital Suburban,Dexed,CLAP,1.0.0,Last year
Digital Suburban,Dexed,VST3,1.0.0,Last year
East West,Opus,VST3,1.0.3,4 years ago

 

[Vocalpoint]

The idea was to have something nicely formatted and easy to read to be stored in text format.

Agreed.

But CSV - IS a text format - and very useful one at that.

I guess it strikes me as odd that if that plugin file is already in CSV AND then you took all the time to write that cool routine (in S1Toolbox) to drag/drop that diagnostic archive, unpack that zip - do a bunch of "Lukas" type magic and in the end - kill off what is really valuable about that file in favor of a format with a much less useful scenario.

Why not just have your routine copy that file, strip the copy to *txt format and offer the user options for both?

VP