In April, I used Cakewalk's Problem Report form to log two bugs I found in Sonar Platinum.  As of today, the Problem Report page says the following about their status:
 

The current status of your report is
New
This is a new problem report. It has not yet been reviewed by Cakewalk.

 
How long does it usually take for Cakewalk to review its problem reports?

mine have been reviewed as fast as a few days.
 
I just saw your other post telling a user  "Please do not upgrade"... and your other thread on a bug in the PRV.
is this real reason for this thread ?
 
I know everyone has issues, some more then others and I can appreciate people striving for greatness, wanting the product to be the best it can possibly be. but I don't think more threads, more comments are going to help that.
I do hope what ever your issue is (the problem reporter) gets resolved soon.
 
make good music + good luck

Thanks for the kind post.  Sorry if my posts annoy. 
 
I am being deliberately "squeaky" in an attempt to draw Cakewalk's attention to the bugs I (and other people) have reported.  Once Cakewalk fixes the bugs my "negative attitude" will ago away, and I will spend less time on this forum seeking fixes and more time making music. 
 
I don't know how else to direct Cakewalk's attention to the bugs, other than by repeatedly bringing them up on the forum.  The "sanctioned" method of using the Cakewalk's Problem Reporter certainly didn't work (so far).  What else can I do? 

They recently revamped their support response process, and likely regularly tweak it.  It seems that there are currently some ongoing issues affecting some folks from getting through to support.
 
They DO triage reported bugs, and how that is done I have no idea, other than that they seem to try to address bugs that affect wide swaths of folks - even putting together quick/hot fixes on occasion in a special maintenance release if a severe enough issue isn't detected until a given update version is released.
 
I happen to have a bug that I would do cartwheels on the front lawn if and when it gets fixed, but it doesn't ever bubble up high enough to warrant someone getting assigned to enhance/maintain that piece of code.  I DO happen to have a workaround for the issue, it is just messy.
 
In the meantime, I wait and hope for its resolution.  I LOVE working with Sonar, and have found the forum member community to be chock FULL of folks who work really hard to help each other with many/most aspects of using the products, including configuration changes, OS maintenance, issues, workarounds, and all sorts of other things.  GREAT community of folks with unmatched depth of knowledge.  I try to give back when I can, and many others approach helping the community in the same manner.
 
Bob Bone
 

Out of curiosity, what is your bug?

Sure - I write a lot of prog tunes, many with multiple meter changes, such as 5/4, 7/4, 5/8, 7/8, 9/8, 15/16, and once even covered a Bruford song that was written mainly in 19/16.  It would be one thing to have only an occasional meter change, but I tend to have places in many songs where there are cycles that combine multiple meters into evolving/revolving sections of alternating meters.  (Steve Morse has a song with over 50 meter changes, as an example of others that do this kind of thing).
 
So, I create many of the tracks using the Step Sequencer, which currently ONLY allows for the use of a quarter note as the meter base, so it is a ROYAL pain to try to deal with any of the above meters that use an eighth-note as the meter base.
 
My workaround is to have to do a 9/8 measure as a measure of 9/4, which then would play back at half the desired tempo, so I have to also insert a tempo change to double the song's tempo at the point where the measure of 9/4 starts.  Then, after finishing with however many of those measures there are in a row, I have to insert another tempo change to reduce the tempo by half, in addition to the meter change back to 4/4 or whatever I was in.
 
The above makes printed scores look like I am an idiot, because nobody in their right mind would create a score with such a goofy meter and tempo change, where a normal 9/8 would have worked fine.
 
In addition, I quite frequently have songs where I will routinely alternate between 1 measure of perhaps 9/8, followed by a measure of 4/4, and alternate between them, or in any case end up with many many meter changes where I also have to do that stupid tempo doubling and halving.
 
Lastly, it is annoying to have to make sure when constructing songs that any doubled tempo is an even value - because cutting a tempo of 119 in half doesn't work too well.
 
But, as I had indicated - not that many folks do as many meter changes as I do, so I get that, and I DO have a workaround, it's just a pain.
 
Bob Bone
 

That's quite a workaround Bob! I have a couple of niggling issues that I reported last year. Despite the fact that they bother me, given that they are not showstoppers and they only affect me due to my workflow habits, I understand that there are certainly more pressing issues for the bakers to deal with. 
 
On the other hand I reported a problem with rendering bit rate changes that was fixed in the next update. Cakewalk certainly do rightly pay attention to the most pressing issues that affect the largest number of users. 

Tripecac
Thanks for the kind post.  Sorry if my posts annoy. 
 
I am being deliberately "squeaky" in an attempt to draw Cakewalk's attention to the bugs I (and other people) have reported.  Once Cakewalk fixes the bugs my "negative attitude" will ago away, and I will spend less time on this forum seeking fixes and more time making music.

 
Negative attitudes seldom produce positive results, especially when it's presented in a context of "I'll stop being negative once Cakewalk fixes the bugs that I consider important."
 

I don't know how else to direct Cakewalk's attention to the bugs, other than by repeatedly bringing them up on the forum.  The "sanctioned" method of using the Cakewalk's Problem Reporter certainly didn't work (so far).  What else can I do? 

Bugs are in a queue. The order of the queue depends on multiple factors. The primary one is if large numbers of users are affected and it causes crashes or serious operational problem. Bugs with workarounds, and issues people refer to as "bugs" but are not, are low priority. All the rest fall somewhere in between. One person bringing up the same bug multiple times doesn't induce Cakewalk to prioritize the bug. Multiple people bringing up the same bug once does.
 
That bug you were complaining about that had something to do with track folders and inserting a track going outside of it was fixed. It's probably best to appreciate that some of the bug that affect you are being fixed, rather that being unhappy that not that all of them aren't, and get back to making music. People score movies, top-rated television shows, and create everything from sophisticated talking book projects to albums to sample libraries using SONAR.

Craig, Just let people be people please.

craig's a person too don't you know batman