I'm just talking about Sonar and I don't see any arguement.
It's CPU cycles vs convenience when it comes to manual vs auto, that's all. Pick your poison.
Until I know exactly what it is that triggers a scan (is Sonar continiously scanning vst directories?) in auto mode I'll stick with manual. I'm not saying that the auto feature is a bad thing either it's up to you what you want.

No scanning is done after the fact. When I say its quick normally its done before I have chosen a project to open. You can check if scanning is continuous by adding a VST after Sonar is loaded and scanning is complete. It will not show up in the VST menu.  

Doktor Avalanche
I'm just talking about Sonar and I don't see any arguement.
It's CPU cycles vs convenience when it comes to manual vs auto, that's all. Pick your poison.
Until I know exactly what it is that triggers a scan (is Sonar continiously scanning vst directories?) in auto mode I'll stick with manual. I'm not saying that the auto feature is a bad thing either it's up to you what you want.

If the guy that writes the code says its best to leave it on auto that's good enough for me. I don't need to be able to build a car to drive one nor do I need to be a programmer to be able to use Sonar.

If cakewalk has the time I'd be interested to learn what triggers an auto scan and when it occurs. Whether there is any polling going on etc. Is the separate process running all the time etc.
 
@Mike the guy who wrote the code still offers a manual scan for some reason. However everybody seems to be implying that auto is a direct replacement for manual scan, and if that is the case then it should be removed.

Doktor Avalanche
If cakewalk has the time I'd be interested to learn what triggers an auto scan and when it occurs. Whether there is any polling going on etc. Is the separate process running all the time etc.
 
@Mike the guy who wrote the code still offers a manual scan for some reason. However everybody seems to be implying that auto is a direct replacement for manual scan, and if that is the case then it should be removed.

Wow! I thought I did answer that. I know I'm not CW but sometimes we users actually know what we are talking about. Most of us wont give bogus information and if we do someone will come along and correct it. I try very hard to be as correct as I am able. Often times I will look something up because I want to confirm it and be sure of what I post. 
 
This is an area I know a little about. I have read everything Noel has written about it and remember most of what he wrote. 
 
You came on here 3 days ago and I have been here from day one. It seems to me you may want to listen to a user that has been here answering questions for many years. Ever since this forum has been around. I can say I have been here longer then some CW staff. 
 
I don't want to sound angry but it is rather insulting. 

John you are implying that auto scan happens only on startup. If that's the case why isn't it called 'scan on startup'?
Auto implies it's being continuously monitored.
 
I have no reason to question you, but you are not the developer and I don't see answers to my questions in the documentation and your answers aren't very specific. Note these questions have nothing to do with how long you or I have been posting in this forum, the actual scan itself or indeed Sony Vegas. 'Something is happening' isn't quite the details I need.
 
Let's split it up shall we. And REMEMBER I'm talking about the file detection process NOT the actual scan itself or any other scanning software OR what goes on when a scan gets triggered (which is exactly the same as manual), these are really yes or no answers:
 
a) Does auto scan only happen JUST on startup as others appear to be saying  (if so please rename it!)
b) OR Is the file detection process running all the time with auto scan ? (Before you say NO rememember cakewalk says it runs as a separate process). If YES how does a scan get triggered (registry or file monitoring or something else?)
c) With manual scan is the detection process running all the time? (the answer is clearly no but here for purposes of completion).
 
Again very specific questions requiring very specific answers. I hope this is clearer now. No need to feel insulted for any reason. I'm sorry you regard all new posters as newbies, please note I don't claim to know it all but I do have some knowledge. It might be better to let somebody else answer if it makes you feel emotional it's not my intention to poke you in any way I'd prefer to stick to topic rather than let personalities get in the way.
 
 

It works as I have described it. I also gave you a test to check it out.  

Of course I've tried it. I'm also not arguing with you about whether you are right or wrong. I just don't think you're really answering my questions accurately or maybe I'm asking for more detail then you can provide. . I bullet pointed the questions above and you glossed over it.
 
Leave it to Cakewalk I suggest unless somebody can point me to better documentation.

BTW
 

John
No scanning is done after the fact. When I say its quick normally its done before I have chosen a project to open. You can check if scanning is continuous by adding a VST after Sonar is loaded and scanning is complete. It will not show up in the VST menu.  

And yet...
 

Noel Borthwick [Cakewalk]

• You can install plugins while SONAR is running and it will pick up the new plugins automatically

So you see my questions in #26 might clear up some confusion it looks like all of us are having. Cakewalk gave some good answers I'm just asking for a little more detail.

I will not contradict Noel. If he says it will then it will.