Apologies to CW RE "Slate vs. Cakewalk" I look forward to them solving their issues.

I have reported over 30 times (I have proof) in the form of Automated Error Reports, official reports and this forum that Slate VCC and Sonar have a problem. Any Sonar project (as far back as X2), crashes at least 50% of the time when I try to open it, and the error is always "Unhandled Exception - Slate VCC ..". 
 
Slate has responded and has been very very helpful, communicative and willing to delve into the issue. They have given me a few test to run, which basically indicates that it is a Sonar problem. 
 
Meanwhile, I have had little more than a "It's a Slate issue" from Cakewalk.
 
Slate VCC works on my PC in Protools 9.06 and Ableton.
 

So... Cakewalk... care to comment? I mean, other than glib replies through "No-Reply" emails?
 

Seriously guys, less lip service about customer care and more customer care would be a good step forward.
 
Sincerely,
 
Ludwig
 
 

Thanks Mettellus, I missed that thread. Doesn't change the fact that Slate is willing to talk to me though :O)

if you're contacting cake via email they are notorious for not replying

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.

Could be since X1 - I've lost track. What puzzles me is that I seem to be the only one having this issue - I see no one else mentioning on this forum. SO, what, do I demand a refund from Slate and loose a great plugin? And no, PC Console Emulator does not come NEAR VCC in terms of sound quality..

Mettellus, I have had endless replies from CW, but they never give me any real solutions, just some lame thing like "Unistall and reinstall VCC".  Then the thing goes dead because I can not keep pushing the button (I actually have music to make to pay my way). Everyone replies (Slate too), then they drop the whole thing like a hot potato.

I might have expressed myself incorrectly, but the bug i still there, and no one is able to fix it. In my defence, I did not actually see Dan's reply (1 week ago).
 
Sorry about that.

Grem, this didn't start this way - it started as polite error reports.

LJB
Grem, this didn't start this way - it started as polite error reports.

Then the purpose of this thread is?

To escalate the issue and to get attention - of course. The previous methods had no impact.

Sorry mate, I'll attenuate and compress my emotional peaks on the subject :O)

I know you are frustrated - but considering the level of active participation in both the forums AND in the development and release of 3 sets of maintenance to X3 thus far (and the promise of at least one more), that it is a bit much to be accusing the Cakewalk folks of 'Lip Service'.  They have been uber present of late, including late at night and on weekends, trying to give everybody they can a smooth X3 experience.  
 
Also, if I read your post correctly, the Cakewalk folks DID respond to you, indicating the issues are with the Slate components.  In the other thread, who's link is posted above in this thread, the consensus was/is there as well that the issues are with the Slate components - including inclusion in Sonar AND in other recording software, as well.
 
I also found the following direct response from Dan Gonzalez (Cakewalk) to YOU, from thread: http://forum.cakewalk.com/X3C-and-Slate-VCC-Still-not-that-happy-together-m2923255.aspx
 
"Yes, I'm currently looking into this now. Sorry for the frustration. The dudes at Slate Digital make awesome stuff and I really want their plugins to work fluidly in SONAR just as much as everyone else :)
-DG"
 
The above would seem to me to indicate that not only have they been responding to you, but that they are also interested in getting the issues worked out, and are indeed actively pursuing doing just that.  
 
And, by the way, in the other thread who's link is above, Ryan Munnis (Cakewalk) ALSO has jumped in to indicate they are actively working with Slate to help them get their issues resolved.
 
Here is the snippet from that thread, with the portion of Ryan's post that pertained to the Slate components:
 
"I personally sent a ton of analysis to the folks at Slate Digital since. To give them credit, they actually reached out to us in hopes to improve the compatibility relationship between SONAR and their products. I'm happy that they did. Hopefully they can make sense of some of the data and can figure out what's going on. In any case, they have my direct contact information if they need to follow up with us so this is hopefully forward progress."
 
AND, Dan Gonzalez also posted in that thread - here is his snippet from that post:
 
"Steven Slate's stuff is unfortunately some of the most reported plugins as far as stability is concerned. I have emailed them personally a few times now without much luck. I'm sorry that you experiencing issues with their stuff. If you want, you could send a long a project. I own VTM and VCC and could possibly try to reproduce the problem."
 
And, for whatever the worth, failures from Unhandled Exceptions indicate that there is deficient code in the VCC component, as an unhandled exception means that VCC has been getting some sort of error response when trying to do something, but the VCC code is not constructed to include dealing with that particular error condition response.  
 
In other words, if I write a program, and it does a 'call' to perform some task, and the task cannot be performed for some reason, an exception will be 'thrown', and my program should be written to deal with any of the possible return codes from the 'call'.  If my program does NOT include programmatic means of dealing with the potential failure conditions for that type of call, the program will fail, with an Unhandled Exception.
 
The fact that your situation has Unhandled Exception failures in VCC means that VCC coding is deficient in dealing with some error conditions.
 
 
Based on all of the above, in my opinion this thread of yours is WAY off base - you are claiming things that are simply not true.  Your thread title is false, unfair, and potentially damaging to Cakewalk sales.
 
I would urge you to give the Cakewalk and Slate folks opportunity to dig into this and get the issues resolved.  They do seem to be actively working on it, even if it is taking some measure of time.  Just hang in there and try not to let the frustration get to you.  Is it possible that rolling back to X3b might help with this situation?  (might be worth a shot).
 
Bob Bone
 

Hi Bob, point made. I am sure that you are aware that the forum posts scroll down very quickly, and I did miss Dan's reply from a week ago, which I pointed out earlier in this thread. I will back off for now and hope for the best.
 
I still consider Sonar my DAW of choice -  hopefully it will stay that way.

+1
 
Bottom line is the "solution" can only be found from CW and Slate talking to each other. Either one talking to us will never close the gap. I truly understand your frustration. But when the bakers chime in on a thread, it is a good guess to assume is it is important to them.

I hate being "that guy" but I must be the odd man out here as I've never had a Slate plugin crash Sonar on project load. And we're talking a lot of instances of VCC and VTM in my projects. To further frustrate things, our systems aren't all that dissimilar either (Win 7 x64, x64 version of Sonar, RME Audio Interface, i7...)

@LJB - no sweat - I know you were/are frustrated with the situation.
 
Just hang in there - they are indeed working the issues.
 
In which Sonar release have these issues cropped up?
 
I am just wondering if maybe using a version prior to when the problems started would allow you to continue working on those projects, while waiting for some sort of resolution to the actual issues.
 
So, if you have any time, could you save a copy of the entire project folder for one of these projects, and then try to find a version of Sonar that allows these projects to open?  Perhaps X2, X2a, X3a, or X3b?
 
If you wanted to try to go through the exercise of finding a workable version, please post back if you want assistance with putting together some steps to accomplish that, and I will try to help you work through the process. (if at all needed or wanted).
 
Even though performing the above would result in some loss of new functionality, if you hadn't used any of the new features from the most current one you are using, then it shouldn't cause any grief, as far as I can tell.  (you would not lose anything in any case, because you made backup of the project, so even if it all fell flat on its face, your original project would be intact).
 
Bob Bone