Bapu obviously cares about post count. ;-)

I had 700 odd but I'm thinking of trimming some of the old junky stuff that never sees the light of day.

Grum.

Good news!

The Bapu
Again I say WOOT WOOT.
 
Thanks CW.

So now he just needs to learn to use a dozen of them properly and he can delete the other 1250!

damon777

The Bapu
Again I say WOOT WOOT.
 
Thanks CW.

So now he just needs to learn to use a dozen of them properly and he can delete the other 1250!

Nah, he can keep them.  Just buy a bigger hard drive to teach those darned VST's a lesson.  (I guess that means I am losing it when I start showing electrons where to go).

Seamless, genius, limitless <tm> :)
Actually in X3 you can very easily run into high plugin counts since if you have both VST3 and VST2 versions of your plugins you have doubled your count. Especially true with Waves plugins. This is what pushed us harder to address this issue. 
I recommend turning on the hide related VST2 plugins option to remove redundant UI clutter if you intend using VST3 versions when available. Note that hiding them from the menus doesn't prevent you from loading projects containing them. Its a UI choice only.

Noel, on the "seamless, genius, limitless...No more plugin limit warnings! Past versions supported upto 700 plugins in menus. SONAR X3 now supports unlimited plugins in menus and in the plugin browser" feature......it does seem that a limit does exist as some of my plugins are missing.
 
In the Manage Layout screen, some of the VSTs that are listed there do not appear in the plugin listings....so the same limitations are present in X3 as in X2.
Could you explain how the "unlimited plugins support" manifests itself if plugins are still missing...or am I doing something wrong? (Note that I scanned it using Sonar X3's VST scanner and I'm on Win 7 64-bit)
 
maxxx

There's a preference for hiding VST2 plugins if a VST3 equivalent exists.   Perhaps that's coming into play?   I believe that would only hide them in the Browser.
 
 

stevec
There's a preference for hiding VST2 plugins if a VST3 equivalent exists.   Perhaps that's coming into play?   I believe that would only hide them in the Browser.
 

 
Point of information regarding this...
There are 2 options is found under Edit/Preferences/VST Settings under the VST 3 Migration settings area.

• Hide Related VST2 Plug-ins
  This has been confirmed as only hiding the concerned plug-in in Sonar's default menus.  Custom menus are unaffected.
  
  
• Replace VST2 Plug-ins When Opening Projects
  This concerns replaced plug-ins used in a project, such as a plug-in inserted in a tracks FX Bin.
  Sonar's help has a table that "shows the expected plug-in substitution results when opening projects containing VST plug-ins."

 

The Bapu
Again I say WOOT WOOT. Thanks CW.

Can't think of any other word than 'immense'