Hi, 
 
As per the title. This just started the other day. Something which preceded it -- though I don't know why it would matter, but still -- was me opening a Hopkinton project in X3e. (There were no problems running it in X3e, the project was simple and did not involve any post-X3e functions). This problem is not specific to this file or any of its later versions; it's a global Sonar problem. 
 
To clarify, I don't mean putting the PC to sleep while Sonar is running. I mean, if I boot the machine, I can use Hopkinton, save close, exit, then put my PC to sleep, and wake it up, but then cannot launch Hopkinton in any way. Clicking the Sonar icon in my taskbar, a SPLAT shortcut on my desktop, or even the SONARPLT.EXE itself have no effect. Double clicking on a Hopkinton file  in Windows Explorer give me an hourglass for an instant, then nada. 
 
I can reboot the PC and then launch Sonar as usual.  But I put my PC to sleep, vs. shutting down, for a reason -- I don't want to reboot unnecessarily, as I'm told this can age a PC.  Hopkinton already requires enough reboots to workaround other problems for me, gets really old in fact, so I would really want to tackle this one at least.
 
Can anyone advise? 

Hi. I am just guessing that SONAR.exe is still running in the background, and has lost its connection (due to sleep mode). Try killing it (SONAR) in task manager, and reopen SONAR. 
All the best.

lingyai
Hi, 
 
As per the title. This just started the other day. Something which preceded it -- though I don't know why it would matter, but still -- was me opening a Hopkinton project in X3e. (There were no problems running it in X3e, the project was simple and did not involve any post-X3e functions). This problem is not specific to this file or any of its later versions; it's a global Sonar problem. 
 
To clarify, I don't mean putting the PC to sleep while Sonar is running. I mean, if I boot the machine, I can use Hopkinton, save close, exit, then put my PC to sleep, and wake it up, but then cannot launch Hopkinton in any way. Clicking the Sonar icon in my taskbar, a SPLAT shortcut on my desktop, or even the SONARPLT.EXE itself have no effect. Double clicking on a Hopkinton file  in Windows Explorer give me an hourglass for an instant, then nada. 
 
I can reboot the PC and then launch Sonar as usual.  But I put my PC to sleep, vs. shutting down, for a reason -- I don't want to reboot unnecessarily, as I'm told this can age a PC.  Hopkinton already requires enough reboots to workaround other problems for me, gets really old in fact, so I would really want to tackle this one at least.
 
Can anyone advise? 

There's not enough proof to verify this.  Best solution on a desktop is to never use sleep mode. 
 

I don't know if it is stated anywhere, but sleep mode and Sonar do NOT get along - never did.
 
Many of us seem to go into power management options and turn off all sleep mode stuff.
 
Bob Bone
 

Your daw computer should be set to where it never sleeps and drives never stop.

kitekrazy1

lingyai
Hi, 
 
As per the title. This just started the other day. Something which preceded it -- though I don't know why it would matter, but still -- was me opening a Hopkinton project in X3e. (There were no problems running it in X3e, the project was simple and did not involve any post-X3e functions). This problem is not specific to this file or any of its later versions; it's a global Sonar problem. 
 
To clarify, I don't mean putting the PC to sleep while Sonar is running. I mean, if I boot the machine, I can use Hopkinton, save close, exit, then put my PC to sleep, and wake it up, but then cannot launch Hopkinton in any way. Clicking the Sonar icon in my taskbar, a SPLAT shortcut on my desktop, or even the SONARPLT.EXE itself have no effect. Double clicking on a Hopkinton file  in Windows Explorer give me an hourglass for an instant, then nada. 
 
I can reboot the PC and then launch Sonar as usual.  But I put my PC to sleep, vs. shutting down, for a reason -- I don't want to reboot unnecessarily, as I'm told this can age a PC.  Hopkinton already requires enough reboots to workaround other problems for me, gets really old in fact, so I would really want to tackle this one at least.
 
Can anyone advise? 

There's not enough proof to verify this.  Best solution on a desktop is to never use sleep mode. 
 

What do you mean? Do you think I'm making this up, posting as a cry for attention? It happens right in front of my eyes. That's why I'm posting about it.  Shall I make a video of this occurring? Would this represent enough evidence, your honor?
 
Just as irritating as the flakiness of this software, is this very kind of reflexive bug denial one encounters on this forum --- "I ain't seen it, must be your fault". 
 
If you've nothing useful to say, why not just stay mum, eh? Thank you. 
 
It's a laptop, not a desktop.  And there must be a reason why after a year it suddenly started this week, despite no changes made to the system this week. 
 
 
 

robert_e_bone
I don't know if it is stated anywhere, but sleep mode and Sonar do NOT get along - never did.
 
Many of us seem to go into power management options and turn off all sleep mode stuff.
 
Bob Bone
 

Thanks Bob, though again, it worked before fine. Can you imagine why this might have started now?
 
If you avoid sleep mode, does this mean you fully power down when finished a session, and boot up when you want to resume working?  Or do you just leave your PC on?
 
I've never encountered a program which demands this kind of treatment.
 
Zarrg, thanks for your post as well -- I'll check and see next time if what you say is the case. 

Resonant Serpent
Your daw computer should be set to where it never sleeps and drives never stop.

Meaning the DAW PC should be on 24/365 for as long as I own it? 
 
Where did you hear this?

If you really must use sleep mode, you could try disengaging the Sonar audio engine before bedtime, see if that helps, but I must agree that sleep mode has never worked very well on my Sonar desktop system, so I have it turned of in Windows power management to avoid potential issues.

 
Sleep works fine for me on Kingston, I do it countless times a day.  Hibernate, however, is another matter.  I haven't tried it in quite some time as I had constant problems dehibernating, but I believe it was my pci soundcard's fault, not Sonar's.