If there is not already a feature request, create one.

alewgro
i just wish there was a way that FX names in the FX Bins can use the name I give it in my custom Plugin-In Layout over the actual VST registered name, as I like my names better.  

Absolutely.  That would eliminate the problem altogether!

scook
If there is not already a feature request, create one.

 
i already did :)


http://forum.cakewalk.com...VST-Name-m3208151.aspx

You can and it works for me (with a proviso): rename the plug-in in the middle pane of the plug-in manager and use a custom menu. You have to do *both* for the plug-in to use your name in the FX bin. And, yes, it works for VST3's here (Melda and Cakewalk CA2A are the only ones I've tried with).

Proviso: SONAR is sometimes too smart when you have names starting with the same root and displays the difference in the FX bin (eg. If I have 2 plug-ins named Reverb (Cakewalk) and Reverb (non-Cakewalk), it will display the part in brackets).

Actually, second proviso: some DX effects can't be renamed in plug-in manager unless you run it as admin because of registry key security (Sonitus FX and Cakewalk MFX are like this).

I've done this before, but then sometimes Sonar decides to re-scan your VSTs and all the names revert... not sure why that would happen, but I have seen that happen before.    great workaround though.
 

KPerry
You can and it works for me (with a proviso): rename the plug-in in the middle pane of the plug-in manager and use a custom menu. You have to do *both* for the plug-in to use your name in the FX bin. And, yes, it works for VST3's here (Melda and Cakewalk CA2A are the only ones I've tried with).

Proviso: SONAR is sometimes too smart when you have names starting with the same root and displays the difference in the FX bin (eg. If I have 2 plug-ins named Reverb (Cakewalk) and Reverb (non-Cakewalk), it will display the part in brackets).

Actually, second proviso: some DX effects can't be renamed in plug-in manager unless you run it as admin because of registry key security (Sonitus FX and Cakewalk MFX are like this).

Woah, it appears in the new version, if you rename a VST in that middle column (that effects the registered name), it reverts back right away, it doesnt stick!

I don't know if you can do this with waves... but most *.dll plugins can be renamed at the window's directory level. I operated by doing that for quite a while - it became troublesome in 2 areas. One was plugin updates and the second problem was older projects not seeing those plugs.

alewgro
Woah, it appears in the new version, if you rename a VST in that middle column (that effects the registered name), it reverts back right away, it doesnt stick!

That doesn't for me (except for some DX and MFX as above); works as expected.

Yeah, some users are seeing this behavior and some aren't. I still have an open ticket with Cakewalk, sonar won't save/keep name changes made to my FabFilter VST3 plugins.

Thanks
Just to make sure we are all on the same page....  All I want to do is precede all of my waves plugins with the name "waves"  such as "waves rbass".   When I change the name of the effect, Sonar allows me to, however  it immediately reverts back to rbass. 
 
Thanks for opening the ticket with waves.