jb101
 
 
I'm sure it can often be system issues, but to make such a blanket statement is ludicrous.
 

And you think "blanket blaming" and "broad brushing" every issue to be caused by Sonar is not?

joden

jb101
 
 
I'm sure it can often be system issues, but to make such a blanket statement is ludicrous.
 

And you think "blanket blaming" and "broad brushing" every issue to be caused by Sonar is not?

No, I think they're as bad as each other, so I do neither.
 
Criticising one whilst doing the other is odd, IMO.

btw, where in my post did I say it WAS his system anyway? I only suggested it might have been. Which I would have thought was obvious with my statement..
 
"Not saying that is the case here, but anecdotally, it is remarkably similar."
 
And I did not criticise one and do the other, read the post...it was a question to you...so your reply is a bit odd. Anyway lets just leave it there and concentrate on trying to help the OP. If at all possible.

For what it's worth...I just installed X3c (and set a system restore point first, just in case). I opened a project and it had a ton of missing plug-ins, including Cakewalk ones, which concerned me. I closed Sonar, opened, created a new project, and ran the VST scan. After the scan was done I opened up the original project, and all the plug-ins loaded properly.
 
Just to be ornery I rooted around my hard drive for some projects done in X1 and X2, and they all loaded properly too. This included several projects that had lots of plug-ins from Waves, Universal Audio, and other companies. So either I'm lucky, the Gods of Sonar like me, or the VST scan thing is indeed an important part of the update process.

Ironically, I was in a rush out the door when I saw X3c was out, so patched and ran out the door without a thought. I have only gotten to play with it a little bit since I got back, and only seen the spectrum analyzer so far, which disabling the 64-bit DPE resolved. I will give it a better workout this evening.
 
Sharke's post made me scratch my head too. I am curious why things are not more universal myself. From a cursory look at things, it seems that the ones "not overly affected" have been Win 7 users??

Anderton
For what it's worth...I just installed X3c (and set a system restore point first, just in case). I opened a project and it had a ton of missing plug-ins, including Cakewalk ones, which concerned me. I closed Sonar, opened, created a new project, and ran the VST scan. After the scan was done I opened up the original project, and all the plug-ins loaded properly.
 
Just to be ornery I rooted around my hard drive for some projects done in X1 and X2, and they all loaded properly too. This included several projects that had lots of plug-ins from Waves, Universal Audio, and other companies. So either I'm lucky, the Gods of Sonar like me, or the VST scan thing is indeed an important part of the update process.

I'm not sure about the OP, but in my case the vst reset and scan was my first step to try to fix things, as well as turn off 64bit in the settings and checking for mono tracks.  I'm hoping a clean install of Sonar will fix things as my issue seems to be different than others (although all the projects with issues does have the console emulation in use).

Thanks for all the comments guys. Just to put a few things straight, whilst I am no IT expert I would say I was above average. I made absolutely no changes to my system before or after updating to X3c. I have been using Sonar since Sonar 5 so I am not exactly a newbie to the way they do things. X3b was running with no problems whatsoever before the update, and seems to be running without any problems since I rolled back (fingers crossed). Like I said I am no expert so I am not speculating that it's my system or CW, I was merely stating the problems I had after the update to hopefully help the situation and make CW aware that there seems to be a few discrepancies with the update. I am certainly not on here to bad mouth Sonar, I love the program and this set back changes nothing. I would go as far to say that I am fairly certain it is not my system as I previously pointed out I made no changes apart from updating (and I am not connected to the internet so there would have not been any background updates inadvertently occurring). By process of elimination I would conclude, therefore, that the update caused the very random problems with my system. I am really glad that it seems that not too many people are having problems and I hope my problems are isolated.

As an addendum I tried most of the things people have mentioned above and in other posts to rectify the situation before the rollback and it is possible that more tweaks may have helped. However I would rather stick with X3b for the moment as turning things off, not using particular settings and executing work rounds in my usual workflow to make X3c work, seems like a step backwards frankly.
 

I would ring tech support, if I were you.  Sorry if someone else has suggested this.
 
X3c should work fine for you.  There are so many fixes in it that it would be a shame to roll back.
 
 
edit - just seen that you are in Dubai - not sure what the call would cost, but it might be worth it to get everything working.  Could try emailing, too.

Thanks JB101. I might just do that. I am back visiting the UK in a week or so, so I might leave it til then as it will be cheaper to call. Will probably email them as well. Obviously would prefer to update to X3c, but more than happy with X3b as things stand.