For VST3: of the DAWs we use regularly, REAPER and Sequoia. For other formats (VST2, AU, AAX): WaveLab, REAPER, Sequoia, Pro Tools, Logic Pro X… literally all of them.
I understand why defaulting to a global folder for presets is a fine practice. However, I don’t understand how it benefits the user to not have the option (one they already have with VST2, no less!) to save presets where they choose.
A few more data points to illustrate why this is important to us:
Between the three engineers at our studio:
- Projects can move between as many as 10 different computers. They are at some point archived to offline backups, and not-infrequently restored for further work. In order to maintain session integrity, all preset files need to reside in their project folder, not a global preset folder.
- We work on upwards of 300+ projects per year. At this rate, a global preset folder will become an absolutely unusable mess within… two weeks?
Use cases from yesterday, in particular:
- I traveled to our studio to make revisions on a mastering project in WaveLab. Saved the VST3 preset changes to the global folder. Uploaded references to the client. Left the studio. Halfway home, I realized I forgot to copy over the .vstpreset files to the project folder. Had to turn around, go back to the studio, and copy the files over.
- A client emailed to revive an older project I had started months ago at home, on REAPER on my Mac. I was able to take the raw WAV files and VST3 preset files and quickly recreate the session in WaveLab on Windows at our studio, and continue further work on the project.
In summation: yes, I realize settings are stored in the Montage and can be stored as .plugs files, but in an environment with multiple engineers, multiple computers, and a variety of DAWs, we need our sessions to be replicable, consolidated, and as platform-agnostic as possible.
Ideally, plugin manufacturers (coughSoftubecough) would make their native preset dialogs usable and I wouldn’t be bothering you with this. But until that happens, we simply need WaveLab’s VST3 preset dialog to give us the same options we have with VST2 presets.
Thank you again for your time! I’m sorry to harp on about this, but in a past life I was a UNIX system administrator and a C/Perl/Python developer, so some things are just ingrained