I am rather confused by that. Fixing bugs does not make a better product? Ironically, no one seems to consider the man hours spent by users writing these reports.

You won't win, although I agree completely. The party line is stronger than the issues of mere users. Sales are up, that's all that seems to matter.

mettelus
I am rather confused by that. Fixing bugs does not make a better product? Ironically, no one seems to consider the man hours spent by users writing these reports.

I'm not sure that was what was said. Fixing bugs does make a better product and I don't think anyone would dispute that. Its the following up with reporting back that might be unproductive. If its fixed does CW really need to inform the reporting user that it was fixed? My understanding is they list it being fixed in a file like the eZine. 

I personally would like to know where I stand with a report I've sent in. but as I said in my previous post,
that's man hours that could be spent bettering the product.
an automated message would be helpful. If the bug is fixed, then its checked off and sent "as Fixed" to the user who reported it.
 
but... im hypothetically speaking here.
in the large grand scheme of things, my idea sounds a bit ridicules.
this is a software company, not a dating service. I shouldn't have to be sent a message saying my reported bug has been fixed unless they are sending out reward points for problems reported.
 
I also read the enzymes... I mean Ezine  

mettelus
I am rather confused by that. Fixing bugs does not make a better product?

 
Of course it does.
 

Ironically, no one seems to consider the man hours spent by users writing these reports.

Presumably the people who do so write those reports to help improve the program. Then the question becomes which will improve the program more, spending time fixing the bugs, or spending time providing status and feedback reports to the people submitting the bugs. In an ideal world, there would be sufficient resources to do both. Given that this is not an ideal world, priorities have to be set. I can certainly understand that a person who submitted a report would get frustrated if there was not sufficient acknowledgement of that particular report, but if there's a bug experienced by multiple people, fixing it would reduce frustration for a greater number of users. I do know that people monitor the fixes in the eZine and are gratified when they see something they reported, or that bothered them, is fixed.
 
I don't know whether the feedback portal will streamline this process or not. 

chuckebaby
What ever the case, I hope your making good music and not letting this get in the way.

If only. Here's today's Take Lane bug wasting my time and interrupting my flow.
 

 
I don't come here to complain because I like to cause trouble. I come here because this is wasting my valuable creative time each time I have to fight with the software. I don't know a single other piece of software that is so inconsistent with what is supposed to be its basic functionality. And I'll be damned if I'm paying out again in the vague hope that some of this ridiculousness finally gets addressed after festering for years.
 

Klyotan,
 
I'll answer your question directly:
 
I read your links with interest, and I have never run into any of the issues you post about here (including the takelane issue you so thoughtfully provided a video of.) The reason I haven't for most of them is probably because my workflow is different from yours, so I haven't run into those specific defects or I haven't set up the conditions for them to show their ugly little faces, but I do sympathize with your frustration. I know you don't want to hear about suggested alterations to your workflow, so I'll move right along here.
 
You're entitled to feel whatever you want, and you're entitled to express any opinion or make any assertion you feel like making here. I fully support this exercise in disgruntlement exposition, and I completely understand if you decide to pack Sonar away and move along to another product. We do what we gotta do to make things work.
 
On the other hand, no one is required to agree with you or anybody else here, and I find it a bit humorous that so many folks post things and then get upset when people challenge their assertions. 
 
As a software developer, you're no doubt aware of how bug reports flow through organizations and how they decide to fix things. If you're a corporate developer, reporting status to your customer is an essential part of keeping the business running. As a commercial product developer where customers may number in the tens or hundreds of thousands, or even millions (in the case of companies like Apple, Google and Microsoft) closing the feedback loop is incredibly difficult. Nobody likes letting that kind of opportunity for customer communication go. 
 
As for the issues I do experience, I elect to read the release notes and check to see if the most impactful issues are still there. I don't want to tell you how to manage that process, but if you do that, you don't need to post questions like the one you posed here. Just skip to the part where you create a fun Cakewalk-bashing-rage-quit thread. [Update: This last comment is supposed to be humorous and does not necessarily reflect my opinion of actual persons, either alive or dead.]
 
I sincerely hope you find something that works well for you!
 

I'd like to add one more point. When I started working in the software industry, complex apps like Sonar that targeted very small markets were STUPID expensive, and very often required custom hardware to function at all. The price we pay for Sonar today is ridiculously low for what it does, even if we pay for twenty years of updates. On the other hand, the cost of developing software has not gotten that much less expensive, so companies elect to offer low initial pricing and charge for updates to make those costs up on the back end. That's a good thing for everybody, imho.
 
The good news is that if you make a compelling case for fixing the issues that cause you grief here, Cakewalk will see the traction you're getting and move the issues up the priority stack. Long-term engagement works for customers and suppliers.
 

Kylotan

chuckebaby
What ever the case, I hope your making good music and not letting this get in the way.

If only. Here's today's Take Lane bug wasting my time and interrupting my flow.

there are tack lane enhancements in the oven, when I don't know but if you look at cakewalk's main page "future updates" you can see what is planned:
Take Management & Comping Enhancements
http://www.cakewalk.com/Products/SONAR/Rolling-Updates#In-The-Oven
 
by the look of it, there are a lot of great updates in store. hope this helps.

Kylotan
If only. Here's today's Take Lane bug wasting my time and interrupting my flow.

 
After seeing your video, I tried to reproduce but couldn't. I don't doubt you're experiencing this for whatever reason, but given that Cakewalk is revamping take lanes, I was hoping to reproduce so I could provide data that might be helpful. Oh well.