Me? ZERO 
 
I've reported 8 issues via tech support/problem reporter this year (March-May to be more precise) but none of them has been reported back as fixed. The issues I reported are obvious and most of them have been confirmed by other users here and/or CW themselves. The status of problem reporter tickets I submitted are currently "Submitted to Development," "Under Investigation" and "Status Changed." I sent a reminder to tech support this week listing all my ticket numbers but was only told to wait for the next status change.
 
I had expected CW to fix at least a few of them before X3.
 
Hmmmmmmmmmmmmmmmm...

That's normal. We only update the reports when fixes are officially available to the public in the form of an update or a new version.

Nobody in tech support is going to be able to answer your question about the status of things beyond that unfortunately. If the bugs were submitted to dev then the tech folks can't provide more info until dev returns an official fix that we can give to you, which really is the ultimate point of the form.

I should clarify. We only update reports to "fixed" when fixes are officially available.

Thanks for chiming in Ryan. I was worried because it had been taking so long but according to your explanation they don't change the status to "fixed" even if they already fixed it 3 months ago, right? Then I just hope some of my issues have been fixed and will quietly wait for X3. Thank you.

Cakewalk tech support doesn't manage planning anymore. It's done by Roland management. Tech
support is a scarce resource, and they manage change request priority based on time estimates,
number of users affected, potential revenue impact, and so forth. I've got a couple tickets that
were first reported for SONAR 5 that remain unfixed. They're things that involve unusual machine
setups and only affect one or two dozen users, so its not likely they will ever get fixed. Your reports
may be impacting you severely, but they won't get much priority unless they're impacting many
users. Like thousands. You also have to compete with all of the development work for new features
and product versions. So your opportunity window can get pretty small. Keep your fingers crossed.
You may get lucky and see some fixes show up.

peregrine
Cakewalk tech support doesn't manage planning anymore. It's done by Roland management. Tech
support is a scarce resource, and they manage change request priority based on time estimates,
number of users affected, potential revenue impact, and so forth. I've got a couple tickets that
were first reported for SONAR 5 that remain unfixed. They're things that involve unusual machine
setups and only affect one or two dozen users, so its not likely they will ever get fixed. Your reports
may be impacting you severely, but they won't get much priority unless they're impacting many
users. Like thousands. You also have to compete with all of the development work for new features
and product versions. So your opportunity window can get pretty small. Keep your fingers crossed.
You may get lucky and see some fixes show up.

None of this is really correct. I work in tech support and have personally been on the front lines for years with helping the Cakewalk product management, quality assurance, and development to identify problem areas and escalate appropriately. Work with tech support, always. Friendly reminder that Cakewalk develops SONAR, and that Cakewalk tech support is a very important resource. No offense to Roland management, but I'd like to think I'm a lot more involved in that process.
 
My point before was that if a bug is already at the stage "submitted to development", we can't identify if the issue is officially resolved until we get the stamp of approval from development and QA that says "we tested and regressed the bug and are confident that this issue is resolved". The "submitted to development" is the acknowledgement you need. Asking for any further acknowledgement is sort of just asking people do what they've already done. It doesn't really go anywhere.
 
Just trying to clarify what I meant by tech support not really being able to relay further info until the reports come back to us.

Why do people post pure speculation as fact?

Because there's no facts available at this time?

 I vaguely recall someone saying something about a thought they had about what someone else was supposed to do in some situation or another.
 
That's a fact.
 

bapu
 I vaguely recall someone saying something about a thought they had about what someone else was supposed to do in some situation or another. That's a fact. 

We all love a fact hunt...