What's new

Plugins "falling asleep"

YaniDee

Senior Member
I don't know if others have experienced this, but I find that if I leave Kontact standalone or a plugin in my Daw (Cubase, FL Studio) idle for, say ten minutes or so, when I come back to it it's sputtering and missing notes, etc. This happens with both sample libraries and vst synths. It's like they've gone to sleep, and don't like being woken..I have an onboard hardware audio card, Delta 44, using it's Asio drivers or Asio4All drivers. I've checked for "allow device to power down" but there's nothing showing that option. I'm on Win 10, fairly fast computer. Has any one experienced this, or can suggest a reason or fix?
 
It could be possible your CPU is entering a low power eco mode after inactivity and then when you try to resume DAW use it doesn't wake properly. I've had to disable all that sort of nonsense on my processor and I think most others do it as well because of how Realtime CPU intensive DAW music composition is, the tradeoff is you pay a bit more on your power bill but you gotta do what you gotta do.
 
Sounds like this issue
I'm surprised I didn't see this, cause I've been meaning to look up this issue for quite a while. I wonder if there's some steps to take to improve this, I don't think my CPU is in any "eco" mode.
 
I'm surprised I didn't see this, cause I've been meaning to look up this issue for quite a while. I wonder if there's some steps to take to improve this, I don't think my CPU is in any "eco" mode.
You mentioned it occurred on VST synths that aren't Kontakt. Is that right?

It'd definitely be worth plugging your speakers into the onboard motherboard soundcard and routing asio4all to that and seeing if the issue persists so you can eliminate the Delta44 card as the problem.
 
I find my ram just dumps itself after a certain period, so I experience what you're talking about when the project is in the template, but not if it's just synths and percussion.
 
Top Bottom