Any way to get VST2's and VST3's in different colors like they used to be?

[Greg Wynn]

For old project compatibility I still have VST'2 that comingle fine with VST3's.  However, can we get them to have different colors like they used to ? ?

[Promidi]

Not at this time.

[Colin Nicholls]

Huh, I never noticed that. I've gotten into the habit of dragging instruments from the Browser, where they are likewise hard to distinguish but at least they use different colors there.

Both the menu and the Browser would be better served by just assuming VST2 (or VST3, take your pick) and identifying plugins that are not the default type.

[Greg Wynn]

Ugh.

 

One of the updates made the colors as they are now.  If I remember correctly the vst3’s were blue. 

[sjoens]

Tho it would be nice, is it necessary if they're plainly labeled?

Earlier SONAR versions had neither color nor label so you were completely in the dark until you realized the 1st one was always the VST3. . . as it still is.

[Greg Wynn]

1 hour ago, sjoens said:

Tho it would be nice, is it necessary if they're plainly labeled?

Earlier SONAR versions had neither color nor label so you were completely in the dark until you realized the 1st one was always the VST3. . . as it still is.

It’s a thing that we used to have.  Is it necessary ?  Nope.

But it was part of my workflow and made things 1% easier and sometimes just that 1% makes a difference.

Why was it ever changed ?

[Greg Wynn]

this 


 

[sjoens]

37 minutes ago, Greg Wynn said:

Why was it ever changed ?

You'd have to ask them.  My guess is the new GUI changed the way things are displayed and they're keeping it simple during the major revamps and will implement the little things like color options after that.  When, is anyone's guess.

[Kamikaze]

Out of interest, is there any reason to use VST 2 when you have VST 3. 

I've excluded the VST 2 from the plugin manager, and where given and option on install tended to exclude VST2 along with anything else, although I'm not consistent with that, and some installers require you to go into setting I didn't realise until after the the install.

 

[Promidi]

18 hours ago, Kamikaze said:

Out of interest, is there any reason to use VST 2 when you have VST 3. 

Yes.  Some VST3 versions of a given synth plugin do not respond to patch change MIDI events, whereas the VST2 version does.

Edited yesterday at 02:48 AM by Promidi

[John Vere]

I simply use plug in manager an exclude the unwanted version. 

[Greg Wynn]

15 hours ago, Kamikaze said:

Out of interest, is there any reason to use VST 2 when you have VST 3. 

I've excluded the VST 2 from the plugin manager, and where given and option on install tended to exclude VST2 along with anything else, although I'm not consistent with that, and some installers require you to go into setting I didn't realise until after the the install.

Backware compatibility.  Recently I opened a project from 2009 and it opened fine (save for plugs that had long been deleted) and it opened fine with the vst2’s that were still installed. 
 

BTW - HUGE kudos to the Bakers making it so we can open files saved 15+ years ago.  Try that, Pro Tools fans

[noynekker]

16 hours ago, Kamikaze said:

Out of interest, is there any reason to use VST 2 when you have VST 3. 

I've excluded the VST 2 from the plugin manager, and where given and option on install tended to exclude VST2 along with anything else, although I'm not consistent with that, and some installers require you to go into setting I didn't realise until after the the install.

 

One of my favourite synth plugins Omnisphere is a VST2 . . . Omnisphere 2 which is VST3 costs $500 . . . that's a big reason for me.

[Kamikaze]

2 hours ago, Greg Wynn said:

Backware compatibility.  Recently I opened a project from 2009 and it opened fine (save for plugs that had long been deleted) and it opened fine with the vst2’s that were still installed. 
 

BTW - HUGE kudos to the Bakers making it so we can open files saved 15+ years ago.  Try that, Pro Tools fans

When you exclude a plug in in Plug In Manger, it just removes it from the menus, but it's still there. So if you exclude a plug for a newer version and open the old project, the original plug in is in the project, just not the menu. 

[John Vere]

2 hours ago, Kamikaze said:

When you exclude a plug in in Plug In Manger, it just removes it from the menus, but it's still there. So if you exclude a plug for a newer version and open the old project, the original plug in is in the project, just not the menu. 

Yes and then I simply use Replace and then add the VST3 version. I personally have no issues with VST 3 versions of my collection. 
 

My method keeps the menu clean. 

[Kamikaze]

Yeah, that's why I do it, I don't use program changes, so haven't run into VST3 being unresponsive. So VST3 only when  I have the choice. 

 

Is there a way to edit the Vender, or is that baked into the VST code? I have 2 folders for iZotope, (iZotope and iZotope, Inc).