pwalpwal
i read Kylotan as being frustrated with the "proper procedure" and that seems exacerbated by the responses here...
only anderton responded directly that 1 was fixed.

 
I did. did you ?
see my first response.
2 out of the 4 im not even going to bother.
 

pwalpwal
 no-one tried to reproduce them, even though his links all contain the info required (info that is repeatedly requested on the forum for troubleshooting)

 
ya...about that..
the title of threads are misleading.
Example: "when I click on a clip I want that clip open".
which seems to be a little twisted wouldn't you agree ?
the real issue was ""Double-clicking a drum mapped MIDI file not opening Piano Roll centred on that file"".
 
I don't mind checking things to cross reference but im not shagging around having to go back to a thread and read 6 posts down to see the bug has changed to something more trivial.
 
 

pwalpwal

Anderton
I think the most important aspect of bug fixing is the part where users provide data to create a pool of possible bugs, and that Cakewalk interacting with users and updating them on which bugs are being fixed, aren't being fixed, may be fixed, may not be fixed, etc. is less importan

i disagree with this - letting the user know one way or the other is important, otherwise, as we see, users become frustrated and then despondent, and stop reporting them

 
I think you're extrapolating a very limited data set to general behavior. There are plenty of people who report bugs, but they probably have an attitude that's more like mine. I never check back on a bug I submit, or ask to be updated on crash reports; I report a bug solely to provide data. I see Cakewalk's function as parsing, analyzing, and prioritizing that data. Once I've submitted a bug report, I don't think about it again. 
 
Users whose primary motivation in submitting bug reports is to help Cakewalk create a better program will continue to report bugs, because it's obvious that Cakewalk does fix user-reported bugs. For me, and presumably others, that's sufficient feedback. Granted, it's great when I see that a bug I reported is fixed, but for all I know it had nothing to do with my report. It could be that someone at Cakewalk found it, or 47 people reported it before me. 
 
Those who submit bug reports primarily with the hope that their particular bug will be prioritized and attended to will likely be disappointed, unless there are lots of reports about that same bug by people who find a similar degree of inconvenience, no reasonable workaround exists, and the resources required to fix the bug are commensurate with its severity. 
 

My expectation, both as a user and a developer of software, is that every bug report at least gets reviewed. It might get pushed onto the "nice to have" pile, or at the other extreme put onto the "immediate hot-fix" pile, but someone has to actually look at it to make that decision. If they're not even doing that... it's worthless.

The party line about prioritizing bugs based on frequency and severity is all well and good. But what if you have issues that don't affect a lot of people but drive you crazy? It could be system specific or the result of a conflict with other software. To me, this is where tech support should be jumping in. They could help that one-off user mitigate the effects of the problem or help users determine if it's a conflict with hardware or other software.
 
Right now tech support is under water. If it's not a problem experienced by many and tech support is booking for 2017, where does that leave the customer? Lately I feel there's too much apologizing and rationalization being done. It makes some people feel better, but not the one's with problems.
 
I'm not bashing Cakewalk, but I don't feel right about dismissing people like Kylotan as complainers. Their problems are real in their world.

Kylotan
My expectation, both as a user and a developer of software, is that every bug report at least gets reviewed. It might get pushed onto the "nice to have" pile, or at the other extreme put onto the "immediate hot-fix" pile, but someone has to actually look at it to make that decision. If they're not even doing that... it's worthless.

maybe not your requests.
but we have seen major improvements in bug fixes over the last year alone.
I have seen so many things I've called annoyances been fixed.
 
do you read the bug fixes that are posted with each release ? or do you just come post here and ask ?
I don't say that sarcastically either. every month their is a lot of bug fixes done on each update.
I read the "Fixes and Enhancements" in the Ezine every month.
 
so when you say "their not even doing that" I think you are being a bit bliss to the truth and fabricating your own way of thinking about it. which of course is a bit twisted.
I can appreciate you wanting a better product, but I think you need to appreciate the things you can do in a DAW in the year 2016.
things that were untouchable 3 years ago are now possible.
try to appreciate that once in a while.

chuckebaby
Kylotan,
 
