• SONAR
  • 2017.5 Seeing Unusal Number Of Dropouts (p.3)
2017/06/20 16:17:30
Steve_Karl
Also keep an eye on the L-Phase EQ and Multi-band if you're having problems.
2017/06/20 16:20:18
Keni
Steve_Karl
Also keep an eye on the L-Phase EQ and Multi-band if you're having problems.




Thanks Steve...
 
Will do. I get spoiled as I so rarely experience such limitations here...
 
2017/06/20 16:22:38
Steve_Karl
Same here ... but I noticed the L-Phase stuff being pretty demanding so they're on the "only when mixing at high latency" list.
2017/06/20 23:29:47
Keni
OK...
 
Does look as though the AL is the culprit here. I don't get any dropouts at all with any projects that it is not in...
 
I can live with that for a bit...
 
2017/06/21 04:00:02
noynekker
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.
2017/06/21 15:11:57
PurpleNurple
You guys are not alone in this. I am dead in the water with Sonar now.
2017/06/21 20:14:39
chuckebaby
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.
2017/06/21 20:31:01
Steve_Karl
It seems it would be good to know specifics about which OS is in use,
for people with problems
and people without problems.
2017/06/22 00:06:11
ampfixer
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.
2017/06/22 00:19:41
Keni
Yup! Hybrid land here, but you know what? It has run so well on 2 different machines for many years now. I experience very few glitches...

I also never update the OSX so its in a very stable place. The machine bootd up and stays in win8.1... dual 6-core xeons, 64G RAM and 4 500G SSD's and i rarely have to adjust latency or experience performance issues such as dropouts at all... so this is a rarity here...

Outside of design issues i have no other problems in Sonar... well, it does crash a lot when closing/opening fikes as i still depend on a few 32 bit vst's.... but im never hurt by that! ;-)

👽🎸🎶
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account