i was going to comment that bob's info was really useful because reaper was ok but sonar not so much, surely there's some useful comparison to be done there?
/fwiw

A Waves reinstall solved the problem. I cannot say for sure but my guess is Jim locked the thread because the user fixed his system problem.

scook
A Waves reinstall solved the problem. I cannot say for sure but my guess is Jim locked the thread because the user fixed his system problem.

As expected ...

ok

i expect that he will lock all the other "solved" threads then, for consistency

pwalpwal
i expect that he will lock all the other "solved" threads then, for consistency

That would make sense only if there was only one flavor of "solved." Some solved issues are of universal importance, some aren't.

Anderton

pwalpwal
i expect that he will lock all the other "solved" threads then, for consistency

That would make sense only if there was only one flavor of "solved." Some solved issues are of universal importance, some aren't.

just seemed a bit unusual, threads hardly ever get locked here (a good thing, imo, btw)

pwalpwal
 
just seemed a bit unusual, threads hardly ever get locked here (a good thing, imo, btw)

When the thread is related to Early Release posts in the Problem Reports forum, I think Jim Lima locks the report to indicate that he has either reported the problem to the developers or the user has solved the problem.  Locking indicates that Jim or someone else from Cakewalk no longer has to review that problem when reviewing the list of Early Release issues in the forum.
 
-- Ron