X1c?

Is another X1 update necessary?

Or is everything good to go until X2 in October 2011?

CW definately need to get this (X)one right and glitch free, before they even think of moving on.

I personally believe that if they just move on to X2, without sorting all the bugs in X1, they WILL lose many long term users to other DAW's.

X1 hasn't been the ray of light that CW imagined, or should that be Re-imagined.

I've thought for a long time that the "one a year" turn around, was a bit much, and at the expense of the previous version.

CW really need to "re-imagine" their product development.

I stated in an earlier post they need to make slight improvements for X1 up to the next upgrade...I am sure they are working their pants off at this stage to make sure that X2 is compliant to consumer software laws (if there is such a thing) however, if not they need to show their loyalty to its loyal fanbase and bring out X2 1) on time 2) not beta 3) working and in order. If they go for the tech touch in X2 it will be an epic fail.

I think people are becoming less and less patient in general these days and I am afraid that Cakewalk will suffer if they do not make X2 to be a polished app.

I am a hobbyist and I am not a person who is happy with unstability because money and time is tight. It is not a commodity that is in abundance. As tech gets better the demands on perfection is more apparent. I think with Iphone and Android becoming more prominent the software market needs to be on top of its game.

I think with what I have been hearing I will wait until X2 (no fancy doo dahs) just a polished app can only be good enough for me.

They should keep to this one until it works, period.

Get this one fixed!!

they need to show their loyalty to its loyal fanbase and bring out X2 1) on time 2) not beta 3) working and in order

I am not sure if this is a tripartite oxymoron or a trilemma. Arguably the "on time" part is the reason that the other issues are issues. There is no technological reason why this, or any software, has to have a "release date." Given time and resources the software can be adequately debugged to produce a product that will work out of the box for most users. Release from beta should then uncover those users with unanticipated hardware or software conflicts, which might be amenable to solutions via "updates."

The only "on time" that Cakewalk is subject to is their own need to generate income from upgrade fees (I have always suspected that the fall release was used to fund the Cakewalk Xmass bonuses), and to add features that make them look more attractive than the competition before the competition steals their loyal fans. Of course there is a real risk if the new features do not  work. I for one have never chimed in with the when-will-the-next-upgrade-be-ready crowd. I am getting to the point where I dread them.

I would like 1c, in this case, to come with an easy to use macro function. Something similar to that available in an Office Suite or Photoshop.
.CAL is far too esoteric to rapidly proceed to perform repeated tasks. Just write your own .CAL function requires the closest to a programmer.

K

Dappa1


Meaning we will forever be Beta testers for those that choose to go through the yearly turmoil of a Cakewalk debacle! Or are you happy to see a release whenever the Tax Disc runs out!

Well, the point of beta testing is to find the common problems and get user comments before the software gets a general release. Traditionally this testing is done by advanced users who are paid a fee, or given a free copy of the final product at least. In some cases the panel includes some naive beta testers i. e. people who have never used the software to determine if it is going to be comprehensible to new users. That should uncover bugs in real use situations that the developers did not foresee.

X1 has caused a lot of consternation because of new design, interface and features that are a shock/disappointment to some users of the previous version, and a revolutionary improvement to others. That is a design decision and not something that the testing process can be faulted for. The redesign naturally introduces a lot of new code, and a lot of new bugs. Cakewalk apparently did realize that this would be a problem and hence the birth of Sonar 8.5, a minor "upgrade" whose release was apparently timed to satisfy the fans who expect something new every fall, and the bean counters who depend on them. That gave them considerably more time to cook the code for X1 than they usually take with an upgrade. How much more time they would have needed to produce and test a less troublesome product is anyone's guess.

If you think you are in effect a beta tester, then you can at least console yourself that as a loyal fan you get a reduced rate on the "final" product. If you are a new user, then...

As long as there are bugs, updates should be the priority.

We shouldn't expect to see cosmetic changes, or feature changes in X1 but everything should work as listed/intended before moving on to X2.

I must admit that Sonar X1 after adding the X1b patch is not still 100 percent fixed, but the X1b patch did make a big difference in the error messages I was receiving and the pops and clicks I had with my audio interface. 

The sound is 100% better, I have not received one error message after installing the X1b patch and over four hours of using X1 with the X1b patch. I did notice some minor things that were not deal breakers for using Sonar X1, so I can overlook them for now.  So for recording music, vocals and mixing it together, Sonar is back on TRACK.


Thanks Cakewalk.

Peace

I agree with SO many of the posts in this thread.  I do hope CW is listening.

X1B is working "ok" for me so far.   I'm not blown away, but it's working at least.   There are still a number of minor annoyances (they add up though) and some bugs I'm bumping into that I thought would be resolved by now, but they're not.

I've been spending an enormous amount of time strictly in X1B since it was released with lots of editing, recording, tweaking, etc.   There are some areas that truly slow me down and that concerns me.

There's one PRV issue I think may be a bug and when I have time to focus on that, I'll submit a report to CW.

But in the meanwhile, I do hope there's a "C" soon frankly.

There will always be bugs - that's the nature of software

Is that the software equivalent of the philosophical cliche that everything is perfect just as it is? If so, then our expectations and the designers' intentions are clearly the problem.

How are we to satisfy our endless appetites, master?

Want little.

I hate the logic of putting out a new version EVERY year just BECAUSE, or just to make more dough. This is not anti-virus software. FORCING out a new version every single year will almost certainly lead to instability and sloppiness.

Just work on X1. Make it great. Give X2 a few years.