BretB
I am sure there is a list that would only be known by Cakewalk software engineering and management. I would not expect a company to openly publish such a list to the general public. Submitting a report would not be a waste of time however because the more faults they receive that are similar would tend to move that problem up the priority list.
A employer once told me "never tell a client that you have sh$*&% in your pants". That doesn't mean that you are not working hard to correct the problem.
I agree with this, but I have to say, the communities in general, and the ways of doing business have changed dramatically. In modern times, those who hide are not trustworthy. Silence is no longer golden (we left the Gold standard behind in the 40's, remember? heh).
Apple Corp. uses secrecy and silence to create a huge bang when releasing new products, and they don't speak much on bugs. BUT, what they do right is offer updates, routinely. When you release small updates it's much easier to get feedback and community testing before proceeding to the next update. Before you know it, when you'd normally send out a whole new install (X2b,c,d,e etc) all the little updates can be rolled up into that. But now you've not only tested these updates internally. You've let your users, the ones who more likely will break the product, to test additionally for you.
Transparency is modern. What if we tried this: Let's create a new entity of community users that can be responsible for monitoring this board, who have signed an NDA, but most importantly are privately communicated with by Cakewalk to validate or invalidate specific issues, concerns, or
cursidents. We can call these escalation people "sentinels". In this case, when someone posts on the forum, they have an issue, the sentinels can review it, and try to work with the individual before anyone at Cakewalk is involved. If the Sentinel validates the concern, possible bug, or just sees a collecting frustration among users, she can escalate this to Cakewalk at her discretion. Cakewalk knows that the sentinel has been briefed and understands that escalating needless issues may lose privileges to Cakewalk, so that any issues escalated are deemed important.
This is just one idea, but it helps clear a reasonable path up the food-chain, so that bugs that otherwise go unreported don't stow themselves away in the next release, lying dormant for some unsuspecting user, only to have it later be determined to be an actual bug that was grossly overlooked.
I also believe that 50% or more if the issues people have with the product aren't duplicated during a Support call, or it happens at 3AM, when many studios are still very alive and working.