beltrom
 

As far as I know there never was an X2b?




My bad...I should have said X2a.  It seems Cake started with X3a this time, so the first update is X3b.
 
The list of fixes/updates for X3b is long...too long to have been started last week.  It looks like Cake started the X3b well before X3a was actually release.  That's a good sign, IMHO.  It shows Cake is taking updates seriously for this version.

They probably learned something from Cubase

This happens every year at about the same time. A newer version of sonar will come out and the older version doesn't get updated anymore. This has been going on for at least 13 years. Nothing has changed, so there are no surprises. This is how its been working for over a decade
 
CJ

Jim Kalinowski

beltrom


As far as I know there never was an X2b?

My bad...I should have said X2a.  It seems Cake started with X3a this time, so the first update is X3b.
 
The list of fixes/updates for X3b is long...too long to have been started last week.  It looks like Cake started the X3b well before X3a was actually release.  That's a good sign, IMHO.  It shows Cake is taking updates seriously for this version.

The original version downloaded from Cakewalk store was pre-upgraded to X3a. Those currently purchasing the DVD version will get X3. The X3b upgrade can install over either, which explains why the list is long; some are from X3a.

That's not the surprising part. The surprising part was the release of only one patch to the previous version before moving on. It doesn't follow Cakewalk's usual behavior in the past.
 
And considering the "a" patch for this new version was ready before release and the "b" patch just about done (if not already done) by release day and released a week later before anyone even had a chance to find and report problems can we really consider these maintenance updates? Seems like code clean up that would normally be done before putting out the product. Now they're already talking about a C patch. It all seems a little weird. Almost as if they preplanned it to make it look like a ton of work had been done after the initial release.
 
I mean it's great they are seemingly taking this version more seriously but to me the C patch should probably be called X3a... perhaps even Quickfix.

Beepster
That's not the surprising part. The surprising part was the release of only one patch to the previous version before moving on. It doesn't follow Cakewalk's usual behavior in the past.
 
And considering the "a" patch for this new version was ready before release and the "b" patch just about done (if not already done) by release day and released a week later before anyone even had a chance to find and report problems can we really consider these maintenance updates? Seems like code clean up that would normally be done before putting out the product. Now they're already talking about a C patch. It all seems a little weird. Almost as if they preplanned it to make it look like a ton of work had been done after the initial release.
 
I mean it's great they are seemingly taking this version more seriously but to me the C patch should probably be called X3a... perhaps even Quickfix.

Not everyone will 'start' from X3a. Initial boxed versions will contain X3 .

Yes. I understand that. It was a fix between the time the boxes got produced and the product went live. It's more like the quickfix from X2's initial release. It's purely semantics but the way things are going it will look like X3 has gotten the same level of maintenance X1 did over the first year of release in the same month when all that's happening is they are fixing/implementing stuff that probably should have been cleaned up before it went out the door. Unless the program is totally rock solid after these cleanup patches that were mostly developed before release and they actually do keep working on problems that get discovered by users we could end up with X3h or i.
 
It doesn't really matter though. It sounds like X3 is significantly more stable than X2 was which is great but it doesn't make those of us who can't or aren't willing to upgrade just yet feel any better. That's what this thread is about.

Many thanks to all of you with your good thoughts and ideas...

I know that waiting for the software is not the end of the world... And the release excitement can often mask severe issues as you all remind me...

I also know that the power I have in my DAW far exceeds anything I've had in the past.... Even working 24 track analog was a burden compared to what we now do...

I guess I'm feeling so sad because my life situation is bad and promising to get far worse before better.... It has been falling this way for a long time, but the one thing I've granted myself every year regardless of situation was the new Sonar upgrade. So I'm feeling even lower that before...

New toys? Sure they're fun, but the music I make these days doesn't really need them. I do wind up writing some different pieces each release though as I tinker with new gadgets and ideas... Mostly what it is for me is the need for improved workflow and "cures" for some of the issues plaguing my work (not a day goes by that I don't get angry about the Lanes issues, so I'm hoping that the new improvements might lift me from the constant annoyance I have with X2.... I will have to adapt to a different way of working than I have done... That much is pretty clear, but I'm hopeful that it will be better...

I don't feel I have too much time left to my musical life and everything that gets in the way of that is a major obstacle for me..

I'm just very depressed facing the loss of my way of life and this is the pinnacle of its appearance for me...

So without spending more time spreading my depression onto so many good people (all of you), I will end this post by saying that as there's nothing I can do to change anything right now and my electric is still on, I will spend today writing a new piece of music and submitting to my other disease (Peterpanitis has been mentioned by me on this forum before - I won't crow up)... The other disease is Neroism (Nero fiddled while Rome burnt and I make my music while my life crumbles from under me)... I will let the disease run rampant today and do my best not to get to angry/frustrated by X2's issues (my issues with it)...

Many thanks to all of you for your support and thoughts... I truly hope you all have a joyous day and make wonderful music with whatever tools you chose to use...

Keni

Jim Kalinowski

beltrom 

As far as I know there never was an X2b?

My bad...I should have said X2a.  It seems Cake started with X3a this time, so the first update is X3b. The list of fixes/updates for X3b is long...too long to have been started last week.  It looks like Cake started the X3b well before X3a was actually release.  That's a good sign, IMHO.  It shows Cake is taking updates seriously for this version.


Almost.... They did release X3 on DVD, but the download version had already been updated to X2a... So X3b is the third release for this version...

Keni

CJaysMusic
This happens every year at about the same time. A newer version of sonar will come out and the older version doesn't get updated anymore. This has been going on for at least 13 years. Nothing has changed, so there are no surprises. This is how its been working for over a decade CJ

Once they move on to a new release, thee are never any more fixes for the older version... <sigh>...

Keni