To me the way it reads it's for the scanning process.

Sandboxed scanning is only for VstScan when it is run from Preferences | VST. It doesn't sandbox plugins themselves at run time. While it could be useful its a much more difficult to do properly and sandboxing plugins at runtime actually can cause additional compatibility issues with some plugins as we have seen with BitBridge.
 
The VstScan sandboxing runs each plugin in a private sandbox mainly to prevent them from corrupting the rest of the scan. It has already solved many problems in our tests including making scanning plugins like Waves more trouble free.
 

Noel Borthwick [Cakewalk] plugins like Waves

which others did you test? care to share?

Noel Borthwick [Cakewalk]
Sandboxed scanning is only for VstScan when it is run from Preferences | VST. It doesn't sandbox plugins themselves at run time. While it could be useful its a much more difficult to do properly and sandboxing plugins at runtime actually can cause additional compatibility issues with some plugins as we have seen with BitBridge.

 
Just to be clear, this is an option/tool to use "if" you have an issue during the VST scanning process to isolate any offending plugins? You would not keep this enabled as a default? I have the option enabled to auto scan for new VST's each time SONAR opens. So in this scenario, I should keep this new Sandboxed scanning disabled until there is a need to use it? I want to be sure I am using this new feature in the most optimum and correct way.
 
Thanks Noel and keep up the great work on CbB!
 
 

FWIW it seems to be on by default.

Matron Landslide
FWIW it seems to be on by default.

so waves work

Billy Buck

Noel Borthwick [Cakewalk]
Sandboxed scanning is only for VstScan when it is run from Preferences | VST. It doesn't sandbox plugins themselves at run time. While it could be useful its a much more difficult to do properly and sandboxing plugins at runtime actually can cause additional compatibility issues with some plugins as we have seen with BitBridge.

 
Just to be clear, this is an option/tool to use "if" you have an issue during the VST scanning process to isolate any offending plugins? You would not keep this enabled as a default? I have the option enabled to auto scan for new VST's each time SONAR opens. So in this scenario, I should keep this new Sandboxed scanning disabled until there is a need to use it? I want to be sure I am using this new feature in the most optimum and correct way.
 
Thanks Noel and keep up the great work on CbB!

 
Hi Billy,
 
The option is on by default so that most users will have a good experience when scanning plugins out of the box. This is one of the common technical support issues so its best this way. Its very hard to troubleshoot scanning issues since data corruption may be caused by any prior plugin in the scan process - most often the plugin that exhibits the problem during scanning isn't the culprit itself but is more susceptible to the corruption.
 
There is really very little overhead with this feature since the sandbox only kicks in when its actually scanning a plugin. i.e if scan on startup is on we don't do any work unless a new plugin is detected so the sandbox scan will never run.
 

Great job TEAM!   The program is in the best shape that I can remember!  Keep up the great work and keep chipping away at the bugs! Stability is priority #1!

Any TLC to the PRV is greatly appreciated and both the VST scan enhancements and the improved continuous controller drawing are great features. Add to that the long list of bug fixes and I must say that I’m impressed with what such a small development team can do in just a month. Thank you both Noel and Ben.

Noel Borthwick [Cakewalk]
Hi Billy,
 
The option is on by default so that most users will have a good experience when scanning plugins out of the box. This is one of the common technical support issues so its best this way. Its very hard to troubleshoot scanning issues since data corruption may be caused by any prior plugin in the scan process - most often the plugin that exhibits the problem during scanning isn't the culprit itself but is more susceptible to the corruption.
 
There is really very little overhead with this feature since the sandbox only kicks in when its actually scanning a plugin. i.e if scan on startup is on we don't do any work unless a new plugin is detected so the sandbox scan will never run.

 
Thanks for the clarification Noel!