Seems they are shared?? Yes/No?
 
This is a slight problem/aggravation if I intend to (at least for a while) bounce between X2 and X3.
 
Mainly because I need to exclude some VSTs in X2 due to the limit, but then it appears the exclude list is shared. So if I exclude in X2 they are also excluded in X3. Bummer.
 
I don't expect X2 to go away anytime soon (for me). Of course the day I decide I no longer need to use X2 this will not be a problem but for now it is a big aggravation.

Nothing?

Hi Bapu,
 
At the moment there is no way to have different exclusions between X2 and X3 since the inventory is shared across product family versions. This issue applies to all versions of SONAR. I can see your point through since we now support more VST's than X2 did :)
I will have to think about this...

Noel Borthwick [Cakewalk]
Hi Bapu,
 
At the moment there is no way to have different exclusions between X2 and X3 since the inventory is shared across product family versions. This issue applies to all versions of SONAR. I can see your point through since we now support more VST's than X2 did :)
I will have to think about this...

Thanks for thinking about it Noel. That's all I can really ask for.

You could always get rid of a few plugs. 

Old55
You could always get rid of a few plugs. 

NEVAH!!!!!!!

Could you maintain two different versions of the shared folders and drop the right one in when needed? 
 

stevec
Could you maintain two different versions of the shared folders and drop the right one in when needed? 
 

Are you talking about?
{program files}\Cakewalk\Shared* 
 
Nothing in any of those folders that I can see implies the VST scan or exclude lists. Those are what I'd expect to keep unique.
 
I'm thinking it's in a .ini file but I have not seen or found it.
 
If it was in a .ini file I'd make SONAR allow an override run time argument {configfilename}.ini={usersupplied path}
 
That way my desktop short cut for X2 and X3 could point to different lists.
 
But, that requires the removal of the (probably) hard coded expected file name.
 
Then again, maybe it's all stored in a registry somewhere.

I was actually thinking that I didn't have that many plugs until I fired up X3 for the first time and saw the number 337 after the VST check was complete?!! I realise that this isn't a pinch on Bapu's collection but I still fear that I may have a problem...
 
Could you just figure out which plugs aren't making it through to X3 from X2's list and then copy and paste their .dll's into X3's vst plugin file folder?

You could rename registry keys at runtime using a script and reg.exe...