ugp
...what about everyone sending a request to support under the submit a feature request:
cakewalk.com/support/contact/featurerequest.aspx
 
I'm not talking about everyone sending multiple request or anything malicious, just everyone sending a request for the "b" update.

But what would your reason be for this request?
 
If you want a specific bug fixed, or a new feature added, the I agree, that's the correct way to proceed. But I really don't expect they'd take much notice of a request for "X2b". It doesn't make any sense without some sort of context.
 
 

ugp
So I've heard that they don't really pay attention to the forum...

 
I seriously doubt this is true. They might stipulate that the forum is not the correct place to officially contact Cakewalk, but you can bet your bottom dollar that they read it regularly - maybe not to research specific problems (although they do occasionally step in to help with such posts), but certainly to pick up on general feelings and 'hot' topics.
 
Seriously, if you don't think they know about the current unease in here about the lack of an update, or more accurately the lack of news about an update, then I'd respectfully suggest that you are mistaken.
 
And if they don't read the forums, and take note of what is being said in here, then they are, in my opinion, missing out on an enormous chance to hook into a massive, on-going market research opportunity. And all for the price of a users' forum.
 
 

Don't you get it: this is just another Herman Munster temper tantrum. "I want it, I want it, I want it!" as he stomps his feet , the whole house shakes, and the ceiling crashes in.  

For example; The frequent forum comments about the color choices available in SONAR X that do not actually work probably inspired this subtle piece of Cakewalk humor:
 

 
If you can't get it done... you might as well have fun. :-)
 
 

daveny5
Don't you get it: this is just another Herman Munster temper tantrum. "I want it, I want it, I want it!" as he stomps his feet , the whole house shakes, and the ceiling crashes in.  

 

 Dave, it's not often that I disagree with you....
 
But the OP paid for his software licence and he's got every right to say what he wants about it, or his intentions for that matter. He's got the same right as someone else who might want to lavish praise on SONAR and express their intention to stay loyal to Cakewalk.
 
In either scenario, and providing nobody strays outside the TOS, I can't see a problem with this. And when push comes to shove, it's up to Cakewalk to decide whether or not such posts and threads (and their creators) are permitted to remain in the forum.
 
 

I actually think the reason people say 'I'm off' is in hope that something comes of it. Someone somewhere sits up and says 'stop - don't - we still want you'.
It never happens unfortunately and in my experience you're better just to do it.
 
At the moment I have a foot in both camps. C7 and X2.
 
IMHO C7 trumps X2 in pretty much every department - no doubt Cakewalk recognise this and I think it explains their absence as they busy themselves with X3 or whatever. Hopefully something cool is around the corner and I personally cant wait for the next version to tempt me back
 
Applying Occam's razor, the alternative scenario is Roland have bought Cakewalk for skilled people and core technology  - Greg is gone, some of the key guys like Brandon have been Borg'd into Roland. It could be they have little interest in developing a flagship pro DAW anymore - at least not in any serious way. Music Creator anyone.
 
In the absence of any information from Cakewalk - who knows?!

I think the most of  "happy w x2a " users are not working in industry. Maybe these little issues are not a big deal for them.  But trust me i could loose my client and can not pay  my  flat rents  just because of a single crash. So every single bug are potential troubles for my business.  That's why i'm coming here and looking for X2b update everyday. Thats why I am impatient. Please  understand my/our situation.
 
ahh also sorry for my English.

I can see why some would do this ...why the issue?
 
I may not be a power user here but I've had enough glitchy things happen that I, too, sometimes will go off looking elsewhere....

The not-so-obvious thing that is ethically challenging to me, and we know there's not much of a way around it is this with Cakewalk: Cakewalk sells X2, knowing it has bugs, but doesn't communicate those open bugs to the customers, except when the customer discovers them and calls support. I have a problem with that.
 
Is this unlike other DAW makers? Probably not, but such a list is something other more highly competitive companies companies provide to logged in customers to help limit the number of support calls and/or frustrations. 
 
Take a note from Cisco Systems Inc.. for example. Every new code release (incremental, btw) has a list of open issues and issues resolved. The Issues resolved are just so, but the open issues are routinely updated so that customers can decide whether to update or not.
 
In the case of X2, had Cakewalk been able to offer routine patches or updates (minor versions) with an open caveat or issues list, we'd all be much happier. The process in use today by the DAW makers is grossly outdated, and the only company successful (albeit failing as of late) at doing things in secret is Apple Corp. It's a dying strategy, and anyone who follows it loses in the end. Even Microsoft gets that.
 

Patches come with a list of fixes on the website/download page.
 
The readme installed with SONAR (and updated with patches) file carries a number of issues and workarounds.
 
Maybe not totally comprehensive, but to say it doesn't exist is simply not true.

KPerry
Patches come with a list of fixes on the website/download page.
 
The readme installed with SONAR (and updated with patches) file carries a number of issues and workarounds.
 
Maybe not totally comprehensive, but to say it doesn't exist is simply not true.

Sorry, my point isn't fully understood perhaps. Sonar is SELLING a known bug or two. Those bugs are NOT listed on the site before the purchase is made. So, any README files are a surprise, which is how OpenSource code works, typically. Bought software does, too, but my point is that Cakewalk doesn't take the initiative to let you know up front any open issues with a patch or platform level (X1, X2, etc.). They only let you know what was fixed.
 
Other companies do. Maybe not DAW companies, but by perusing the forum, you can size up the frustration this strategy exposes. It's ok to admit there are open issues. To be open about such things lets the customer know that the company doesn't have something sinister or negative to hide. To be tight-lipped sends the message to the customers that the company has plans that do not necessarily address the open issues. So, my ethical challenge is, and this is nothing new, if you willingly sell a product knowing there are a few bugs, hoping the customer will never experience them, are they listed in the README or on the website? Are they being addressed or will they only be disclosed as known bugs on a support call? If the latter you're bound to ask, "When is the patch/fix going to be available? What would be the support agent's response to that question?"
 
How would that discovery make you feel as a new Cakewalk customer?
 
"Am I wrong?" -Walter
"You're not wrong, Walter, you're just an a--hole!" -Dude