Urge for a NEW BUG thread Section on Cakewalk FORUM!

Freddie- I think its a great idea. I second this totally.

I want to upgrade to Sonar X1 but right now I just dont have the confidence to do so. Its going to take at least a Sonar X1C before I feel comfortable doing that.

By highlighting more remaining bugs as your post wants to do that would enable Cakewalk to continue to improve Sonar X1.

I reckon there are a number of cakewalk customers like me who Cakewalk could "bring in from the cold"  and get to upgrade.

I was just talking on Facebook to another Sonar customer who is staying on 8.5.3 because its stable for him but might upgrade in the summer. He mentioned crashes and stability issues as his reason for not upgrading.

These are also my concerns.

So the more bug reports the better for me if it helps Cakewalk get X1 ironed out and gives me the inner green light to upgrade.

Shouldn't it maybe be a thread section specifically for bugs that have been reported already to CW and acknowledged by them via the bug reporting system?    That way it won't get swamped with niggles and problems that can be resolved via the forum.

Thanks!


I think it can be good idea have a new BUG section here at this forum. NI has it already-

Cakewalk have needed a proper bug tracker for some time, it's not as if they're hard to come by: http://www.webresourcesde...ug-tracking-softwares/

And while we're at it a feature request manager and voting system would be great too:

http://brainstorm.ubuntu.com/

It's definitely time that they put a bit more of a toe in to the waters of community development and ownership of 'their' product.

Child

He mentioned crashes and stability issues as his reason for not upgrading. 

It's stable for me and doesn't crash either. It's also a cheap upgrade from 8.5.3. 


I like the idea of a bug section on the forum. Just so users can corroborate each others experiences for the benefit of the Cakewalk team and ultimately the Cakewalk consumers.


Someone told me with the lean manufacturing methods used by Toyota if they had a problem they shut down the whole plant until the problem was resolved. Definitely an incentive to get things sorted out. But... I think we can agree that Cakewalk has done a fine job of bug stomp9ng these last few weeks. I'm impressed with the new quickfix regime and also Sonar X1 (I think it totally kicks butt).

Bristol_Jonesey

I want to upgrade to Sonar X1 but right now I just dont have the confidence to do so. Its going to take at least a Sonar X1C before I feel comfortable doing that.

I was just talking on Facebook to another Sonar customer who is staying on 8.5.3 because its stable for him but might upgrade in the summer. He mentioned crashes and stability issues as his reason for not upgrading.

Steve, I was one of those who had insurmountable problems with X1 and X1a.

As a consequence, I've been using 8.5.3 since December as it was the only way I could get any work done.

But with the advent of X1b, and the 2 hotfixes, all of my problems seem to have disappeared - but with one caveat.

If I try to open up a project started in any other version of Sonar apart from X1 - X1 will crash.

So the moral is, only use it for brand new projects, and finish all your old stuff in 8.5

Other users might be more fortunate than me and have enjoyed the ability to open up any old projects in X1 and not get crashes.

Since adopting this strategy I have had ONE X1 crash, and that was when I attempted to drag an Fx plug from the browser into a tracks Fx bin.

It's not happened since.

funny you say this mr jonsey..because at one point this was the only way sonar would crash on me(dragging an fx from the browser to the bin.)

This is harder than one might think, against all reported issues for X1, only about 35% were true actual bugs.  The majority of reported issues can be resolved through either tech support or reading the documentation.

I'm not saying this is a bad idea - but I don't think it would serve as an accurate resource for users and it might prevent a user who needs help from posting in the right place to actually get help.

Cakewalk have needed a proper bug tracker for some time, it's not as if they're hard to come by

We actually have a very robust and flexible issue tracking system.  Just because we don't make it public doesn't mean we don't have one

Shouldn't it maybe be a thread section specifically for bugs that have been reported already to CW and acknowledged by them via the bug reporting system?

This would be the right way to do it if the forum is used IMHO.  All the forum threads won't mean a thing if it never gets reported to us.

The final problem I perceive is accuracy in reporting.  In the forum users can edit posts, change details and sometimes rant without providing any information that we can use to get to the bottom of the problem.

I'm not saying no, we'll never use the forum its not an option I just don't think its the right solution.  What if we made all verified and submitted to development bugs public and users could add their info to it, kind of like saying +1 but then without the troubles of having to go and provide all of the step by step repro info?

What if we made all verified and submitted to development bugs public and users could add their info to it, kind of like saying +1 but then without the troubles of having to go and provide all of the step by step repro info?

There are bugs that are annoying, but ultimately insignificant, like text lables not wrapping properly, that everyone will see and report.
Then there are serious bugs that may constantly crash a machine that only a few will report because only a few will be using the specific scenario that causes the crash.
 
With blind reporting the devs can only prioritize by the number of people that report bugs, so the text labling gets fixed before the serious crashing on the basis that if only 5 people report the crash out of 50,000 users then it can't be that bad can it?
 
Having a public list of reported bugs, easily visible and searchable, with the ability to "vote" for the bugs that affect you would give the devs a more accurate picture of what needs their attention the most as it would highlite issues that people may not even know they have so they can go test it.
By posting a list of ve

AND THIS GOT MOVED TO THE CH BECAUSE........????????

Because its not a product-specific question, its a discussion about a Cakewalk process

Because its not a product-specific question, its a discussion about a Cakewalk process

Yeah Right

musicman100


AND THIS GOT MOVED TO THE CH BECAUSE........????????

Because "The Willy" said so.  no more discussion is necessary when "The Willy" speaks.  right bapu?
 
back on topic - I really don't see that a separate bug subforum would really provide anything useful.  look at the chaos of the upper forum.  a bug subforum would QUICKLY devolve into something even worse than that with rants, arguing, name calling, cats living with dogs, mass hysteria...

Willy Jones [Cakewalk
]

With blind reporting the devs can only prioritize by the number of people that report bugs, so the text labling gets fixed before the serious crashing on the basis that if only 5 people report the crash out of 50,000 users then it can't be that bad can it?

We prioritize issues internally based on a number of different parameters issues that lead to data loss, crashing or project corruption have the absolute highest priority.

That being said sometimes a fix isn't always simple so we may not always have time to fix a gross bug but if something can be fixed quickly and many users are reporting it we'll try to address it.

I think the tech support and process improvements are prioritized in about the best way they can be.  IMO I believe the intent of Forums has been somewhat lost with the Owners/Moderators trying to appease users and make things easier for us using suggestions and flows from within the forums. The Moderators, bless their hearts, have blessed us with their interactions when possible and are helpful.
 
I dont know and cant imagine how many registered users utilize this site for help, not from CW but from other users,  but Im sure the number is HUGE and more help than not is received and made regardless of the site layout and how it is managed. (Things will be misplaced by users and when it interupts a clique, flags will be raised)
 
With that said, thanks again moderators for the job your doing and added support you provide outside of the tech support email and phone section.  (here)