X1b update list questions

I'm just curious if any of the Bakers happen to read this, what their take would be? I swear this is not meant to cause any conflicts, I'm seriously curious about this if you wouldn't mind shedding some light on it for me? I just hope I word this the right way as it's honestly not meant to be negative at all.
 
First off, before I say a word...thanks to your guys for keeping us updated about all this stuff that is going on. I think that is an awesome thing to do as well as show all the things that are being fixed. With stuff like that being posted, I really don't care when the update comes out....at least we know how thorough this thing is going to be and that's all any of us can ask for.
 
But back to my questions. If you are one of the guys that came up with the X1 concept that may have pushed this to the suits within the company, when you look at that long list of stuff that's been posted, how does that make you feel as the guy that initiated or created X1?
 
Do you feel "wow, though we all know this is ground-breaking software, we maybe should have kept it under wraps and tested it a bit longer"?
 
Or do you feel "sheesh, we had the best of intentions and though the software does work for some people, it pains us to see all the things that were missed and are being fixed here"?
 
Granted, I fully respect that you guys are fixing all this stuff and know there will always be growing pains when you release something as complex as X1. But with a list like that being posted, how does it make you feel to be a developer? Do you feel someone may have messed up somewhere?
 
Do you have any regrets or things you would have done differently?
 
Were calls made that went against you to where you had to do what you were told in certain instances that you can mention?
 
Did you guys just run out of time?
 
Were there lists of things that you knew were wrong before release?
 
If so, why do things get released if they are not quite ready and you know about them?
 
Are there situations in which there are a certain amount of bugs allowed to be present in a release? If so, how many and who makes that call?
 
I'm really curious about this stuff just for my own head. Do you feel a bit sad when you guys look at that list? I know that your first answer will probably be "when we look at that list, we see progress and know that the things that are not working properly will be working properly."
 
But if you put yourself in another place....or think of us that are loyal customers, do you look at that list and ever say "poor people...I feel bad about this, but no worries, once we fix this, we're gonna rock your world"? I'm just curious as to what you guys think about when you don't have your Cakewalk outfits on...though it may be impossible to separate that since you are soo close to all of this.
 
At any rate, thanks for working on this stuff for us and I must say that after reading that list, I'm feeling very confident about X1b and look forward to using it. As much as I have a few issues with it right now, I'd be lying to you if I said I could put it down. I tried to shelve it for a while due to my little annoying things I have going on, but it seems to open up all by itself and I'm still enjoying it regardless of my issues. :)  

Definitely unintentional, twisted and honestly out of curiosity. I have admitted my frustration with X1 as postively and professionally as I could in the past. So I'm definitely not trying to hide any frustration...but honest when I tell you, it's not meant to be in this post. I'm just curious about this stuff because I'm working with a plugin company that is about to release a guitar sim. It is in no way as powerful or complex as X1, but there are situations I am faced with that are in ways compared to this. We have something that is very new and groundbreaking in the works and there are some bugs. We've went through the pains of hell to hold up on releasing this thing backing it up nearly 2 years. So in reality, some of the questions I asked help me to make decisions in my own life as well as my curiosity about X1. I don't think the Bakers owe anyone an apology, but I do wonder what may go on in their minds...that's all bro...honest. :)

No, you're totally right twisted....going back over the questions I asked, I sort of led the questions on a bit to where I can see exactly what you were saying. I appreciate you bringing it to my attention because honest when I tell ya, I had no malicious intent with any of this. :)

It's like...we sort of saw this with Sonar 8 in a sense, ya know? I just picture myself being one of the Bakers...happy as heck about this new software. When I see a list like that, in MY mind....I would feel that maybe I tipped my hat too soon? See man, I'm not in the software business, so part of this is due to my ignorance and really is more about curiosity than finger pointing. But for example, if we released this plug I'm working on and it had a list of fixes like that, I myself would feel like I didn't do my job. I'm not saying the Bakers didn't, I'm speaking for myself, know what I mean?

It's like, say we have the new "Twisted" DAW you just built. You did everything in your power to make it as good as you could, you had your beta guys all lined up and in your mind, you did what you were supposed to do. What happens when you release your DAW to the world and you get enough feedback reports to present a list like what we see? You the creator...when you see that, what goes through your mind? Maybe I should delete my original post and word it like that. LOL! Thanks for your insight man, much appreciated. :)

Thanks Charlie, I just hope people don't take them the wrong way. LOL! I should have just posted a video so people could see the tone of voice and facial expressions. :)

Basics of the software industry as I know....

Determine the scope (upgrade, new build). Based on the scope, budgets are calculated. Develop timelines for developing, testing, etc.

Depending on whether the company is public or private is how long the leash is for delays. Public companies tend to be worse IMO, whereas private companies with good cash-flow aren't under the outside scrutiny of the stock market.

Those things and more set things up, and it can go off the rails in numerous places. I've found outsourcing to people that don't understand  the industry (in this case, music software) isn't as efficient as some proclaim and burden the Project Managers or Team Leads an ungodly amount. And the when the lost/wasted man hours start snowballing ...oh man.

Id be curious of the Cakewalk process, and how the bug list was as comprehensive as it is (just going by Zyler's thread).

I think the next paid update should be free for early adopters of X1. Basically anyone who purchased it prior to x1b's launch date should go to a like for like upgrade to x2 when it launches at no cost.

Danny,

Excellent questions posed. Its understandable if your frustrations come out in your post and you should in no way apologize.

I have programmed quite a bit of multimedia and web applications and had many issues with Alpha and Beta releases, but nothing that even comes close to the list of current fixes. I try my hardest to make sure the client has the least amount of issues with any of my developments. If not I worry about losing them as clients. I think if my applications/developments had a list that long after a release to the public, I'd be out on my keister.

With that being said, I hope that this X1 release is not indicative of software releases to come from Cakewalk. If so, it will be sad to see them go.

Lately I've only use Sonar for voice over recording, but do the occasional songwriter demo or musical artist. Imagine my suprise to find out I couldn't even do a quick v-vocal fix on a rough vocal take. Can't imagine what you all who record bands are dealing with. I suppose just using 8.5 for now.

Anyway, that's my rant. I sure do hope they get the X1b patch put up soon.

Again, great post Danny. Thought-provoking for all the folks at Cakewalk.

Wally