algodon
Thanks again, Bob.  The settings are: input 2.3, output 3.0, and 5.3 roundtrip.  Does everything appear to be in order?
 
Stephen

I used to run that 'lean', but would end up getting dropouts with latency set that low.  I now use the following settings, and have no dropout issues whatsoever: Driver Mode = ASIO, Sample Rate = 48 k, Record Bit-Depth = 24, ASIO Buffer Size = 128.
 
The ASIO Buffer Size is a setting from the audio interface.  Some interfaces use a slider and/or drop-down for Number of Samples, to control the ASIO Buffer Size.  Whichever method your interface uses, the size of that ASIO Buffer will also affect the latency.  my total roundtrip latency is just a bit under 10 milliseconds, 9.3 - I believe, and that works very well for me.  
 
Just for a test - try adjusting your ASIO Buffer Size to get your total roundtrip latency to be just a little below 10 milliseconds, and see how your dropouts are at that point.
 
It is certainly quick enough to test.  Please note that it is recommended that you power-cycle your audio interface after making settings changes, to refresh everything.  (If USB-connected, you can also just unplug its USB cable and plug it back in).
 
Bob Bone
 
 
 

Agree with Bob, you may benefit from increasing the number of buffers. Those are pretty low latency figures.
 
Also to answer your direct question about WTR files. Both WOV and WTR files are part of the picture cache and can safely be deleted at the windows level. Select them in the windows browser and delete them. The files will be rebuilt on demand when a project is opened. Clearing the cache is not an unusual activity but as CJ indicated it is not a solution to the issues discussed in this thread.

Thanks for the replies folks.  Unfortunately, nothing changed as far as the dropouts.  All I can do is take solace in the fact that after about 3 hrs. of leaving the computer and Sonar on, the dropouts go away.  BTW, the reason I had my latency so low is that I use a drumKAT and several VSTs for percussion parts, and there's too much latency if I don't keep my buffer size low.  Bringing it up a bit still keeps the drumKAT working well enough, but didn't affect the dropouts.  
 
I really appreciate all of the help you guys have given me.
 
Stephen

Thanks for the replies folks.  Unfortunately, nothing changed as far as the dropouts.  All I can do is take solace in the fact that after about 3 hrs. of leaving the computer and Sonar on, the dropouts go away.  BTW, the reason I had my latency so low is that I use a drumKAT and several VSTs for percussion parts, and there's too much latency if I don't keep my buffer size low.  Bringing it up a bit still keeps the drumKAT working well enough, but didn't affect the dropouts.  
 
I really appreciate all of the help you guys have given me.
 
Stephen

Well - can you please detail which buffer(s) you brought up, and what you brought it/them to, and what the resulting total roundtrip latency value was?
 
There may be room to bring things up a little more, which may yet assist in reducing dropouts.
 
Also, have you run DPC Latency Checker?  It is freeware, and available at:
 
http://www.thesycon.de/deu/latency_check.shtml
 
You would download and run it, with Sonar NOT running, to get an idea of the basic ability of your computer to handle audio streaming, such as what happens with Sonar.
 
Please post back the details on the changes to the buffer(s) you made, and also please download DPC Latency Checker, run it, and post back what it reports after letting it run for a few minutes.
 
Thanks, 
 
Bob Bone
 

On my UPS not all the outlets are backed up by the battery. Maybe check to make sure the outlet your computer is using on the ups is in fact powered by the battery when AC goes out. On my ups unit there is a USB connection that connects to the computer which tells the computer when to shut down properly when the battery gets low.

As for dropouts since being shut down incorrectly, and Sonar being fine once letting the computer run for a while, sounds like something is going on for that first hour or so. Perhaps a raid mirror is failing and rebuilding? Or virus scan is scheduled?

Use event monitor and see if any processes are using a lot of resources. If so use google to look up the process to see what program it's associated with.

I got a drumkat. Pretty nice little drum pads. I can never get the hi-hat pedal configured to open close smooth though.