• SONAR
  • Play, record, stop lag in Platinum
2017/04/06 19:01:50
rodreb
I am experiencing a 1 to 2 second lag when hitting play, record, or stop. Sometimes, but not always, the blue spinning ball thing appears during the lag. I have shut off all FX and no difference. This has been happening for quite a while so, it is not related to the latest update. There was a time when Platinum was very snappy but, not recently.
Any thoughts or advice would be welcomed.
Specs - Windows 10 64 bit, Sonar Platinum 64 bit, i5, 8 gb RAM, NVidia Gforce 620, Focusrite Saffire Pro 40 & Octopre.
 
2017/04/06 19:11:33
chuckebaby
hey Rod.
I would first make sure you have not pressed the "Pause/Break key by accident. I've done this before.
Its sure to slow things down.
Then give a look for any updates to the Focusrite Saffire Pro 40 ( probably not but worth a shot.)
If not maybe even consider to reinstall the driver, could have become corrupt.
 
What if you try changing the buffer size... has that made any difference ?
 
 
2017/04/06 19:45:34
rodreb
chuckebaby: (Thanks for jumping on this, Charlie!) I will check the pause/break key. Saffire driver is up to date. Have tried many different buffer settings in the ASIO panel.
Interestingly enough, this hasn't effected my ability to use Sonar. In fact I am currently in the middle of three full length album projects for three different clients and am having no problems. Is it possible this could just be a graphics issue?  
2017/04/06 20:14:02
chuckebaby
very possible it could be a graphics glitch, when was the last time you updated your graphic drivers ?
I use to have a Gforce 610 but pulled it out and use onboard now.
Onboard on my rig has dual DVI's. and I just haven't seen the positives in having a outboard graphics card (unless im playing world of Warcraft or something ) But I could see the advantages to use outboard video if onboard Video was VGA single, exc.
2017/04/06 20:24:19
gswitz
Sounds like you have a high buffer and some hogs for VSTs. Bring down your buffer and bypass VSTs with the E key. Still laggy?
2017/04/06 22:37:03
rodreb
gswitz: As I stated previously, I have tried various buffer settings and have bypassed all FX - no change.
chuckebaby: I always keep my video drivers updated. I will have to check but, I think my on board graphics only supports one monitor.
2017/04/08 00:02:54
rodreb
Still no answer. I've checked and tried everything I know of, to no avail. As I said, it doesn't stop me from working but, it is soooooo annoying. Is it Sonar related? Is my hard drive dying? Is my video card dying? It's got me questioning everything now.
2017/04/11 00:08:58
tenfoot
Have you tested other driver modes Rob? Will your audio interface run under wasapi exclusive and does it still happen? I'm not suggesting you stay using that mode - just as a test.
2017/04/11 00:34:56
NotASpeckOfCereal
chuckebaby I just haven't seen the positives in having a outboard graphics card (unless im playing world of Warcraft or something ) But I could see the advantages to use outboard video if onboard Video was VGA single, exc.

 
Besides the support for dual mon if the onboard video doesn't, I don't see how an outboard video CAN'T help out your system when it a) has it's own processing and b) provides lots more memory. True that Sonar isn't a video game, but it's still updating a lot of tracks, drawing waveforms, and when starting up (play/record from start), might be asking for a lot of resources.

So a dedicated video card doesn't sound to me like it would be suspect unless the mfg is know for producing really buggy drivers. I suppose rolling back recent driver updates would be a quick check on that.
 
I might go through the Windows updates for the period during when the problems cropped up and back them out, one by one. Hit the View Update History link (Control Panel, Windows Update) and scroll the list looking for suspicious stuff, ignoring innocuous things like Windows Defender definition updates... something hardware related.
 
Sorry, I know that's not much help.
 
Speck
 
 
2017/04/11 02:00:54
emwhy
I see you're running Win 10. Did you by any chance switch your MIDI driver from MME to the new UWP engine? I tried to do that and it created exactly the problem you're describing.
 
 
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account