And if it didn't solve someone else's similar problem, they need a different solution and need to start a NEW thread,so as to keep solutions tied to the OP. How's that for a run on sentence?

Anderton
And by the way, this post explains another very good reason for adding "solved."

Thanks Craig - please don't misunderstand, I had NO problem with it being marked as so, I was just curious who did it... fwiw I concur, as far as this thread title was concerned the issue was solved and I learnt soemthing in the process from Scook (as always ) and yourself.

I will also add solved when a question is answered or a problem has been solved. I do this after it is clear it has been solved for the reasons Mr. Anderton has already stated. No deception is intended what so ever. The notion that a host or a CW staffer would want to deceive is an absurdity.
 
   

The notion that a host or a CW staffer would want to deceive is an absurdity.

 
well.   are you sure about that?    I see many many posts that someone seems to have doctored to make the product seem better than the people who post about it think.   
 
I use Sonar, I appreciate its good points, but it is still, like many other programs by Microsoft, Apple, Adobe, and other top producers, in my estimation buggy, weirdly and carelessly designed, and counter-productive. 
 
And, hosts, marking ANYTHING at all on a post that is not your own, is overstepping a boundary, again in my lonely opinion.   Just make a comment, if appropriate (and some are very helpful, no question) but don't doctor an existing post.
 
 

On my project where I had this problem, today I went through and started deleting plugins while tapping on the kick drum key. At some point, the latency went away completely. I "undid" the most recent deletion, and the latency did not come back. I started undoing previous actions, trying to discover exactly which effect was causing the latency. Long story short I never found out. I'm guessing that there is some amount of time before a latency-causing effect actually begins to cause latency, sort of a latency latency.
 
This is not actually important, as I could easily have kept working on tracking the project with or without any and all of the effects, but...
 
I do think as a courtesy to forum users, hosts and staff should check with the original poster if (s)he feels the problem is solved before marking it solved, even if it looks to you as if it has been solved. If I had started this thread, for example, I might still have issues (see my first paragraph), and still be looking for answers. There is time enough to mark it solved. Or if it is going to be a policy that your questions might be marked "answered," then publish that policy as part of the code of conduct, perhaps with a notice that we owe it to each other to mark our own posts promptly.
 
Love you all.

williamcopper

The notion that a host or a CW staffer would want to deceive is an absurdity.

 
well.   are you sure about that?    I see many many posts that someone seems to have doctored to make the product seem better than the people who post about it think.

 
Given these "many many" posts, can you provide one example of what you mean by "doctoring" and a "doctored" post? What do you see that makes it "seem" that this mysterious deceptive "someone" has been poking around changing someone else's post? I have NEVER changed what someone else has written in a post, and I don't think any other host has, either.
 
If you consider putting "Solved" in the header of a post where the OP has said the problem was solved an example of "doctoring," then I think you are missing the entire point of a peer-to-peer support forum. The purpose of this forum is to assist people in getting the most out of SONAR, both in terms of useful techniques and solving problems. Indicating when a solution has been found for a problem increases a thread's value considerably.

Anderton
[ The purpose of this forum is to assist people in getting the most out of SONAR, both in terms of useful techniques and solving problems. Indicating when a solution has been found for a problem increases a thread's value considerably.

 
 
And that's the name of THAT tune...
 
It seems some folks think companies put up forums just for complaints. That is not a community, it's a "returns" desk.

Larry Jones
I do think as a courtesy to forum users, hosts and staff should check with the original poster if (s)he feels the problem is solved before marking it solved, even if it looks to you as if it has been solved. If I had started this thread, for example, I might still have issues (see my first paragraph), and still be looking for answers. There is time enough to mark it solved. Or if it is going to be a policy that your questions might be marked "answered," then publish that policy as part of the code of conduct, perhaps with a notice that we owe it to each other to mark our own posts promptly.

The problem is that the majority of the OPs don't mark their own posts promptly, or put "solved" in the thread title when it's solved, even when they say in a thread that it's solved...they're happy the problem is solved and they go back to making music. And because the problem is solved, they don't go back to the thread and see where someone like scook or roberet_e_bone or whoever has requested that they please put "solved" in the header. So someone has to do it for them.
 
As already explained in painstaking detail, putting "solved" in the header provides numerous benefits to the community and to those who understand how search engines work. Unless someone can point out a legitimate reason not to call attention to how to solve a problem, I don't see any downside.
 
I don't add "solved" unless the poster has indicated the problem has been solved, which is clearly what happened with this thread. The only time I will add solved without this is if the thread has sat there for a considerable amount of time, a solution which clearly solves the problem based on past experience has been presented, and the OP never came back to confirm that the posted solution solved his problem. It's FAR more likely someone will return to a thread if a problem is not solved. 
 
If I add "solved" for any reason other than the two above, I will post in the thread saying I added "solved," and explain why. For example I think the guy who solved his Axiom problem because it wasn't compatible with USB 3.0 by using a USB 2.0 hub that was compatible with 3.0 presented a brilliant tip that has applications beyond just the Axiom 49. Technically, it didn't "solve" the compatibility issue per se - the Axiom 49 still doesn't work with USB 3.0 - but it solved how the Axiom 49 could be made compatible with a USB 3.0 system. So I put "solved" in the header, and explained why in a post. 
 
Seriously, how can anyone have a problem with that?
 
 

I gotta be "serious" too?  

You can be Sirius, or you can be XM. Your choice.