• SONAR
  • How do I diagnosis random playback / recording stops?
2014/06/25 00:35:04
yodermr
Seems to happen recording or playing a simply stereo channel with one Ozone plug - nothing else
 
Sonar X3e used mainly for mastering (1 stereo channel with Ozone)
 
Win7 64bit
i7 3770 3.4 Ghz
8 gig ram
 
Thx
Mark
2014/06/25 11:05:50
dlion16
ozone is probably too processor intensive to be used as a real-time plug.
 
clone the track, archive the original, then bounce the copy to clips with the ozone, then uncheck the ozone in the copy.
2014/06/25 11:26:53
CJaysMusic
Raise your ASIO buffers or WDM slider. Your PC and sound card driver setting cannot handle the current load of your project.
 
Thats all this is and hopefully you have a recommended sound card and not using the onboard sound chip. 
 
CJ
2014/06/25 11:27:34
yodermr
Sorry not following you. Real time plug in? I'm not using it while recording. I am using it on one pre recorded track. Only one plug in in use (Ozone) on the main buss. 
2014/06/25 11:30:11
yodermr
Cjays... Current load of the project? Well again... One stereo track, one plugin in. What might be the hardware requirement be to handle this?. My sound card is an Lynx Aurora 16 & Lynx Two using the AES16pci card
 
2014/06/25 11:32:01
CJaysMusic
You said it happened in recording, so this is 'Real time' Playback is not real time. Got it?
Just do what i said to do, and it will fix it.
 
Cj
2014/06/25 11:32:13
yodermr
Additionally, I have run >24 tracks all with plugins, with a few of them being Ozone with no problems. This is a new issue. I thought some Windows update inserted some process that interrupting now
2014/06/25 11:33:23
yodermr
Sorry, yes in recording one stereo track but not using (not sure the name) live plugin loop back to hear the plug while recording
 
2014/06/25 11:39:59
Anderton
First, isolate the issue. Check whether the stop is associated with the audio engine stopping (I'm pretty sure it is, but it's always good to be certain how the problem manifests itself).
 
It's possible to set latency low enough to get dropouts with almost nothing in a project. Set the latency to 256 samples and see what happens. Ozone can be very processor-intensive, so if you have buffers set to something like 48 or 64 samples, then and having other processes running on the computer (e.g., internal wi-fi if it's a laptop) could be enough to push it over the edge.
 
 
2014/06/25 12:15:01
yodermr
Thanks I will check my settings and report back. Thought I had it properly tweaked as I have run much high plug / track load before. And now the issue appears when nothing has changed except a few Windows updates
 
Thx
M
12
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account