Not the keyboard or mouse. I changed batteries anyway, but everything else was working, just not any transport control, then all faders/knobs had no affect, then I had an issue where saving, didn't save anything. All other apps like Word and Excel, Premiere Pro, etc, all behaving normally. Just Sonar. But I've created a new project, brought in all the wave files from the 'bad' project, without any plugins, and everything is completely normal. Start adding plugins, and things start to just go crazy and I have to shutdown the PC entirely to get the project working again.
 
I'm going to re-install my scarlett driver, video drivers, cleanup the discs and defrag, and make sure my RAM and CPU are being managed and working properly. Everything is fully updated and I've scanned for any malware. Nice sunny Sunday, coffee pot on, bit of music going in the background, hopefully set the environment for a successful day !!!  I will post again if I can't find what's wrong. cheers. Dave.

reginaldStjohn
I have had occasions where the transport starts responding very sluggishly. Sometimes it has gotten so bad that when I hit the spacebar to start or stop playback I thought that it didn't work because it takes several seconds to respond. I don't know what causes this and usually a restart of Sonar helps but not always.
 
I have always been able to control the transport with the mouse however so my experience does not completely mirror your description.

reginaldStjohn
I have had occasions where the transport starts responding very sluggishly. Sometimes it has gotten so bad that when I hit the spacebar to start or stop playback I thought that it didn't work because it takes several seconds to respond. I don't know what causes this and usually a restart of Sonar helps but not always.
 
I have always been able to control the transport with the mouse however so my experience does not completely mirror your description.

I have had this sometimes too, usually just overloading with too many plugins going on. I try to keep everything to minimum through the phases to keep it in check, but this is different. It's like certain functions within Sonar are simply not responding anymore. Thanks for your reply..

MacFurse
The other odd thing is the buffer size in mix control for my scarlett had changed to its lowest setting. I never change it, leaving it at 10ms midrange because I don't ever monitor the input.

 
With SONAR, the main issues involve third-party plug-ins and drivers. Don't know if you've updated your Focusrite drivers lately, but check whether an update is available. Historically, there have been various examples of strange SONAR behavior that disappeared when audio interface drivers were updated.
 
And of course, the lowest latency setting may be too low, and causing the kind of issues when the sample buffers are unhappy. It's important to remember that sample buffers are a moving target. They can be "on the edge" and working, but then the computer runs off to do something else and you no longer have enough sample buffers. 
 

I have the current Focusrite driver Craig that has been out for a while now. When win10 came out, there were a number of problems, but things settled and the old driver was still the one to use. But, I've just unistalled, reinstalled etc, and still having the same issues. Gone through as much as I can software wise, now I'm looking at hardware....

I have two evo 250g SSD's and the one I use for audio/samples etc has read/write errors. It's only 12months old and has 130g free, so I have no idea why. I've heard of issues when there are heaps of read/write's/delete's going on, but this is just data storage for projects and sample access, and almost entirely only used for Sonar. Nearly everything else is on another HDD, and when I store old projects on my main backup HDD drive, I remove them from the SSD, but it's not a lot. So, disappointed that an SSD has failed so quickly. Hope the other is OK, it hosts the system and program files. At least I do have a reasonable backup routine and have not lost anything. Just time and a bit of face.
 
Thanks for the help. Considering now whether to replace the drive with another SSD or just a good old HDD. I've loved the fast access, but not at this price.
 
cheers. Dave.

Make sure TRIM is enabled for your SSD, and your system doesn't think it's a hard drive so it tries to defragment it all the time...I dunno, that might help.

Didn't know that TRIM command, but it is enabled. I've reformatted the drive and it appears to be working OK. Maybe, it was just too much in one go for sampletank3 and Miroslav 2 that I did last week. Pretty big files and installations. I think I will replace it with another bigger one, and put this one to work mirroring my system/program SSD and see if it behaves itself for a month or two before using it for access storage again. I guess the durability of SSD's is still a grey area. We all hope they never fail, but who knows. At least I'm back to work again. Was the wrong timing a couple of days ago and I confess to panicking just a little   Thanks again. Dave.

Anderton
Make sure TRIM is enabled for your SSD, and your system doesn't think it's a hard drive so it tries to defragment it all the time...I dunno, that might help.

what is the trim command ?

http://www.windowscentral.com/how-ensure-trim-enabled-windows-10-speed-ssd-performance
 
Apparently this works for Win 7 & 8 too (see end of article).
 
Cheers, Peter.

chuckebaby

Anderton
Make sure TRIM is enabled for your SSD, and your system doesn't think it's a hard drive so it tries to defragment it all the time...I dunno, that might help.

what is the trim command ?

If enabled, when you delete anything, it also 'wipes' the space clean, ready for writing. If it is disabled, before something can write, it must delete the 'space' first, so it takes longer. It keeps the SSD 'clean' as you delete. But I think this refers mostly to older SSD's. Doesn't hurt to check to see if they are enabled. Could make a difference.