vintagevibe
mmorgan
Probably damn near the true numbers there Glen.
Agree with this and with Glenn's numbers.
I write software and I also have to support it. The software I write has full error trapping that can tell me which function call had the error and what the error was. Those are errors and/or bugs. I also do a lot of verification that users have supplied the correct information or that the information I need to perform the task at hand is available. If it isn't I throw my own error and my error handler can determine whether it was a system error or a bit of information that I need to inform the user that something is missing.
Can't tell you how many times a user has told me that there was a bug/error message. When I follow up on it and ask them what the error was they "don't remember". But I log all of my applications error 'messaging' and when I look it up I'll see something along the lines of "Last Name is a required field. Please fill out all required fields and then click the Save button." That isn't a bug, that is the system trying to inform the user that they haven't done something they need to.
This is not to say that problems don't exist, they do. And I suspect I'm not the only person coding who really strives to eliminate bugs. However, as Glenn so correctly states, most of the time it is not a 'bug' - it is a misunderstanding on the users part. And for what it is worth: I changed my sampling rate a few months back and have been bedeviled by on ongoing series of 'bugs' - generally resulting in GSOD followed by BSOD. All of which had a logical and easily correctable solution once I understood where the problem was.
Regards,
Tools not working as per the manual = bug.
Inability to drag/scroll in the play list = bug.
Keyboard shortcut in playlist (E) not working and no way to assign it = bug.
Drum map manger inserting another drum map name in the save window after saving = bug.
When saving a synth preset Sonar adds another .fxp for every save giving synthpatch.fxp.fxp.fxp.fxp.fxp after multiple saves = bug.
I could go on but there are many real bugs in X2 ... or perhaps these are all by design and Cakewalk has the worst application designers in the industry.
im sure you can do better than this.
like which tool(s) are you speaking of ?
what is a playlist ?
I know your upset, but think about, insulting cakewalk employee's isn't going to fix your issues man.
I can tell by your sig that this is really upsetting you. ( "programers..tech support...exc." ).
every software out there has some failures to it. every single one.
ive used other daws as well and im sure you have as well, you know others have issues too.
I think its because you like sonar and that's why your so upset.
because if you didn't, you would be wasting your time here.
I agree there are some things id like to see bettered in the next version, but surely you can appreciate this version ?
if we could rewind 10 years ago, we would die to be using a daw like this..and all these little things, issues, we would simply blow them off and move on because we would just chalk them up as part of the price we pay to have this technology we would be happy.
I can live with these things, its the real crashes and show stoppers or repeated failures in a process that I cant put up with.
and ill be the first to post them as I have before when x1 came out. it was a nightmare.
but once the first patch rolled out, it got better.
this release was nothing like x1 (im sure you know).
anyway, I hope you hang in there, I hope things get better for you.
and here's hoping what ever the next thing we see makes you happy.
good luck vibe.
have this technology.