Big of you to apologize, but we all blow off steam, say inappropriate things and just plain have our a-hole days :)  Most of it comes from passion.  I think we all agree that we simply want Sonar to be the best product it can be and actually perform all the features listed as advertised. It's so had online at times to reflect intent and even harder to take back words that did not come across to others as it dd in our heads.  All good.  Merry Christmas

I feel your pain when it comes to technology, but I've found that one of the easiest ways to avoid frustration with ALL technology is first to find out how it wants to be used, and use it as intended. It's like I pointed out regarding the issue you're having with Take Lanes - they're Take Lanes, not Edit Lanes. You can edit with them, but they're not optimized for that application. Conversely, standard tracks aren't optimized for comping.
 
There have been many times I've tried to get technology to do what I want it to do. But if that's not what it wants to do, I can expect frustration to follow shortly thereafter!
 
Many posts that relate to "bugs" actually translate to "Sonar doesn't do things the way I expect them to be done." Now, there's a lot to be said for programs that are truly intuitive--someone can walk up to it without knowing anything, and get it to work because it works as you'd expect. But, different people have different ideas of what's "intuitive," so it's not always possible to satisfy all those needs.
 
For example, if someone had never seen Sonar before and wanted to insert a measure in a project, they might think "Project" would be the appropriate place to look because they need to insert a measure in a project. Or they might think that "Insert" would be the appropriate place to look because they need to insert a measure in a project. Who's right? Answer: The programmers--because you can't change what they programmed.
 
I've learned to accept what a program does. If doing a punch in the middle of a loop causes problems, I'll just punch on a different track and paste the results into the loop. To me, it's not a big deal to use workarounds providing that they really do work around a problem. At that point, it becomes less important to me whether a problem is fixed or not...I'd rather see problems fixed for which there is no workaround.

Craig, I can relate to and appreciate what you are saying, but when product behavior changes workflow  from patch to patch, it gets frustrating. I used to be able to do things and now I am not. That is where most of my frustration comes from.

I know that the bakers see this forum and that beta testers report back to the bakers about this forum, so my postings are 1 - to report issues and 2 - show them, and others, I am not happy with whatever is bugging me about a product that I paid for.
 
I am gonna go grab some coffee now so I don't start ranting again. Thanks for your time and concern.

 
use the weapon your most familiar with, your heart.

 
 
liked your first post a lot :-)

Show me a partnership, business, organization, product or whatever where there is no tension,frustration and sometimes out of control,over the top rhetoric..and I will show you a partnership, business,organization, product or whatever that is heading for irrelevancy..
 
Keep being vocal about the things that matter to you - It's called passion and it inherently has an attitude 

I have never been accused of being passionless. :) thx DK.

"We're a forgiving bunch!"
 
That`s true
 
Peace