2017.5 Seeing Unusal Number Of Dropouts

Anyone else seeing anything like this?
 
It happens even when I have a very minimal setup such as for mastering... But I keep getting them (dropouts) and the reset start/stop engine don't seem to work after each incident. I must restart Sonar to get back to normal...
 
I do think I notice that it happens when I allow Sonar to sit in the background for a few minutes...?
 
I'm running a fully updated version of Win8.1 here...
 
Thanks...
 

I am also getting dropouts quite frequently. and crashes.  Sonar is getting increasingly unstable in my opinion

Judging by the fact that this thread has not lit up with people having similar issues since updating to 2017.5.... looks like it's something particular to your systems. 

What audio driver mode are you using.  are all Windows patches up to date.  Confirmed that all latest hardware drivers - including video.  No unnecessary background tasks eating CPU cycles.  Audio buffer time set too low.  What bit depth and sample rate are your projects at?, etc

Sonar is mostly running just fine.

I seem to be getting these now even when near nothing in the project and not running. Sometimes Sonar is in the background when it happens while i do some simple chore such as copying files.

All software is up to date and this did not strat happening until 2017.5

and Resplendence LatencyMon shows everything ok?
http://www.resplendence.com/latencymon
 
We'll look into it.
 
Keith

I'm getting a few more dropouts and crashed than usual after this last update. Seems to happen when I try to insert certain plugs (NI compressors, Izotope Neutron)in track FX bins.
Also, some of the instruments in Komplete 11 are acting strangely when I load them. Some will have no presets at first (which later show up), some just make a weird "flanging" noise that fades away then everything is good.
Of course, just had a major Windows update too, so there's that....

power saving?
 

It seems I recognize some of you guys from the forum sometime back, so maybe there is something similar about our systems.
I've also had more dropouts since the 2017.5 update.
In addition, I get an "Out of Memory" Prompt from time to time.  If I restart Sonar, the problem, more times than not, is resolved. On another occasion I was making a master wav file and I noticed drop outs or glitches more than in the past.  When I set the buffer to 1024 to eliminate the drop outs, the transport would not start.  The same with 2048. But, When I close and reopen Sonar I can get the transport to work.  In general, I have had to use a higher buffer setting than before the update on some projects, but not all projects.
 
i7-6700 @3.40GHz 16GB RAM - Steinberg UR44 - Novation Impulse 61 - JBL LSR308 Monitors - Sonar Platinum  64 & 32 - Harmor - Rapture Pro - GPO - Harmless - Z3TA 2 - Octopus - Primary vocal and voice mikes: AT4040 and Cad VSM-1 Tube.  Studio type: Open windows, birds, and next to a railroad track.



 
 

I just started having this issue two days ago... happens about three or four times per session.   The issues take place during mixing, not recording...hmmmm?  Might need to roll back...but I would sure miss those Quadcurve presets :(
 
Edit:   Not using Adaptive Limiter and latencymon reports everything AOK for audio

Adderoo
Switching of the Adaptive Limiter in the masterbus prevents the dropouts from happening.

Well there ya go.

Also keep an eye on the L-Phase EQ and Multi-band if you're having problems.

Same here ... but I noticed the L-Phase stuff being pretty demanding so they're on the "only when mixing at high latency" list.

I've been having some issues as well, but I was assuming "dropouts" (which may be a fairly vague term) was something with my audio interface, I froze tracks, archived tracks, streamlined plugins, and adjusted ASIO latency, didn't help. Granted, my current project is surely pushed to the max with plugins, but then I adjusted my midi playback buffers. I did this as a last resort and it actually worked for me.
 
I haven't had to adjust my midi playback buffers since I can't remember when . . . it's always been at 750 msec, for many years. Moving it up to 1000 msec buffers solved it for me.
 
I'm not saying this is the same case for everyone here, but somehow this latest Platinum update has changed something with my midi buffer requirements ? Just something else to try, if nothing else works for your projects.
 
And, yes . . . I've been blaming the new Adaptive Limiter as the possible cause for this . . . but switching back to Concrete Limiter, the issues persisted. By adjusting my midi buffers, I'm also able to run Adaptive Limiter in this crazy project, successfully.

PurpleNurple
You guys are not alone in this. I am dead in the water with Sonar now.

Just roll back. That's what the function was created for. So people such as yourself wouldn't be "Dead in the water".

I haven't noticed any difference myself. Everything is moving along excellent here. However im using Windows 8.1 so it could be something involved with Windows 10.

Keni is using a MAC machine running windows, so that's another layer to be considered. Another thing to remember is that windows updates can turn on previously shut down services and sound devices. I know that my AMD video card has audio output that conflicts with Sonar's operation. Sometimes windows turns it back on and I get weird messages from Sonar. I also have to disable my wi-fi adapter. After a big windows update I go through the entire system and see what settings have been changed.
 
There a lot of moving parts when the OS changes weekly and Sonar changes monthly.