Wookiee
If you go to %install drive%:\Program Files\Common Files\VST 3 and carefully rename the offending VST 3's then open SONAR it will rescan your VST's and delete the offending VST 3 and enable the VST 2 versions.  Then when whomever is at fault with the VST 3 implementation solves the problem you can just rename them back.
 
I find it most interesting that it is only my Arturia VST 3's that fail, even the free ones seem to work fine.

Hello Wookiee,
I renamed the files by putting an 'x' before the VST 3 file names, is this the sort of thing you mean when you say to rename the VST 3's?
If it is, it did not work for me!

Am I doing this correctly?

Thanks,
Paul

The upgrade price is very reasonable so buying it was a no brainer. I was toying around with the Solina the other night - Some interesting sounds. Very vintage.

I had an offer to purchase V Collection 4 for $199 and jumped. Some wonderful sounds in here. However, I have already experienced the dreaded stuck midi note issue that I've read about elsewhere. I just submitted a ticket - we'll see what happens.
 
PS: The Oberheim is wicked cool! :)

p.r.woodward@btinternet.com

Wookiee
If you go to %install drive%:\Program Files\Common Files\VST 3 and carefully rename the offending VST 3's then open SONAR it will rescan your VST's and delete the offending VST 3 and enable the VST 2 versions.  Then when whomever is at fault with the VST 3 implementation solves the problem you can just rename them back.
 
I find it most interesting that it is only my Arturia VST 3's that fail, even the free ones seem to work fine.

Hello Wookiee,
I renamed the files by putting an 'x' before the VST 3 file names, is this the sort of thing you mean when you say to rename the VST 3's?
If it is, it did not work for me!

Am I doing this correctly?

Thanks,
Paul

In the directory computer\local disk ("n")\program files\common files\vst 3\
 
I put the ".X" after the name i.e. "Solina V.vst3.x" 
 
Where "n" is the drive letter of your installation disk

Wookiee

In the directory computer\local disk ("n")\program files\common files\vst 3\
 
I put the ".X" after the name i.e. "Solina V.vst3.x" 
 
Where "n" is the drive letter of your installation disk

I did this and Solina disappeared from the VST3 list in Sonar, but didn't appear in the VST2 list!

Did you have V Collection 3 installed?
If you did, did you install V Collection 4 on top, or did you uninstall V Collection 3 first.

I am a bit disappointed with Arturia, (or is in Sonar's Fault!), because I bought V Collection 4 specifically for Solina and Matrix 12V as I owned all the others!

OK, they do work in stand-alone mode, but I would like to use them with Sonar.

Thanks for your help.

I simply uninstalled the software and reinstalled just the VST2 and stand alone versions. On the old eLicencer system this did not require a reauthorisation. Of course that could be different now.
 
Before you do that check if the VST2 DLLs are in a path that Sonar is scanning and then do a rescan.

I can imagine that the Matrix 12 would have a pretty heavy cpu load just to emulate the basic structure. Maybe this is what's causing the stuck note offs? just processing load? I'm still using very old sonar, but looking into Arturia and a computer update is looking intriguing. Anything but Kontakt is still my moto. Has anyone tried tweaking the midi set-up in Sonar to increase the midi buffers?  Hell I don't even know if that's tweakable in the new Sonar X offerings.

p.r.woodward@btinternet.com

Wookiee

In the directory computer\local disk ("n")\program files\common files\vst 3\
 
I put the ".X" after the name i.e. "Solina V.vst3.x" 
 
Where "n" is the drive letter of your installation disk

I did this and Solina disappeared from the VST3 list in Sonar, but didn't appear in the VST2 list!

Did you have V Collection 3 installed?
If you did, did you install V Collection 4 on top, or did you uninstall V Collection 3 first.

I am a bit disappointed with Arturia, (or is in Sonar's Fault!), because I bought V Collection 4 specifically for Solina and Matrix 12V as I owned all the others!

OK, they do work in stand-alone mode, but I would like to use them with Sonar.

Thanks for your help.

Yes I have the V3 Collection as well as the V4 the installation basically overwrote the V3 install.
 
In your case I would do as Bristol_Jonesy suggests remove them then using the new licencing tool reinstall making sure you, make a backup of any patches you have made then;
 
a, uncheck the installs for the VST3 and any other formats you do not need.
b, install them to a path you know.
 
It does not take long I did it took about half an hour.
 
As to the VST3 problem any other VST3's I have installed work fine it is only the Arturia VST3's that cause a problem.  As it was explained to me it is down to implementation of the authorisation within SONAR that causes the problem though that did come from Arturia not Cakewalk.

Thanks chaps!

I removed the V4 Collection, re-installed using custom, selected stand-alone and VST2, and everything is fine now!

It took about two hours to download and install everything again though, but it was worth it to get them working.

Thanks again.