Potential work around for those having trouble with Arturia Synths

I know that some of you have experienced a problem, as have I, with Arturia's Oberheim SEM soft synth.  i.e. It cause SONAR X3e to blow up when trying to insert.
 
Arturia's recommendation is to roll back to X3d which I personal find unacceptable.
 
I was having a little troll through some of my works in progress and loaded a project in SONAR X3e which contains the SEM synth, which loaded and worked OK.  I consequently tried an experiment.  I cleared the project of every thing except the SEM synth saved it as a template and then tried to use the template to create a new project.  UIt worked.
 
Now I will not guarantee it will work for others and it is really not acceptable but if you want to give it a go you may find it will work for you.
 
As an aside Arturia tell that the problem is with the VST 3 version and not the VST 2 therefore un-installing the VST 3 is also a potential solution.
 
I hope this might help some of you.

I have had little problem with Arturia synths up until X3e andI fail to understand why such a problem now exists all my other VST's work fine it only the Arturia ones that are twitching. 

Seems its the VST3 Arturia synths that are crashing for me CWBRN-26631.
 
The VST2 ones seem to work fine but SEM, Analog Factory and Wurlitzer V are VST3 and all crash Sonar on insert. Now I have to work if I can install VST versions of these.
 

There are 64 bit vst2 versions of the 3 problematic vst3s, no need to use bitbriidge.  I can only confirm that the vst2 version of SEM works correctly in 64 bit X3E.

Instead of renaming or moving the plug-in binaries, it should be possible to go into the Cakewalk Plug-in Manager and exclude the unwanted versions.

Renaming things mess something up!
 
In the end I did "properly" and uninstalled the three offending synths and re-installed with VST3 unchecked. It all works now.

Wookiee

Glyn Barnes
Renaming things mess something up!
 
In the end I did "properly" and uninstalled the three offending synths and re-installed with VST3 unchecked. It all works now.

I did try that but I did not see in the V-Collection installer where I could make that decision to not install the VST 3's probably got fur in the eyes.
 
Importantly Glyn is you sorted it which is good.

While I purchased the V collection each synth could all be uninstalled indivudually in control panel. I just downloaded the latest updated for the individual synths. I was a bit wary of this but once I had screwed things up renaming things I did not have much to loose.

Wookiee
Interesting am I right in thinking you ran the installer for the latest version of the any of the V-Collection synths?
 
What happened when it came to install the e-licenser did you cancel that bit or what?
 
If you did did you have to re-enter a key?
 
Cheers

I just let the installers run, including the eLicencer. I was suprised but I did not need to reauthorise or enter any codes.