I've seen the issue when windows sleeps (it dosen't matter if it's in sonar or not). My soundcard loses the sync (red), so i have to turn the soundcard off and on (hard reset), and the sync is back(blue).

Paul P

Jim Roseberry

Sleep/Hibernate are known to cause this issue in a DAW.
If you make use of them... the only solution is to reboot.

I'm interested in knowing why, so I can go about fixing the problem.
 
Sleep/hibernate lets you shut the system down without having to close everything you were doing only to have to setup everything again when you want to continue.  I find it odd that some don't see the utility of this.  I don't sit at my DAW computer all day long, only an hour or two here and there when I find the time.
 
My computer is water cooled (which means it has a pump) with 6 fans, a 140w cpu and three hard drives.  There's no way I'm going to leave it running all day long.
 
My issue is Sonar not being able to record off a soundcard that other programs can.  I'm trying to find out why.  One variable that I forgot to mention is that Sonar is using the ASIO driver while Audacity is using Windows Direct Sound, whatever that is.

 

It's likely that  the ASIO driver is the issue. Nothing to do with SONAR. I get an occasional problem where I lose sound after running Adobe programs.

John


Why wouldn't a save take care of having to setup your project?   

By setup, I meant everything I was currently doing on my computer, which could be anything, not just Sonar.

  Everything on my system works fine, sleep or not.  I don't need to sleep Sonar, closing Sonar before sleep and reopening it after would be ok.  The thing is, with normal use of a computer, which in my mind includes sleeping, Sonar (and perhaps all daws) always requires a system reboot before operating properly, whether it has previously been opened or not.  I find this archaic.

I will dig deeper following Acron and simonknight's information.  I wouldn't mind having to reset my soundcard, that would sure beat rebooting.
 

I have never viewed programs like Sonar as normal programs. To me they are like Autocad or Vegas Pro Video and Photoshop. These programs task a computer to its fullest. These type programs are not like word processors or Email. They use all sorts of devices and system resources. They should be respected as powerful programs that need the full attention of the computer. 

I have never let Sonar sleep or any other DAW. If I need to do something else and leave the computer and I wont be on it for a while I turn it off. If I am going to come back to it son I don't do anything unless it is to close Sonar. Otherwise the computer is left to run. 

I can see the need for sleep with a laptop or tablet but for a desktop not so much. 

I know that Windows is a multi tasking OS but that should not be the model for DAW use. Many people have computers that do only DAW work. They don't use them for anything else. When you open Sonar and load a project refrain from doing other things. Close Sonar when you are done using it. 

This is the way I work and you will notice you don't hear a lot from me with issues. Could it be because I respect the DAW?

First time I've been accused of lacking respect for a software application :-)

I've made a bit of headway. When I use my Mackie Blackjack interface (ASIO) everything is fine and dandy. I can put everything to sleep with Sonar open and when it wakes back up it'll resume recording no problem. Being usb powered, the Mackie is getting a hard reset each time, which may be helping.

With the Soundblaster (ASIO) [I know a lot of people don't want anything to do with Creative, but for the moment I'm giving them the benefit of the doubt, until proven otherwise] it actually worked a couple of times during my trials, though sometimes at reduced volume. It hadn't worked at all before. Windows and at least browsers apparently have no problems with the card. I don't yet know what happens to the PCIe bus and cards plugged into it during sleep.

I have to study up a bit on how audio is handled and routed internally to Windows. I'm missing some big pieces of the puzzle which makes testing kind of vague.

I believe software should be solid enough to work as is without having to baby it or tinker endlessly with it. It shouldn't be possible to break it, at least not easily. My benchmark is that a little old lady should be able to use an application. I've worked as a software designer and programmer on large programs in another life so I have an idea of the complexity involved. I feel sorry for the little old ladies of today.

Paul P

I believe software should be solid enough to work as is without having to baby it or tinker endlessly with it. It shouldn't be possible to break it, at least not easily. My benchmark is that a little old lady should be able to use an application. I've worked as a software designer and programmer on large programs in another life so I have an idea of the complexity involved. I feel sorry for the little old ladies of today.

If a little old lady is seriously interested in audio production to the point of dropping $400 on a DAW, then she's going to have to deal with a lot more complexity than just the DAW itself. She's going to have to learn about sample rates, compression, EQ, side chaining, and a ton of other technical stuff associated with audio and plugins. So if she can wrap her head around that then I'm sure she can wrap her head around Sonar. Your "benchmark" is ham fisted to say the least.