X1b Update March 9th!!!! Look up!!!!!

http://forum.cakewalk.com/tm.aspx?m=2222611

HumbleNoise


Thanks ping,

I see a bug fix that's been er... bugging me.

Lol!!!!!!!!!!!!!!!!!!!

Heh, yeah - it looks like a whole new re-write ;)
 
I don't see the issue of Bus Envelopes getting completely deleted when being pasted yet.
 
That concerns me.  The rest looks like a lot of work has gone into X1B (as should have gone into X1).
 
So we'll see.
 
 

brundlefly


Wow, I log on to check status for the first time in a week or more, and I miss the update by a couple of minutes. Thanks for the heads up.
 
X1b is looking better all the time.
 
Really staggering that more of this stuff wasn't caught and fixed in beta, though. Especially the things that were carryovers from previous releases.
 
 

Yeah, that's the part that truly bothers me.   So much of what's on the list either was caught by QA and their beta testers and ignored by CW for the sake or profit only, or ... well, I can't figure out how else that stuff (most of it at least) could have gotten through.
 
I'm also wondering how it is many of the users on this forum claiming they have no issues actually use the program.  It seems like it'd be hard not to run into a bunch of those with even a casual use.
 
But I still would like to be able to use X1 seriously, so I'm happy to see all those fixes regardless.
 

 

SilkTone


The vast majority of those are non-critical bugs. I really don't understand why these bugs weren't triaged by severity, and then fixed in that order. Then CW could have released a patch a long time ago already so that those of us that can't even use X1 in its current state can at least start using it. That is how real software development works, especially if your current flagship product is DOA. It has been over 3 months now and we are stuck waiting while CW wastes time fixing a huge list of trivial bugs.

To me X1 is the poster child of bad decisions. Even after the severity of a lot of the bad decisions CW has made with X1 has become known, they still choose to continue making bad decisions. Really disappointing.

I haven't quantified what is/isn't critical bugs in that list for myself, nor would I assume it to be the same (ie, critical/non-critical) for all users, but I would agree with your statements otherwise -- especially the part about bad decisions.
 

SilkTone


Well what I mean by critical/trivial is anything that has the word "crash" in it, or anything that causes important functionality to stop working altogether with no known work-around is critical.

Things like wrong tooltips, overlapping text, or pretty much most cosmetic bugs are trivial. I can guarantee you that the reason many of us can't use X1 now is not because of cosmetic bugs or things like "can't maximize the busses".

Yes, I generally agree.   And it's funny how some of those "non-critical" things can add up and create an annoyance that still detracts from the creative workflow.   Of course there have to be degrees for such things, but they still matter at the end of the day.
 
 

I have to agree here. With such a long list of bug fixes why not release an interim update? I implement a financial software package in my day job. There are bug fixes released by vendors all the time. Usually monthly. Some we choose to install at customers, some we wait on based on the customers needs. We decide with the customer what is best.

It is great Cakewalk wants the software to be as complete as possible but the reality is there are going to be more bugs anyway. Without a large group using the software you are never going to get a real picture of what users will experience.  Just my thoughts...

Crg


Thanks for posting this.

You're welcome!

I remain skeptical, however, I'm going to think positive thoughts and I'm rooting for Cake.  After all, Cake's success is our success! 

I agree.  I am rooting for Cake too.  I have enjoyed and been productive on every version Since 4.  I have even convinced a few friends to switch over.  I am looking forward to the update.

fireberd


I worked as a programmer (at NASA) and it was a different world than the current "commercial" software world. Something like this would have never been released like X1 was. 

There is a bit of difference in the criticalness of the programs' use.  Your NASA program had to ensure that your astronauts would get safely to the moon(or other destinations) and back.  X1 just has to be there to be able record us singing about "Flying to the moon".

I'm reading some of the grumbling about the large number of fixes Cakewalk is posting.  But, if my memory serves me correctly, this is the first time Cake has posted fixes before releasing an update.

First off, I'm GLAD for the large number of fixes. 

Secondly, how do we know, in comparison, how many fixes have been on previous updates?

Third(ly), is there ANYTHING some of you folks DON'T complain about?  (I bet some of you complain about the sun rising "AGAIN" every morning ... lol)

koolbass


...  (I bet some of you complain about the sun rising "AGAIN" every morning ... lol)

Yeah, what's up wit dat anyhow? 

I've seen about 1/3 of the bugs in the list that was just added, not to mention a lot of the bugs listed prior to this update. After reading how many people claim to have no issue's, I was really starting to think it was my PC. Now I know 100% for sure it's not. I'm really glad they are putting out the fix list like this because when they do, it prevents a lot of headache's for the end users because we don't have to spend time troubleshoot our PC's.

Bub.

In my experience, the size of this bug list fix is business as usual for the vast majority of commercial software. Just look at the patch release notes for the 8.5 patches, as a quick example.
Hell, I work with an ERP system that is still being updated weekly, 10 years after development of the base code was frozen (not apples & apples, but just another example). I've seen smaller lists, and I've also seen much bigger lists.

And I agree, it's just about ALL has to be because of rush-to-market. I'm in no way defending the practice, but it really is the norm.......sad, really.

As a good example of how it can/should be done, check out the bug fixes in the 1.1 patch relase notes for StarCraft II.....I think there's like 4 items, hehehe. Blizzard just does it like it should be done in that regard.........the flip side of that is, is the game's release date being pushed out constantly, literally for years. I don't think many software companies could survive that long of a cycle..........but there's got to be a happy medium to be found there somewhere