This post has been a giant waste of time.
 
I think the OP might be just getting his jollies watching all the folks try to help, while not engaging in the thread himself.
 
I don't believe I will be participating in this guy's threads anytime soon.
 
If he doesn't care enough to participate, then I guess I don't care if his issues ever get fixed.
 
Bob Bone
 

GUESS WHAT!


I was doing a LOT of automated punch in/outs today and then all of the sudden the time line became jerky. I have no idea why. Not only that but volume knobs and loads of other controls became difficult to control (it was like the refresh rate was down to about 0.25 seconds). I was still able to carry on overdubbing but it was irritating.
 
So I saved the project and closed/reopened Sonar. Still the issue persisted. I could not get rid of it. Then I rebooted the PC and it completely cleared. So this 100% demonstrates to me this is EXTERNAL to Sonar. I'm guessing display drivers as I rolled them back recently, it could also be my Focusrite drivers (the latency was set very low maybe it didn't like it), but I cannot confirm this.
 
However I can confirm 100% this is DEFINATELY NOT a Sonar issue otherwise the issue would have cleared when restarting Sonar, or the issue would have persisted after a reboot. Case closed. BTW if your issue persists after a reboot then you have an even more serious issue away from Sonar (and frankly you need to fix it, don't expect any more help).

Sounds like CPU conservation mode was enabled http://www.cakewalk.com/D...dioPerformance.21.html

scook
Sounds like CPU conservation mode was enabled http://www.cakewalk.com/D...dioPerformance.21.html

I doubt it because restarting Sonar and restarting the PC had entirely different behaviour. Anyway I'll see if I can repro again (I will be lucky!).
  
Cheers...

Alex,
Your troubleshooting method is not sound.  Just because an issue goes away on reboot does not necessarily mean that there is not an issue with Sonar.  Yes, there is some other issue that is contributing to a problem that is observed within Sonar, but it also depends on whether the outside-of-Sonar issue affects anything else or just Sonar - is it for all apps that use the audio driver?  Is it for all apps when the system usage of memory gets to a certain point?  What other factors are there?
 
Computer systems are a lot more complex than a simple "if a reboot fixed it, it can't be the software".  Same situation applies for hardware.  A reboot often corrects issues that are seen when there is a hardware problem or a driver incompatibility, but that doesn't mean that the hardware isn't the problem or that the drive is fine, look elsewhere.  All it means is that giving the computer a nap at least temporarily corrected the problem.
 
No offense, but it seems like you defend Sonar at every turn as if it's perfect.  It's not.  And it has different problems on different systems, with different hardware and drivers.  If, for example, the driver for a video card happens to interfere with Sonar, it doesn't necessarily mean that the driver has the defect if Sonar is the only application where there are problems.

With all due respect Blades you didn't read my post carefully. I said it can't be Sonar. I didn't nail down the issue to a specific driver either.

I cleared all Sonar processes and disabled a load of other stuff like antivirus and the problem persisted when restarting Sonar. The only thing that cured it was rebooting which resets drivers and all of a sudden the symptoms stopped.

It's a pretty safe conclusion then that the issue is outside the sonar environment otherwise the issue would have resolved itself with a simple restart of Sonar within windows and without a reboot (demonstrated to me it's most likely at level zero at kernel level). Furthermore most people don't experience this issue and yes it is that simple. I don't know what you mean by 'taking a nap' however power saving is off.

Please forgive me stating I've been working in IT since the 90's and I have a degree in it, I'm not saying I'm a genius but I do have a pretty good grip on technology as I've pretty much done every job there is around the field. As far as defending Sonar at every turn I suggest you look here. If an actual bug can be proven I'm more than happy to document it.

http://forum.cakewalk.com...aspx?m=3009969&p=1

CakeAlexS
As far as defending Sonar at every turn I suggest you look here. If an actual bug can be proven I'm more than happy to document it.

http://forum.cakewalk.com...aspx?m=3009969&p=1

IMHO Alex has a balanced view of Sonar. He recognizes both its strengths and its limitations. I presume the strengths outnumber the limitations, or he'd be using something else 
 
As to the troubleshooting, I'll leave that to the professionals but I think I understand Alex's point about the difference between restarting Sonar and resetting the drivers.

Thanks Craig. I've used pretty much all the major Daws and Sonar simply does the job and is my Daw of choice. Of course it can be improved but so can anything including my crappy posting :) One thing I did regret is not analysing the issue in more detail (I did rule out Sonar though) so I could rule out what the specific issue was but I was on a deadline.

CakeAlexS
Please forgive me stating I've been working in IT since the 90's and I have a degree in it, I'm not saying I'm a genius but I do have a pretty good grip on technology as I've pretty much done every job there is around the field.

And you still do not know what application can do to drive system crazy till it is rebooted? I do not mean bugs in the system, I mean wrong use of the system.
 
And if you think my question is theoretical, no. I was forced to work with one program which did that with graphic system. And many times with other system components as well. In one case you could simply wait 15 minutes before program restart instead of rebooting the computer, no system bugs involved, "following standards" pure (this example is from networking).

It's a pretty safe conclusion then that the issue is outside the sonar environment otherwise the issue would have resolved itself with a simple restart of Sonar within windows and without a reboot (demonstrated to me it's most likely at level zero at kernel level)

I do not claim there is this bug in SONAR. But I claim your statement is naive...

By all means use Cubase... Jeepers. 
 
Using that as a threat to Cakewalk is a joke IMO.