There was once a time where I was very disgruntled on this forum.
for a short time I was on a mission to just blast anything I could find wrong with Sonar.
I argued with users (who I thought were being homers / Fanboi's).
Then I took a break from this forum and started using another DAW.
 
I started using Pro Tools. Tried Reaper, Studio One and Cubase.
What I finally began to realize was, these DAW's had their Quirks / bugs as well.
Some of them did exactly what I wanted, some of them did not.
Some had bugs in areas where the others did not.
 
I put my hands in front of me and created an imaginary scale and weighed out the pro's and con's
of each DAW. What I came to understand was Sonar fit my needs best.
Maybe not the best DAW...But it was the DAW that fit my needs.
 
Now back to being miserable.
I decided that if I was going to come back to this forum (which I honestly believe is one of the best support forums on the web) I was going to try and stop complaining and try to be more constructive in my comments.
(for some reason it seems like no one listens when we complain, only when we are constructive)
and that's just what I did. I also tried to help others as much as possible.
This way...if I do complain once in a great while...people will understand its not in a negative way.
 
I would go about the proper procedure and file a report on those bugs with as much info as possible.
the more detailed the better. I can see by some of your threads. you have outlined and detailed things very nicely.
that's about all you can do.
maybe your different from me but like I said above. when I stopped using sonar, I missed it.
Good luck.
 

Excellent post. It should be a sticky.

chuckebaby
but we have seen major improvements in bug fixes over the last year alone.
I have seen so many things I've called annoyances been fixed.
 
do you read the bug fixes that are posted with each release ? or do you just come post here and ask ?

 
This isn't relevant. If I see that there are 100 bug fixes one month, is that supposed to make me think, "hmm, I shouldn't care about my bug that has been ignored for half a year, because they're fixing other people's bugs"? No.
 
Nor do I buy the idea that I should somehow feel grateful for bug fixes. A bug fix is where a software company restores the software to the state that it should have been when they sold it to you in the first place. By all means, be happy bug fixes happen because life is getting better. But not grateful. We're entitled to them.
 
And I feel perfectly entitled to be annoyed that, now I no longer consent to continually renting their software to get future updates, that I'm stuck with a program that I have to fight to get to work. The six bugs in my original post have cumulatively wasted hours of my time and caused yet more disruption in terms of ruining creative flow.
 

so when you say "their not even doing that" I think you are being a bit bliss to the truth and fabricating your own way of thinking about it. which of course is a bit twisted.

 
I am sure that I am fabricating the fact that this bug report says it's not even been reviewed.
 

things that were untouchable 3 years ago are now possible.

 
And some of the things that were practical in Sonar 5 years ago are now harder to do! Thanks, take lanes.

Kylotan
This isn't relevant. If I see that there are 100 bug fixes one month, is that supposed to make me think, "hmm, I shouldn't care about my bug that has been ignored for half a year, because they're fixing other people's bugs"? No.

We all have our own personal bugs we would like fixed. im sure there are others that have been waiting longer than you to have that 1 nagging thing they want fixed.

Kylotan
A bug fix is where a software company restores the software to the state that it should have been when they sold it to you in the first place.

this is not necessarily true. when new features are introduced, things in the code change.
would you rather not have new features that make your life easier ?
 
I think you totally ignored my post above where I said I've been in your shoes before.
your not the only one who wants a better product. but we need to look at the whole scope of things and not just our own personal scope of things. wouldn't you say ?
 
if cakewalk was not fixing anything, same bugs were showing up month after month, I would be right next to you agreeing with everything. but that's not the case.
I do wish there was a better follow up system for submitted issues though. this way you would know where you stand, where your issue is in Cue. Even if they assumed your submitted report wasn't warranted enough to bump up the list, at least they could let you know that. that would be nice.
however (im guessing) they are dealing with a lot of reports and following up on everyone takes a lot of man hours.
hours id rather see spent on bettering the product.
 
What ever the case, I hope your making good music and not letting this get in the way.
enjoy the product for what it lets you do, if it doesn't, try something else.
that's the best advice I can give you.

GLG

chuckebaby
Kylotan,
 
There was once a time where I was very disgruntled on this forum.
for a short time I was on a mission to just blast anything I could find wrong with Sonar.
I argued with users (who I thought were being homers / Fanboi's).
Then I took a break from this forum and started using another DAW.
 
I started using Pro Tools. Tried Reaper, Studio One and Cubase.
What I finally began to realize was, these DAW's had their Quirks / bugs as well.
Some of them did exactly what I wanted, some of them did not.
Some had bugs in areas where the others did not.
 
I put my hands in front of me and created an imaginary scale and weighed out the pro's and con's
of each DAW. What I came to understand was Sonar fit my needs best.
Maybe not the best DAW...But it was the DAW that fit my needs.
 
Now back to being miserable.
I decided that if I was going to come back to this forum (which I honestly believe is one of the best support forums on the web) I was going to try and stop complaining and try to be more constructive in my comments.
(for some reason it seems like no one listens when we complain, only when we are constructive)
and that's just what I did. I also tried to help others as much as possible.
This way...if I do complain once in a great while...people will understand its not in a negative way.
 
I would go about the proper procedure and file a report on those bugs with as much info as possible.
the more detailed the better. I can see by some of your threads. you have outlined and detailed things very nicely.
that's about all you can do.
maybe your different from me but like I said above. when I stopped using sonar, I missed it.
Good luck.
 

Excellent post. It should be a sticky.

+1

chuckebaby
I do wish there was a better follow up system for submitted issues though. this way you would know where you stand [snip]...however (im guessing) they are dealing with a lot of reports and following up on everyone takes a lot of man hours. hours id rather see spent on bettering the product.

Your guess is correct, and I agree with your preference.