Although this is possible by editing the Plugins XML file, it would be much better if you could rename the “friendly name” of plugins as this can provide easier ways to search for plugins when you have a large number (by adding more description in the name) so you don’t have to remember sometimes obscure product names.
This request has been posted multiple times since for each end every Cubase version… to no result.
https://forums.steinberg.net/search?q=Plugin%20rename%20%23feature-request
2 Likes
I find that using custom folders etc. really helps. A made a little video a while ago about things that you are probably already aware of but may be worth a quick watch.
1 Like
I already use custom folders extensively, but it is often quickest to search using my custom names that I manage (carefully) through the XML plugins file. But thanks for the suggestion and it is certainly something I would recommend to all users.
2 Likes
Custom collections are great, but don’t solve the problem of overly long plugin names that get crippled in the insert slots and worst case, aren’t even properly distinguishable in the mixer because of shortened names.
This could only be solved by having plugin name aliases, which I am all for, but I doubt that we will get it anytime soon, seeing how often it has been requested (and actually rarely voted for).
Honestly though, renaming plugins in plugin manager, if it ever happened, could never be as fast as just editing the XML, as described briefly in the video,.
XML can be edited like a text file. It is very easy and fast.
If you use something like Notepad++ you can also search replace, use regex etc.
1 Like
I’ve moved this feature request to an existing topic.
In my opinion, editing the XML is not a good idea if you create your own collections of vstpresets, because these files rely on the plugin name for identifying the presets so, if you manually change that name, you will lose access to your previous saved vstpresets.
Dang, you’re right. The only area where cubase uses the plugin name, as it seems.
And i just started to write a powershell script that could do all the renaming semi-automatically…
You could also rename all the folders of course, but it will never be more than a dirty workaround. It’d be much better if Steinberg implemented plugin name aliases in the manager.
1 Like
I see the point here is not only to aid with searching but that was what the OP was asking for before this thread was merged.
Nope this is not correct.
Rename a VST3 plugin in the your custom XML and try it.
It is only the name in the dropdown list that is affected. Assignment is done on IDs. In fact you can have multiple copies of the same plugin with different names. I have been doing this for years.
But not to worry, I can’t actual fix the problem so was just posting my work-arounds.
2 Likes
+1 from me, makes life so much better!
1 Like
+1
In other DAWs you can rename different instances, but of course not in cubase. Although this simple feature has been requested for many years.
+1
(cannot upvote because Steinberg limits votes?!?!?)
1 Like
Yeah everybody gets 6 votes. It’s kind of a good thing: it makes everybody prioritize their top feature requests. If you click where it says Limit under Votes, it shows a link to “List Your Votes”. If you go into your vote list you can click on one that has been fixed, fulfilled, or you don’t care about, and that will take you to that topic. You then click on your vote there and that will free up a vote which you could use here.
Ok, thanks for the update! Steinberg in a quest to combat inflation of a different kind ( 
I wish plugin rename feature to work directly in the Mixer as I need this feature to differentiate many instances of one plugin from each other. R-Click and Rename would be perfect.
The reason I do this is Dolby Atmos. I stack several Stereo plugins on top of each other and use the Routing Editor to choose what plugin affects which two channels. Renaming in Mixer would allow to see easily which instance to edit.
As it is now I need to open the Routing Editor to confirm which channels each plugin affects and it is very slow.
yes please +1
2 Likes
+1
Please Steinberg. It’s about time to finally implement this feature
2 Likes
But now try to open a vstpreset that you saved with the old Arousor name. Cubase won’t find anything, because it actually uses the VST name, not the plug-in ID, to create the subfolder inside the main developer folder to put the vstpresets. In your example, if you now save a vstpreset it will go to a new folder called “I am Aroused”, not “Arousor”.
By the way, maybe it’s time to start asking for this feature to be implemented in Cubase 14…
2 Likes