How many plugins are allowed in Sonar X2?
I just re-scanned for update x2a & received the limit reached message for the first time ever &  haven't added new ones in over a week.
 

I've got several hundred.

I get that message when I'v double installed the same plug in different locations (it happens on an update if I'm not careful to select my layout, not the default). Look around and see if you can find a dup plug.

Thanks bapu,

I'll check it out , wondering if the x2a update has anything to do with it since it's never happened before.

I also saw for the first time after scanning & closing the pref window that there's now an asio type scan. This is also new since the update.
Have you or anyone else seen this before?
Do you know what it does?
It goes by so quickly I can't read the message.

It is like 700-800.  Of course, some plugs take up more slots with several variations.  It is a windows or VST2 thing.  There are a couple of old threads about it.

@

I haven't tested X2a to verify if the plug-in maximum limit has changed but since there was no mention in the release notes to indicate a change I would be inclined to believe that  the maximum plug-in limit is still the same.

For Sonar 8.5** through X2 - the maximum limit on how many plug-ins Sonar can load is:
735 FX plug-ins
255 synths
31 rewire devices 

**never bothered testing earlier versions to check.

It's not a Windows thing or a menu thing, its a fixed allocation of memory thing vs dynamic allocation thing.

X2a does address a number of plug-in issues such as  - addressing plug-in dupe issues where if there were both 32 & 64 bit versions of the same plug-in and both had the same CLSID# (not an unusual occurrence).  Previously you couldn't be sure which it was actually be used until you had a problem.

Haven't had time to take an in depth look, but it is nice to see that plug-in management got some attention this release.

TheSteven


For Sonar 8.5** through X2 - the maximum limit on how many plug-ins Sonar can load is:
735 FX plug-ins
255 synths
31 rewire devices 

**never bothered testing earlier versions to check.

It's not a Windows thing or a menu thing, its a fixed allocation of memory thing vs dynamic allocation thing.

Actually the limit is "in force" when no custom plugin layout is used, with a custom plugin layout, the layout is loaded by an xml and I don't believe there is a limit.

If there is a limit, it is huge because I've never hit it.

My custom layout has all my plug-ins sorted by what they do such as dynamics>compressors, etc. AND by vendor such as FabFilter, Voxengo, etc. so my layout is probably double the size of how many plug-ins that I have on my sytem and I don't get a "limit reached prompt".

gustabo

TheSteven


For Sonar 8.5** through X2 - the maximum limit on how many plug-ins Sonar can load is:
735 FX plug-ins
255 synths
31 rewire devices 

**never bothered testing earlier versions to check.

It's not a Windows thing or a menu thing, its a fixed allocation of memory thing vs dynamic allocation thing.

Actually the limit is "in force" when no custom plugin layout is used, with a custom plugin layout, the layout is loaded by an xml and I don't believe there is a limit.

If there is a limit, it is huge because I've never hit it.

My custom layout has all my plug-ins sorted by what they do such as dynamics>compressors, etc. AND by vendor such as FabFilter, Voxengo, etc. so my layout is probably double the size of how many plug-ins that I have on my sytem and I don't get a "limit reached prompt".

Sorry, but you are wrong (spoken with respectful politeness).
It is something that is 100% reproducible and has been reported to Cakewalk.

This is something that my customers and I have flogged till frothy and is not effected by OS or hardware.

Doesn't matter if you use custom menu layouts or not.
The limitation is not in the registry databases created by the VST Plug-in Scanner, nor is the limitation in the xml plug-in menu structure that you referred to.
The limitation is in the amount of fixed memory that is allocated in Sonar's internal data structure to hold plug-in information.
If your plug-in menu has over a thousand unique FX plug-ins in it - only 735 of them will work and you don't which 735, the rest are just dead menu items.


This is a design issue, an old design issue and I understand Cakewalk's reluctance to deal with it.  Its probably one of the older pieces of code in Sonar and the original programmers may be long gone.  Its like replacing the old galvanized piping in your home with copper. It may be a messy job and if you make a mistake somethings gonna be broken and the kids are all going to be screaming at you.

Edit:

gustabo

My custom layout has all my plug-ins sorted by what they do such as dynamics>compressors, etc. AND by vendor such as FabFilter, Voxengo, etc. so my layout is probably double the size of how many plug-ins that I have on my sytem and I don't get a "limit reached prompt". 

We're have a minor communication error here - I was referring to the number of plug-ins not number of menu items.
Re-listing plug-ins in multiple menus or submenus is not the issue and does not effect the maximum plug-in limit in any way.
As a note - Sonar's internal data structure is loaded without consideration to the plug-in layout menus in use. So if you've exceeded the limit you may still have dead listing in your menus even if the menu contains less than the max number of plug-ins.

Thanks for the help.


I always use custom menu layouts but this is the first time I received the limit message..
I checked & had 599 total fx plugins listed. I suppose it's no longer a 735 limit or maybe another x2a bug.

I just removed my full x86 search scan folder path for the moment since I only need a few & used direct paths for those.

@TheSteven,
ok, I stand corrected.
Thanks!