manually alter the vendor of a VST plugin?

Cubase
1

Is it possible to manually alter the vendor name of a VST 2 or 3 plugin ?

I’d love to consolidate plug ins into one vendor name, as sometimes they are listed under multiple versions of the same name… slows me down!!! :imp: :slight_smile:

2

No

3

Ok thanks.

That is a shame.

We seriously need more plug in organising capability in Cubase. I’m sure this has been asked for in many places on the forum…

4

Win7 here…

Don’t know if it applies to osx:

You might try to edit the cubase vst plugins.xml which cubase generates upon scanning.
Changes are lost after rescanning, though

5

ok cool ill take a look at that thanks

6

I totally agree!

7

For windows and vst2, there’s my VST2 Plugin Manager

8

That looks great and would be great on Mac, but really I feel this should be integrated within Cubase itself.

9

Of course.

I prefer a solution cross-DAW-wide, to organize once and have it organised in every DAW.

10

Actually thats true. Any plans on a OSx version of your app? ! :slight_smile:

11

No

12

Owch :frowning:

13

FYI Site Admin Marcus literally writes: “We are currently investigating how to integrate a VST Plug-In manager/editor in Cubase.”
In this thread

14

Awesome thanks!

15

you can easily do it for your vst2 plugs but not vst3

16

ah ok cool

how do you do for VST 2 plug ins?

17

I guess he meant moving the plugin .dll’s (.vst2 on OSX?) into a custom folder structure, setting the root folder as plugin folder in cubase and don’t sort plugins by vendor in cubase (in which case the custom folder structure is reflected in cubases plugin menus)

It’s not really “altering the vendor” of a plugin, but another way to sort plugs.

I do NOT recommend moving plugin .dlls (.vst2) files around, as this might lead to plugins not working anymore (as they for example rely on data which gets installed into the install folder along with plugin installation)…

18

ah yeah I used to do that and yes had problems with plug ins stopping working

ok thanks anyway

19

I’ve moved the majority of my VST2 plugins into custom folders and never had a problem with any of them not working… worst comes to worst, just re-install a problem plugin into the custom folder and you’re done.

20

no need for reinstallations, moving dlls and data folders, keep track of x32 and x64 and x32/x64 plugins and jBridge and automap and what not… I simply use my PluginManager :wink: