Let's hope you get this sorted soon, LJB.
 
I, too, live outside North America, and so have to rely on Email support, which can be a little s  l  o  w..
 
I have found Cake's support on this forum remarkable, though. Many times I have found help by either posting on here, or  by P.M-ing Cake staff.
 
This forum, and Cake's customer service, are a major selling point for Sonar, as far as I'm concerned.

LJB
This just in from Mr Slate himself, or whomever runs his personal Facebook page:

"Hi Ludwig, VCC will be ported soon to our new framework and bugs will be fixed."
 
 
 
Bob, thanks for YOUR offer too - I'm in too deep with my mixes, and the bugs go back to early versions of X2 or X1. I reinstalled VCC only using the 64bit option, and it seems MARGINALLY more stable, for whatever reason, provided I adhere to a few odd workarounds (like don't click on the console view until you have opened some buss plugs in the Bus view etc). I'll persist on this course for now. Thanks for listening guys. And please know I am a huge defender for all things Sonar, in a land ruled by Mac-based DAWs. :O)

I was just fixing to say that all his plugs are supposed to be updated soon. A couple already have. I hope everything gets worked out for you. Hang in there!

LJB
This just in from Mr Slate himself, or whomever runs his personal Facebook page:

"Hi Ludwig, VCC will be ported soon to our new framework and bugs will be fixed."
 
 
 
Bob, thanks for YOUR offer too - I'm in too deep with my mixes, and the bugs go back to early versions of X2 or X1. I reinstalled VCC only using the 64bit option, and it seems MARGINALLY more stable, for whatever reason, provided I adhere to a few odd workarounds (like don't click on the console view until you have opened some buss plugs in the Bus view etc). I'll persist on this course for now. Thanks for listening guys. And please know I am a huge defender for all things Sonar, in a land ruled by Mac-based DAWs. :O)

 
tell slate that VBC has issues as well (at least on my system ) ...it was working great X3 B and no more X3C (VBC fg grey only ..weird ) so new framework isn't a waranty....some happened (in the plugin maganement) from X3B to X3C , would love to know what 

LRL, not sure how to take your comment, so I'll just acknowledge that I received it. Thanks for the "Good Luck".
 
I will add this - if you are implying that I am arrogant, or an a-hole, because I demand a product that I paid good money for (in advance) to work, then hey, I'll gladly wear that moniker, and also the one that says Consumer Rights.
 
I'd like to remind you that I don't escalate anything unless it's a real problem, and I always follow the proper communication lines first. I have all the communication datiing back to speaking to Brendon about this to prove that.
 
When it's fixed, at least you'll also enjoy the benefits of a better system.

All right, misunderstood you, LRL. I agree that my tone has gone through the roof. When I'm not trying to fight with deadlines and crashing software, I'm actually a pretty nice guy. Hopefully my good humour will return shortly :O)

Signing off and shutting my mouth now.

Zo

bitflipper
I don't want to aggravate your aggravation, Ludwig, but an unhandled exception raised by a DLL is more likely to be an issue within the plugin rather than the host.

unless it' was working great in version A and not version B of the daw ;)
 
had the isssue with VBC ...rolled back to X1 ...wating patiently ..X3 rocks but has been dangerous ....for me ..

Well, an unhandled exception is something not handled properly within the failing module, which I believe is Slate VCC in this case.  
 
This unhandled exception condition could certainly be exposed by some coding difference between two releases of Sonar, but without question the Slate component did not properly deal with a failing return code from calling some subroutine.
 
It may well be that there some fixes needed for one or more things between X3b and X3c, but this would be a separate issue than the VCC itself needing some tightening up of its error handling logic.  In typical error handling, routines are often written to have specific handling of the most likely kinds of failures that can occur when calling a subroutine, and then if a given error condition is not one of those, there is normally some generic reporting of the condition and some sort of controlled exit.  In this particular situation, that sort approach was not bulletproof, and one or more error conditions are not properly processed.
 
I DO agree that if you have something working in X3b, and then you end up with an issue like this in X3c, that rolling back to X3b makes perfect sense, while you wait for the fixes to the failing component that were exposed by processing with X3c.  
 
Bob Bone
 

Agreed Resonant.
And run Windows update, update your firmware and drivers everywhere, and make sure you run this afterwards:
http://forum.cakewalk.com/Driver-Boost-m2928792.aspx

And then chkdsk and SFC /SCANNOW.

It may not appear related, but best to rule everything out first...

How the ilok driver can be faulty since other Ilok plugins are working ...?
 
Anyway for my parts i upadted everything even if it's not at all logical ....ilok /plugin version /re install ect ....
 
And then in X3D things will re work again ...and all this psycho dance will end ....
 
IF some is working a time T and not at time T+1 then what have changed since T : if nothing but sonar , so it's SONAR !!
 
as simple as that ....
 
LJB don't waist your time by going in to deep ..roll back if you have an back up ...work and then re check in X3D ....

I have to also have the view that even if the only thing that changed was Sonar, that there may be one or more issues in plugins that are only exposed by the Sonar code, but not CAUSED by the Sonar changes.
 
This is quite common in things like plugins, as every developer has to interpret the specifications for things like VST 3, and often these kinds of specs can be interpreted in multiple ways, if some parts of the specifications are a bit on the vague side.  So, it is quite possible that Sonar is correctly following these specifications, but some plugin is not quite doing the same kind of thing in THEIR interpretation of the specification, then problems can show up after updating Sonar - when the fault may actually lie within the plugin code, and only just now failing.
 
I LITERALLY had this happen with a program I use, called Forte, from a company called Brainspawn.  (GREAT program for live gigging for keyboard players, by the way), and my Presonus AudioBox 1818 VSL audio interface.  In this case, Forte got updated, and problems immediately showed up with it following the update, but it turned out that the Presonus developers had used some really obscure parameter in their drivers that only got exposed through the Forte update - but the problem was actually in the Presonus use of the obscure parameter.  The Brainspawn folks actually entered into dialog with me, and they were kind enough to actually change their product to allow the Presonus use of this goofy parameter that nobody else on the planet was using, so that's how my situation got resolved.  The point is that these kinds of scenarios actually DO exist. 
 
Bob Bone