Oh Craig! Why did you start this. Experience shows that no matter how pretty a flower is, by the time it's passed through the forum it's often been covered with so much crap that you can't see the flower any more.
Oh why Craig?

Anderton

BASSIC Productions
Mr. Anderton, when something isn't working and you offer a complicated work around, it has a very "... then let them eat cake" kind of feel to us users.

 
I didn't realize you spoke for all users, but thanks for the heads-up. It never occurred to me that trying to help people with problems they're having would be seen as my being callous. I figured people who are having some kind of problem would appreciate any solution compared to no solution.
 

Well nobody speaks for all users, but speaking for this user only (myself, to make sure it's excruciatingly clear, which seems to be necessary around here sometimes) I very much do appreciate workarounds being offered when a problem presents itself, for a number of reasons: 
 
First, being of a pragmatic bent I'm the kind of person that would prefer to get past the problem and get on with whatever I'm doing that the problem is obstructing, rather than spend much (if any) time complaining about the problem being there in the first place. Bugs happen. I want to get back to work. 
 
But perhaps more importantly, workarounds are generally the product of lateral, creative, problem-solving-type thinking, and therefore offer much more than merely getting past the disconnect of problem and solution. They also frequently provide a different perspective from which to think about the 'problem', thereby uncovering other possibilities that might never have come to light if the problem had never happened. 
 
Furthermore, since there may be several viable 'workarounds' to any given 'problem' - i.e. several different perspectives to look at the situation from - it's a way of interfacing with someone else's knowledge of the program and/or someone else's creative or problem-solving process. I have been using Sonar for a long time, and have relatively thorough knowledge of the fairly thin slice of its functionality that applies to my everyday workflow, but there are lots of feature areas that I never use and therefore have very little knowledge of. If a 'workaround' involves those unused functions, it can open up ways of working that I would never have noticed or bothered with, as they don't obviously apply to my workflow, and possibly enhance my experience and knowledge of the program - or even show me better ways of doing what I already do. 
 
Finally, I have a hunch that every once in a while this process can fuel actual program innovation, where what starts out as a workaround suggests a different way of working, that leads to a lightbulb moment, that leads to new features and functionality down the road. Whether there are concrete examples of this I cannot say, but it wouldn't surprise me. 
 
So please, Craig and everyone else who helpfully posts 'workarounds' here, whether as a stopgap measure until bugs (hopefully) get squashed, or for the more subtle purposes described above, please ignore the ungrateful voices that posit 'workarounds' as somehow patronizing or unhelpful because they aren't Fixing My Exact Problem Now... please keep offering them. There are those of us who greatly appreciate them, and you never know where they may end up...

mudgel
Oh Craig! Why did you start this. Experience shows that no matter how pretty a flower is, by the time it's passed through the forum it's often been covered with so much crap that you can't see the flower any more.
Oh why Craig?

Crap, fertizer... let's grow a pretty flower, otherwise you just have a little sprout.

I know for a fact that I'm not OT for saying this here this time
 
Here we go again ..this thread has turned into a perfect example of Newtons 3 rd law in action ..
 
 
Newton's third law is: For every action, there is an equal and opposite reaction. The statement means that in every interaction, there is a pair of forces acting on the two interacting objects. The size of the forces on the first object equals the size of the force on the second object.
 
Kenny

Thank you for sharing this Craig. It is really encouraging to see how that interaction was successful. I see a lot of upside moving forward.

subtlearts
First, being of a pragmatic bent I'm the kind of person that would prefer to get past the problem and get on with whatever I'm doing that the problem is obstructing, rather than spend much (if any) time complaining about the problem being there in the first place. Bugs happen. I want to get back to work. 

This is my situation too. Having worked with software for over 40 years I know there will be bugs. The more you push software into areas that weren't tested thoroughly, or for which others have no use case, or were not accounted for in the original product design, the more likely you will find those bugs.
 
However I am also aware that pilot error is a huge factor. Despite using SONAR for almost 17 years, I still make rookie mistakes. I don't excoriate myself for those any more than I excoriate a company for making them.
 
People need to realize human beings are flawed, imperfect, fragile, and often damaged. We're all in this together. By helping our fellow travelers we improve the world. By understanding them, we improve ourselves.

Props for pointing it out craig!
 
And as far as other users negative comments on your presence here, Id like to point out that you are a blessing to the community through your weekly instructional tips that are 9 times out of ten - something I never would have thought of in my daily workflow - and your involvement in helping users find solutions.

Hi. Thanks for trying to post something positive here. Appreciate it.
If nothing else, this thread has given me perspective as to where I will bother to try to help out in the future.
There are always someone new to put on that list 
All the best.

Hello,
I really don't get this and though I have come to respect Craig and the Bakers as it stands. But have become just plan tired of the propaganda here... lol it's all a mater of perception... My Splat is broken!
 
Craig you said a few posts back that kindness goes farther then being mean. (well something like that).
To me that says the Bakers allows their emotions to dictate bug fixies.
 
People here are also saying that "you can't expect to buy houses and cars without issues".
Well that's not the same thing unless you are talking about a used software package because new cars and new homes normally come new from top to bottom and if there is a problem say with a car they get it fixed fast or there ends up being a recall. With a new home... When you buy a new home, if there is a problem it will gets fixed fast or the contractor gets suited or worse.
 
Software is not a house or a car and yes there are bugs... but coming from a gamer/artist point of view I have rarely come across bugs in games or graphic/animation 2d/3d programs and it would be only days before a patch would be available. yes it still happens but one thing about games and graphic software... when you got a patch it left everything working alone... and in the old days... ;) a software company would release what worked 100% then you could buy the upgrade of the software with new features next year. I think the "Why is Cakewalk  not ProTool?" is simple, they could not deliver back in the day... and they still fight to deliver. Where is a the solid DAW foundation?
 
