bugfix list?

i know it's early days but is there, or will there be, a list of bugs fixed? tia

+1 ..........yes, bug fixes and also the "under the hood" improvements to the core program! This would sway me more than anything else as to whether to upgrade or not.
 
Cheers,
 
Billy Buck

Well from Disc pressing to download there is already an X3a....

+Bapu

A fix log, while good sounding, isn't always a great indicator between version cycles. There's a few reasons for this:

1) Some things get fixed without their reports getting closed. This has to do with the fact that sometimes when you fix something or implement a new feature you inadvertently fix other things. It's not until you backtrack and go through the logs on downtime that you'll find it fixed and can close it out.
2) We get duplicate reports either from the Beta team, end users, or internally. Sometimes we'll close out something a few times. On the face of it you'll see 5 fixes, but it was really 1.
3) Sometimes things change so much the old issues will simply not exist anymore.
4) Sometimes devs find and fix things before they are ever logged.
5) There's usually some pretty bad issues in development, like CRASH CRASH CRASH. Since the user never sees this there's not much need to report it. If anything it may cause more alarm and give 'ammo' to trolls.
 
As you can see there's lots that are at play. I believe there was around 100 customer reported or talked about issues fixed this cycle. Though I suspect that number is actually higher. I think we'll be able to get lists out in point releases though as that's a bit more manageable.
 

cclarry

backwoods
That's even faster than Steinberg updates. Shows they care right 

or they goofed....one or the other...hopefully the former and not the later...

 
Nope, we just wanted to keep busy and continue to improve the product. If you don't set a deadline for something nothing gets accomplished.

bapu
In other words only installed users will actually know what has been fixed for now (if they know what they are looking for)?
 
I was a VP of Software Developemnt for a highly complex ERP system for five years. We had a bug tracking system in 1982 that told customers by tracking number what bug had been fixed and published it when we delivered a major or minor release.
 
I'm pretty sure no one want to see anything from CW's #5 as that is ONLY development rated. But really, with all due respect, your explanation of being unable to tell the customer base what was fixed is straight out of the 1960s unless your tracking system is entirely paper based and then I'd say the 1940s.
 
Nuff said. I will not harp on this.

The CWBRN public system is separate from our internal system. I think Ryan has mentioned this multiple times. This is to keep out junk reports and 'Contact Supports' out of the dev system.

+1 to the OP and Billy Buck.  I'll be making my buy decision based not on the obvious VST3 changes and added plugs, but on improvements and fixes for all the more subtle workflow issues.  Need the list.  Make that +3.

noels blog goes some way towards discussing such horrors as bugs fixed :-)

Completely agree. 
 
I honestly would have considered paying for a pure bug fix/maintenance release to X2.  I cannot, however, jump to a new version with new bugs when the previous version was abandoned since 2012.
 
Not every update needs to be a marketing extravaganza.  The product needs bare bones maintenance every release.  The experience with X2 this year was off-putting to say the least.

+ 100 over here! An "under the hood / bug fixes" thread or blog post would be very much appreciated. I understand that sometimes companies might have a little trouble with "publicly admitting" troubles with their products and/or centralizing  those somewhere easily accessible... but it's just how it this with software, so why not embrace it? So If fellow Sonarites and / or fellow bakers could participate in ONE common thread to gather all of the bits and pieces ( like... "oh yeah, we fixed that by the way"...) it'll be greatly appreciated by a lot of people I'm sure.
 
So far, I'm thrilled and excited of what I could gather up so far regarding X3. But, I for one have enough plugins already... (heck... there's a new reverb with a lot of SONAR iterations...) SOooooo... i'm trying hard to focus on the DAW's improvements themselves instead of "included and flashing new toys", hence my interest in an "Under the hood" thread...
 
That being said: have I went "WOW ! All these goodies for about 150$ ??! WHERE DO I SIGN?? WoooHooo !!!" (happy customer bouncing on his head out of pure joy over here...)
 
... Hell yeah I did...

The $49 X3 upgrade http://www.store.cakewalk...ductid=10-CXSR3.00-30E

It is the basic version of X3 available for any Cakewalk user. There is no "Essential" version of X3. The basic version is not as restricted as the old "Essential" versions. http://www.cakewalk.com/p..cts/sonar/versions.aspx

Feels to me, that CWs approach to a formal "bugfix" list is a little Nancy Pelosi-ish.
"Pass the bill, THEN you can find out what's in it."
"Buy the upgrade, use it, THEN you can find out what has been fixed."
No thanks, I'll be waiting to see how all this shakes out. It's not the money, as I have spent thousands on plugs, VSTis, and gear. I got burned with X1 even with the updates. Burned again with X2 with only one update, then abandoned. Why would I try again? I think it is unethical to sell a product with known issues, fix a few and then abandon the users of that product in order to generate revenue.
I find the silence on a couple of issues here deafening. A bugfix list being one and staff view being another. Did the bakers totally forget staff view was even in there? Apparently not even one improvement.

jatoth, way to sneak politics into the convo lol