With the time you invested in writing this thread and following it, you could have called contacted them with the info they want.  Am i missing something? Yuo are hear for other reasons, just to complain probably.

 a program does not work in the way a reasonable user would expect, to every vendor except Cakewalk, that is a bug. Well-designed software should not have "odd" behaviors, and Sonar's full of them.

FYI, Every program has bugs. Name me one DAW that doesn't have a bug. You cannot, because they all have bugs. LOL

I could be wrong, but I think in most cases they are not able to reproduce a problem as described, and are referring it to Support either to resolve the user/usability/configuration issue or to clarify the steps that expose an actual  bug.
 
That said, I was able to easily reproduce an issue a couple days ago with another user's project submitted with a bug that was incorrectly referred back to Support. So that does happen, but I think you have to give the Bakers the benefit of the doubt that it's just garden-variety mistake/misunderstanding if it actually is a bug, or that you might actually be mistaken about that, yourself, or haven't sufficiently clarified the conditions that reliably reproduce the bug. This happens a lot as many bugs are dependent on a particular project or content or settings or 3rd-party plugins.
 
In any case, I'd be interested to see what was submitted in this particular case.

It means we think we can help with the reported issue and would like to assist directly. There's no need to read into it any more than that. It doesn't have to be an argument. We have a technical support team for assisting with issues like what was reported. This is explained multiple times in the form.

One of the really wonderful things about CW are its support people. I have never in all these years had a problem interacting with them. Its always been a pleasant time spent with them. I find this thread obnoxious in its ridiculous assumptions.   

I don't understand...
If you've been a beta tester for 3 year then you already know the process.
 
I agree that the bug submission form is a major pain and when you're already frustrated it does nothing to change that.
But having been on the other side of the coin - getting bug reports that are missing critical information are a waste of everyone's time.
 
Sorry to hear that you're having problems, hope you can get them ironed out. 

One of my reported issues just got "contact tech support" status assigned today. No problem with that. Yet living in a different part of the world doesn't give you access to phone support anyway - so it's got to be email. No problem with that, either.
It's just strange that the issue is bounced back to you rather than just handed straight over to support. In my case it means providing the infos about the troubles yet again via email ... and then sit back and wait ... would be much easier if this just ended up in a support queue ...
 
 

I think his point is.... If cakewalk have asked me to contact them because they think they can help, why haven't they just contacted me with the initial steps to help solve it to start with..

Or should I get my coat? ;-)

Yevster,
 
I understand your frustration.  Filling out a bug report is a major workflow-killer!  "Contact tech support" feels like time wasted (you just DID contact tech support).  You then have to make new contact and re-describe everything.
 
But...I think you're being overly-stubborn.  You took the time to post this thread and reply to it several times already.  With a fraction of this energy you could've already contacted tech support.  Did they specifically say "call"?  I assume you could just email them.
 
In the meantime, you could use the forum to try to resolve or verify your issue.  Best of luck!

post the recipe here and the cwbr #

I would have just emailed tech support and told them how silly i thought it was to send Cakewalk the same info twice.  That's probably more likely to get them to see your point than the passive-aggressive act of wasting even more time complaining to peers on a board.