dang double post

dang double post...
 

haha this thread is so funny!! hehe :)

O. K. Funny.
As someone who has never posted a bug on the forum, however, I do object to the characterization of those who do as morons. If you have ever spent an hour or so consulting documentation, trying useless sequences of commands, checking your hardware and software for nothing, and trying to figure out how everyone else gets something to work while you seem to be the only idiot in the world, you will have an appreciation for the usefulness of the would be "rock stars" who post about bugs. If the beta team were going to catch all the bugs, that would be fine. But if some get through, it is very very useful to have them acknowledged before many of us tear out our hair or tear up our installations in a vain attempt to fix something that we have no control over.
 
I have repeatedly called for an easily searchable, "known issues" (aka bug) list in the Sonar knowledge base that would make it easier to find these problems. Such a list would be a potential disincentive to buy Cakewalk products, and would require some significant amount of maintenance, but would save users a great deal of time and frustration. But even before a bug report should be submitted to Cakewalk, the ability to confirm that is not  just a glitch with a single user's installation by asking other users on this forum to confirm it can save users and the support staff a lot of time and trouble.

slartabartfast
O. K. Funny.
As someone who has never posted a bug on the forum, however, I do object to the characterization of those who do as morons...

I thought it would be obvious the whole thing was tongue-in-cheek, but I must admit, those people that HAVE to be first to post a bug list do really annoy me - it's the race to post the first bugs within minutes of release I find comical.
 
Posting about bugs and how they affect you and maybe even possible work-arounds is a completely valid exercise and one of the reasons for the forum.  I have no problem with that.  I have posted about the bugs that cause me grief too.  It just sometimes looks like a bunch of primary school kids fighting to be at the front of the queue at times.
 
Just thought I'd have some fun with it - certainly didn't intend to offend you.  That said, I'm not apologising for my post - just explaining the reason for it.

If it was scowling, that monkey would look a bit like my ex-wife.
 
Alex - you get a giant gold star for that bug report.  (I just watched a show yesterday on flying cars, too)
 
Bob Bone

@slartabartfast, 
 
Alex had been maintaining such a list in this forum, pretty recently, and several folks have added their current outstanding issues to it.
 
Cakewalk has not released any such list, for various reasons, but perhaps this one that Alex made could be beneficial to you and others.
 
Bob Bone
 

> but I must admit, those people that HAVE to be first to post a bug list do really annoy me - it's the race to post the first bugs within minutes of release I find comical.
 
The bug list started about a week after X3D came out. It was a lot of hard work for the first month and now bugs are just tricking in. Most of the bugs listed are legacy I suspect.
 
Actually it's really important to post new bugs just as soon as possible esp after release. You will notice Cake's forums activity shoots right up after a release; that is no coincidence, for they will be worried (as all software developers are) that their release is going well. Secondly other members of the forums will want to know if the release is reliable and will be monitoring the forums, some people will wait 2 to 4 weeks (very sensible IMHO) until it's been shown to be stable, and they need feedback from the community. I would not regard this activity as a race, however if it were regarded as a race it would be more helpful then unhelpful! (although I couldn't care less personally).
 
BTW whilst I maintain a record and try to verify issues, Jlien X is doing a lot of work here identifying and writing up the bugs here, , he is doing an excellent job, for free, and he should be commended. Maybe one day he will want to reveal what is under his mask.
 
When X3E is released we will need to find out if the the issues posted on my bug thread are actually fixed, it would be nice if people could attempt to validate the issues on the buglist to see if they are actually fixed or not in X3E regardless of what the documentation says (call it regression testing if you like). Anyway I'll try and attempt to rally troops nearer the time, I suspect it will be a big turn off for some (happy to respect their opinion) but some people may get what we are trying to do here and realise it could be of benefit to them in the long term.
 
Cake will of course have tested the patch, but there's nothing like extra testing.
As far as being a beta product tester is concerned, I don't want to sign a NDA. There are always more bugs in beta, which means a lot of work, and for something like that I would need to get paid. I'm holding out hopes for a free copy of X4 Pro upgrade though as I suspect we've contributed more than most beta teams, but these are just fantasies !

Cheers....

Hi Alex,
 
Your current bug list is awesome..  Funny is that if you do log a bug report, there is no way you can see how it is progressing...  I just tried to look up the bug I logged and nothing comes up, even when I enter the bug code and my email address...
 
Usually (correct me if I'm wrong) once the patch is released it comes with a list of the fixes and new features, take a look at x3d patch fix list and features in http://www.cakewalk.com/support/kb/reader.aspx/2007013355
 

Yes Jimmy indeed there is a list, however there's no harm in people double checking and confirming their issue (or other people issues) are actually fixed (or not), and the other reason is that if there are any new bugs to be found along the way (because the bug fix might be buggy itself) , they would be likely to find them. It is called regression
testing.... Cake will have done most of this of course, but there's no such thing as "enough testing"... and I want to see what is actually fixed in my list, not what Cake says is fixed (which of course should be the same in theory).
 
As far is progression of issues is concerned, I don't really care about that too much I trust Cake's internal systems, but when a bug is not reproducible at their end all communication is totally cut off. Issues cannot be reopened for instance or debated about. It would be better of course if Cake published a list of known bugs then we wouldn't need to maintain a list (their list is probably far more accurate and extensive than mine) like open source software. I doubt that will happen (I can't argue here, they own it, they do what is best for them).
 
Cheers...