For the record, I too will be buying X2 right out the gate.

 
Yeah, I probably will too.   I like a lot of what I've seen in the preview, and am also curious to try out automation lanes to see how they work.  I don't have many outright issues with automation, more annoyances.  So I'm looking forward to seeing these changes!
 

scook


Never in the history of SONAR has CW ever patched an older version once a new version has been announced. Of course that does not mean it will not happen but I suspect the staff will be busy addressing issues introduced by X2 in addition to problems grandfather in and then there is the ever increasing list of feature requests for X3 just a year or so away.

I'm not an expert on how this stuff is done, but if they fix some of the bugs from X1 in X2, couldn't they then put those fixes into a separate patch for the X1 users to download and install...? Or is that dumb?

couldn't they then put those fixes into a separate patch for the X1 users to download and install.

 
I'd imagine it depends on how the fixes are implemented; e.g., do they depend on changes unique to X2?  I've worked for a software company for almost 15 years and have come across this situation a number of times.  It's quite often that fixes are connected to other changes in a newer version that make it impossible (or at least impractical) to port back to an older build.
 
Whether this is the case with SONAR...  no idea!   But I wouldn't doubt that a good potion fall into this category.  There's also the financial/time factor - having development and QA working on a previous version vs. the new version which now represents the flagship product.  A pretty decent sized staff is usually needed to do both.
 

Anything is possible, but if the past is any indication of how they will act in the future, do not count on changes being made to previous versions of their products once a new product announcement has been made.

No its not dumb pjfarr, but in doing it this way they would do two things to themselves...

1. Take people away from working on the X2 update, for a product that is at its life cycle end point monetarily speaking.

2. Make the X2 update less nifty for us to purchase since fixing X1 with these new fixes/items, meaning less money and food on the table for the bakers. They gotta eat too ya know... 


Its all about new 1's and 0's and bank account amounts now, for future X's of course... 

@ Steve, I even have my wallpaper loaded up and waiting lol.



Mike

@ Steve, I even have my wallpaper loaded up and waiting lol.

 
Ha!   
 
OK, maybe I haven't gone that far, but I am looking forward to X2 none the less.  
 

mikey

1. Take people away from working on the X2 update, for a product that is at its life cycle end point monetarily speaking.

2. Make the X2 update less nifty for us to purchase since fixing X1 with these new fixes/items, meaning less money and food on the table for the bakers. They gotta eat too ya know... 


Its all about new 1's and 0's and bank account amounts now, for future X's of course... 

Thanks Mikey! I hear ya, but just for clarity:
 
1. It wouldn't be taking any staff away from X2 development since the X1 bugs would be worked out as part of the development of X2, no? I'm just saying couldn't they then take that batch of fixed code and make another X1 patch from it (although another poster did explain why that wouldn't necessarily be possible if the fixed code incorporated new coding that's specific to X2 that X1 wouldn't understand—or something).
 
2. I don't think it would make X2 any "less nifty" to any potential X2 customers since there's always the new bells and whistles and new UI enhancements every new version entices previous users with that are unrelated to important fixes.
 
And even then there's no guarantee that certain bugs will even BE fixed in X2, since there are still some bugs following each new version that have been lurking in the code since the Pro Audio days.
 
Look how long Microsoft supported XP, even right through development and release of Vista and Windows 7. In fact I think I read support for XP won't end until 2014.

Check CW history. Have they ever provided a
maintenance release once they had the latest 
releae or sale?

I don't think so but maybe somrone can prove me wrong
as I skipped a few versions along the way.

Mario

There sure as hell NEEDS to be one. X1 d killed fastbaouncing of timecode based plugins (antare, melodyne, gtr rig, waves) Takes more than twice as long to bounce everything. Still can't drag a midi effect from clip to clip or clip to bin. Can't delete a clip with a midi effect on it. Still have reberb tails pasted on the beginnings of song exports. Half the time transients are detected that aren't even there (every quarternote). Have to revert to 8.53 for reliable transient detection. Plugin delay compensation problems. Cakewalk needs to take responsibility for what THEY BROKE in X1D. I've been writing and calling since March about all of the screwed up issues. I officially stopped recommending Sonar as of X1. Customer service sucks!! When I called and asked when Fastbouncing timecode plugins be fixed, They said, 'it's fixed in X2'. I said, 'Oh great, when are you fixing it in X1?' They told me that they weren't fixing X1. Complete --BULL**** There's been plenty of time to take care of the customers that only want what they've already paid for... a working product, Not a substandard piece of crap. Continuing down a path of COMPLETE disregard of the professional customers WILL result in the DOWNFALL and DEMISE of CAKEWALK.