• SONAR
  • [RESOLVED] The Neverending VST Scan (p.4)
2013/10/03 00:31:38
DigitalArchivist
Dan Gonzalez [Cakewalk]
 
Is it safe to say that everyone in this post has 400+plugins? Don't be shy to tell me your number. :)
 

 
Dan, not sure of my exact number, but in SONAR X2 Producer, as you may know, it's not capable of handling more than 255 plugins unless you organize them into folders, which is a pain. This applies to be VSTi and VST plugins. I sure hope this problem has been fixed in X3 which I'm now downloading. Certainly the promise of unlimited should also apply to plugins!
 
Update, October 3, 2013
 
I've had my PC off and on and it finally finished the scan this evening, but I think that only happened after I removed one of the folders it was looking for which was C:\Program files\Steinberg\VSTplugins or something like that. The plugins installed under C:\Common files\Steinberg\VST3 are all now there. Also, the first time I fired up X3, the auto scan hung up on MeldaProduction's MDrummer large with 16out. I uninstalled the program and will now install it as it supports the VST 3 format.
 
I was amazed that my plugin count was over 900!
 
I'm very much looking forward to working further with X3.
2013/10/03 00:35:30
scook
Noel answered you here
there is no limit to plug-in count in X3
2013/10/03 00:50:16
Eric Beam
Nebula is one vst that updates a .xml file in the vst directory while in use. I've noticed the background scanner kicking in with X3 while using Nebula. But I haven't experienced a scan loop on launch.
2013/10/03 07:02:52
smallstonefan
I appreciate your help Noel, and glad I could also contribute to polishing the migration. TRUST ME, I know better than most people the challenge of a new software release! ;)
 
If I can find some time I'll take a look at the file dates. I am taking tomorrow off, but hope to spend most of it goofing off. I definitely want some time with the new comping tools. :)
2013/10/03 11:26:25
TheSteven
Noel Borthwick [Cakewalk]
I'll alert tech support to put a KB article about this. Perhaps for the next update we can forcibly disable rescan all / failed if automatic background scan is on. That way it will prevent someone getting into this scenario.



Wouldn't it make more sense to have those options function as one time toggles?
Where if you turn them on - that the scanner turns them off as soon as appropriate or at the latest when the next scan is complete?
For example - if I remember correctly Rescan Existing starts off by nuking the existing plug-in database so that option could be modified to turn off as soon as that action is done.
 
2013/10/03 11:43:03
Noel Borthwick [Cakewalk]
I agree. They are inefficient and unnecessary to be left on permanently. We'll look into it.
2013/10/04 00:41:07
maxxx
scook
Noel answered you
there is no limit to plug-in count in X3


Has anyone tested this yet? It seems that X3 will process unlimited number of plug-ins and show a total count (VST, DX, VSTi, DXi etc) that is large but from my testing, it seems that there is still some limitation when you actually try and access the individual VSTS as I'm noting that some VSTis are missing from the 'Default All Plugins' list....is there still a limitation of 255 VSTis in X3?
2013/10/04 08:01:04
Noel Borthwick [Cakewalk]
There was never a limit of 255 audio plugins. It was much higher than that - more like 600 or more in X2 and earlier - I don't remember the exact number but there was a specific range allotted to plugins, synths etc. We no longer use ranges so this issue has been solved.
 
Please explain how you are coming to that assumption - where exactly in the UI are you looking for the plugins and which specific plugin is missing? Did the scanner report a count that includes all your plugins? Most likely you are looking in the wrong place or trying to pair up the scanned plugin count with what you see. Or perhaps you have not added a scan path for a plugin folder.  In the plugin browser try using the search box to find the plugin that has been scanned.
 
The count reported by the scanner includes *all* plugins. VST2, VST3 as well as 32 bit and 64 bit versions that are found in the scan path. However the menus and plugin browser will filter out redundant choices. e.g it will only show a 64 bit version if both flavors exist. Additionally if hide vst2 plugins is checked, SONAR will favor VST3 plugins on the system and hide the corresponding VST2.
 
I have over 900 plugins on my system and I can access all of them via the plugin browser with the Default - All plugins choice selected.
2013/10/04 10:43:24
maxxx
Thanks for your input Noel.
I was referring to TheSteven's posting on KVR dated 25 Jul 2012 entitled "Latest notes on Sonar's maximum plug-in count limit" ( ) which states that plugin limits for X2 are as follows:
"735 audio plug-ins
255 synths
31 rewire devices"
When I scan my X3, "Scan complete. 1008 plugins found" in the little pop-up box in the lower right.
Based on the X2 limit numbers it seems that for audio plug-ins (VST, DX etc) I am within limit but for synths (VSTi, DXi, VST3 synths etc) I seem to be above the limit by almost 20. So I checked them one by one against the files in the selected VST filepaths scanned and also the Manage Layout list vs the Browser list for the missing ones, I also checked that they did not have a corresponding VST3 version eg. Massive (and ensured that these were not redundant choices that were filtered out)
Another example: Retrologue which I have both VST3 and VST2 versions was missing in both.
(For all of these I am using "Default All Plugins")
 
Anyway, when I took away the excess plugins and kept it within the earlier stated X2 limit, all the missing plug-ins reappeared. This seems to suggest that some sort of limit might be present.
Lest the naysayers say that I should just use a limited number of VSTS, do note that for X2, I keep it within limits and just use the VSTs I need but since it was stated that there were no limits for X3, I was trying to load lots of my freebie VSTs that I had not used for ages just to test them out.
 
Hence, that is why I was asking if anyone tested the plugin limit - I did and I seem to have missing plug-ins. If I am doing something wrong, I would gladly welcome being pointed in the right direction. Note that I also did the Full VST Rescan Recommended for Upgraders here:
 
 
2013/10/04 11:09:12
smallstonefan
Noel,
I just wanted to update you - I've looked at the VST folders (probably not all of them) and I don't see any files that are being updated by the scanner. If I run across one, I'll certainly let you know...
© 2025 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account