Keith Albright [Cakewalk]
I understand nothing is perfect. But know we are committed to quality and new compelling features as well as continuing to improve on existing features.
There was an X2A. That easily had two hundred fixes in that. It wasn't a tiny patch by any stretch.
As a demonstration of our commitment to quality, we built an automatic fault reporter and added fault detection to the applications.
In addition we have the web problem reporter.
https://www.cakewalk.com/support/contact/problemreport.aspx
We do look at both the automatic and web entered reports and work to address them.
Obviously we don't have infinite time or resources, so we must prioritize. But, the more everyone uses these systems, the better the priorities will be.
Thanks.
Keith
Absolutely Cakewalk has improved the fault reporting system, and given the fact that most users are musicians and not computer experts, it is far more likely you will receive reliable and useful data from a robot than from a user. Definitely there have been numerous bug fixes included in the update packages, proving that Cakewalk does investigate and fix problems.
Now I would like to suggest a new support feature that would save users thousands of hours of wasted time:
Include a known issues page on your support website, that will tell users what bugs you have found and what features do not work as most users expect they will.
A user who finds something is not working as expected may spend hours repeating his attempts to get it to work, uninstalling and re-installing plugins that are not to blame, searching this forum (good luck with that) to see if it is only a problem on his system and finally reporting it to Cakewalk. In many cases these bugs or whatever you choose to call them will already be well defined in your support pipeline, and if the user could see what bugs you already know about it would be very helpful as a first step in troubleshooting his problem.
I appreciate it when you proudly list the bugs that you have fixed in the new update. That is not just good information to decide if the update should be applied, but good marketing. But that does not really help recover wasted time when the user uncovers the bug on his system before it is fixed. I also understand that listing problems that exist but have not (or will not) be fixed is bad for sales. A prospective buyer may be put off by a list of dozens of things the do not work. But there might actually be some who are impressed with the integrity implied in such a resource. And you might find that your support costs would be less, and your response times better if you did not receive duplicative emails and calls from users who had all discovered the same bug, to whom you have to individually reply that this is a known issue that you are working on (or not ).