Well - I appreciate ANY efforts that anyone makes towards making software work better for all using it, whether Sonar support staff, the second string of Sonar employees trying to get the backlog under control, the willing forumites, or whomever. That said, I've rarely gotten responses that fixed a problem from mailing support or filling out their online forms. I've only done it a few times over the years.
I used to be a lot more active here with assisting others, providing tutorials, etc, but haven't had as much time to spend on this as I used to.
I currently have two issues in the problem reporting system. They are both issues that have existed through many versions that I can't imagine others are not having - in fact I've seen a few posts about them without remedy. They are not show stopper bugs, but seem like the kind of thing that would have gotten fixed because they both represent a problem with a feature that plain doesn't work.
Both are about (midi) Remote Control. One of them allows the remote control to function in that the on-screen images change when the control is changed, but the things that they are supposed to have an effect on do nothing. In this case, it's the send on/off of a channel. Map it to a button on my PCR800 and it doesn't turn the send on and off. the GUI shows it being turned on/off, but audio is unaffected.
The second one is because the first one didn't work. Using the same midi Remote Control concept, I have assigned a button on the PCR800 to toggle the mute on my hardware output. I have one output for speakers, one for headphones. I have the same remote set to each with the toggle initially set so that they are opposite of each other (one pair muted, one not). This completely works and makes it very each for me to change from speakers to headphones with a single button.
Unfortunately, none of the mid Remote Control assignments are saved with the project. So every time I open any project (including my scratchpad), I have to remember to add the Remote Control assignment to both of the main buttons. I wouldn't use the feature for anything else because it would be rendered pretty useless if I had to try to remember a bunch of CC information and which controls I had it set to.
Is it a bug? Seems pretty dumb that they would intentionally not choose to save this info with the project. A complex setup would get completely out of hand. And the things I'm trying to control are not in ACT, so I can't just use that, which I'd prefer, but they aren't there.
All of this comes down to the response to my problem report when I check it:
Status InformationThe current status of your report is
New This is a new problem report. It has not yet been reviewed by Cakewalk.
I submitted the report on 8/20/16. That is 16 days ago and the report isn't even acknowledged. Since I run a technical support company with a ticketing system, I can say if we had a ticket that wasn't even acknowledged as existing for 16 days, there would be meetings and resolutions, or at least communication.
Sorry for the rant. Just showing ACTUAL experience.