I have no idea about apple or protools and other DAWs though I have checked out a few others.
I think that Cakewalk's DAWs are extremely comprehensive in theory but the bugs are extreme as well.
 
I really could care less about the "right way" to get a bug fixed! what I do care about is when something has worked for 10 years than it stops working... that's a problem. I could give many examples but what's the point? They rushed 2016 10, 11 and 12 out the door because they said that they could deliver every month.
None of these work "for everyone" though some cool features have been born! The foundation of Splat is crumpling! there is just too much stuff jammed in! lol But tying to tell anyone "how to do it" is... lol 
 
This was not posed with any hostility... I really don't care enough about it for it to effect me...  
Peace!
 
 

I know hostility when I see it, and my hostility meter's needle didn't move.
 
But let's get reality out of the way. Games and artist programs outsell DAWs by multiple orders of magnitude. For example Electronic Arts has 7,645 employees. Adobe had somewhere around 10,000 last time I looked. People don't seem to understand the market for DAWs is a tiny fringe of a tiny niche in a tiny market, and that alone imposes constraints. Unless people are willing to pay $2,000 - $3,000 for a DAW, these constraints will continue to exist (and not just for Cakewalk by any means). Other DAWs don't deserve to get the crap they endure on their forums.
 
I've been thinking about something else...music. There are bands that are sloppy but exciting. There are bands that play to a click track and reproduce what's on their CD. I think the people who like SONAR like that the company pushes limits and take chances. Yes, that can lead to occasional fails, but also to elements that no other DAW has. 
 
I can only say what I've said many times. It is not a company's responsibility to conform to an individual's needs. It is the individual's responsibility to find a program that conforms to their needs. With few exceptions, that will not be possible - which entails making compromises.
 
I started this thread because I wanted to encourage forumites to follow THambrecht's example, give him and the forum props for their detective work, and I wanted Cakewalk to take better advantage of what this forum has to offer. I'm sorry I ever started it, which is why I've cut back my participation in the forum recently, and will scale it back further going forward since I apparently cannot convey what I want to say with sufficient clarity.