Proposal: Consolidate all prefs and presets into one folder

Cubase
1

Every now and then, there will be a posting here about trying to migrate Cubase’s various presets and preferences to a new machine (or even backing them up), and how difficult it is, as the files are scattered all over our systems.

I realize that with programs like Cubase, which have numerous modules, this might take a while, but it would be great if we could have all the preferences and presets in an easily accessible folder.

Perhaps something like this.

As both Windows and OSX have “Documents” folders, all prefs and presets could be placed in a directory like

/users/UserName/Cubase/Prefs and Presets/

If you wanted, you could put files into folders within that folder.

/users/UserName/Cubase/Prefs and Presets/Halion/

/users/UserName/Cubase/Prefs and Presets/Groove Agent/

For OSX, if some files need to be within the ~Library or /UserName/Library/ folders, perhaps use something like hard links to point them to the Prefs and Presets folders. I would imagine Windows has similar capabilities.

If there is already a folder called “Cubase” in the user’s Documents folder, you could just create the Prefs and Presets folder in that.

I think it would be easy for a new user to understand what that folder contains and could make dealing with issues like when VSTs get confused a lose their presets.

I know there is a worry about users screwing things up, but let’s face it. Users and going to mess things up regardless of where you hide files.

4 Likes
2

I am with you, it could be way less cluttered. One example are Halion, Backbone, Groove Agent, and Padshop and the management of associated samples. It’s kind of a science in their own right.

If there was a comprehensive documentation on file management I wouldn’t complain. But since there is no such thing (apart from a decade old vague overview) you have to put the pieces of the puzzle together all by yourself and that’s time-consuming and annoying.

In all fairness, Cubase and its VSTis are only one part of the bigger picture. I assume that most users also work with 3rd party plugins which all come with their own preset formats and rating systems. That’s where it can get really messy and nasty, too.

1 Like
3

For those who are looking for an easy way to handle it for the time being -
here’s a very helpful backup & restore script for Cubase 12-15 on Windows:

It takes care of all internal Cubase presets and settings including Mediabay. However, VSTis are not fully included for reasons stated above.

3 Likes
4

I agree about the premise, but mixing Cubase preferences and VST3 presets in one folder is not a good idea, because VST3 presets can also be used by other software than Cubase, e.g. VST Live, Dorico and so on. For that reason, there exist defined standard locations for VST3 presets which are independent from any app:

5

Couldn’t that be accomplished by using symlinks or hardlinks to the /users/UserName/Cubase/Prefs and Presets/ directory?

So other applications would still see the required files in the ~library or wherever, but the actual files would be in the /users/UserName/Cubase/Prefs and Presets/ folder?

6

If anything, this reminds me to create a folder with symlinks or regular links to all these folders for quick easy access. Too many times, like you mention, I am scrambling to find or check something. I have a plugins folder for this, but a Cubase all links for everything folder is needed.

7

If you consider Cubase as the “center of the solar system”, then yes.

But imagine you use Pro Tools, and Cubase, and Logic. And then you purchase a VST plugin from a third-party vendor. Where should it be installed to?

One could propose an extra location for VSTs, but … oh wait - that’s how it’s actually done… :wink:

8

I look at the forum on a basis I thought was fairly frequent … so how did I miss this??

Thanks for the heads up, @Reco29 :slight_smile:

9

If only Cubase would do the sym link approach, it would be fine.

Other installers could do whatever the heck they want (as they do now).

10

I’d be happy to beta test it if SB ever is curious. I don’t do mission-critical stuff, so if everything goes kablooie, I won’t die.