I've seen it, too. For me 2016.5 or possibly the previous release was the first time in a very long time.

Are you able to see this bug report (from 22 April):
 
https://www.cakewalk.com/...em-Report-Status/49792
 
How long can we expect it to stay in "New" status?
 
What is the point of having a bug reporting system if Cakewalk never actually gets around to reviewing the bugs???

We can't see your bug reports, only our own when we follow that link.

Well, evidently Cakewalk can't see my bug reports either. 
 
They're still in "New" (unreviewed) status even though the most recent one is from back in April.

Tripecac
Well, evidently Cakewalk can't see my bug reports either. 
 
They're still in "New" (unreviewed) status even though the most recent one is from back in April.

Seriously dude.... methinks you complain too much! How many threads do you think can you resurrect before someone calls you out? 

Posting on these forums is the only way to get Cakewalk to address bugs in Sonar.  It has been this way for some time.  The support channels are mostly there to handle sales and minor installation problems.  It gives a false sense of security that support actually exists.  The wall between front-line support and the Sonar development teams is nearly impossible to breach.
 

Has it always been like this, or was Cakewalk more responsive to bugs back in the pre-X1 days?  (I didn't experience nearly as many bugs prior to X1, so don't know how to compare before-and-after support quality.)

msorrels
Posting on these forums is the only way to get Cakewalk to address bugs in Sonar.  It has been this way for some time.  The support channels are mostly there to handle sales and minor installation problems.  It gives a false sense of security that support actually exists.  The wall between front-line support and the Sonar development teams is nearly impossible to breach.
 

while I understand some of your opinion, its not true.
bringing attention the details that need fixing / constant complaining are two different things.
its one thing to come here and share your ideas, discuss issues that need fixing, then its another thing to come here only to voice your displeasure.
can you imagine if every single person did this ? who would be here ? no one.
 
I also don't believe the "Squeaky wheel gets the grease" either.
there are certain things I would love to see improved and a few minor issues I would like to see resolved as well. 
but im not going to go on a mission of thread after thread of negative feedback.
that helps no one.
 
I put my trust in the developers/bakers that sooner or later they will address issues.
if I don't put my trust in the developers/bakers I wouldn't be using Sonar and I surely wouldn't be here.
 
I've always looked at this forum as a give and take. (now that's just my opinion / the way I think)
I have received help from good people here...and in return, I've returned that favor by helping others.
you give... you take.
 
 
 
 

Tripecac
Well, evidently Cakewalk can't see my bug reports either. 
They're still in "New" (unreviewed) status even though the most recent one is from back in April.

That is in accordance with my experience. I have a problem report from 3/13/2016 that is still on status "New".

I put my trust in the developers/bakers that sooner or later they will address issues.

 
Well, trust has to be earned.  And it can be lost. 
 
As of Sonar 8.5.3 I was pretty trusting.  When I started to have problems with X1, then X2, then X3, then Platinum... my trust in Cakewalk eroded.
 
When I see bugs I submitted in April still marked "New" and "not yet reviewed", that further erodes my trust in Cakewalk.
 
It seems like the only threads that I've posted which actually get Cakewalk's attention are the ones which question their business model.  In other word, Cakewalk seems far more interested in what we give them (money) than what they give us (quality product and support).  This disparity further erodes my trust in Cakewalk.
 
I'm sorry if you find my attempts at getting bugs fixed annoying.  I tried the forum first.  Nothing.  Then I tried the problem reporter.  Nothing.  Now I am trying the forum again, seeking to find other people who are experiencing the same problems. 
 
Please tell me: How else can I get the bugs fixed?  Cakewalk's code is not available for scrutiny and recompilation.  If it was, I would fix these bugs myself.
 
Should I just give up?  Let the bugs win?  Move to another software package?  What? 
 
I'm not some whiny newbie, irritated at the slightest little hitch. 
 
I have been using Cakewalk products since 2000, and have a well-established work flow.  When Cakewalk introduces new bugs that interrupt that workflow, I get annoyed.  Naturally.  And I try to get those bugs fixed.  Naturally.  I don't just quietly, stoically suffer.  I am not a sheep (despite the fact that I live in New Zealand).
 
Unlike the blindly faithful (and faithfully blind), I believe that sometimes you HAVE to be a squeaky wheel in order to get adequate customer support.  In my case, when the "quiet" path (of using the problem reporter) doesn't work, I have to resort to the "loud" path (of repetition on the forums).
 
I'm sorry if my bug reporting bothers you.  I am trying to draw Cakewalk's attention to the bugs, so that they can be fixed.  If you don't want to read my topics, then don't.  If you see "tripecac" as the starter of a topic, then don't open it.  And certainly don't post to it, because each time you do, it pushes the thread to the top of the queue, thus encouraging other people to contribute to it, adding even more noise.  By posting in my topics you are only making the wheel squeakier, which helps me, but annoys you.  So why do it?  Why deliberately annoy yourself?