• SONAR
  • My Audio Dropout Tale...
2013/05/25 08:30:34
synkrotron
Hello Peeps

As some of you are aware I have been upgrading to Windows 8 in the last week or so. I went for a clean install because I wanted to install onto a larger SSD and I felt I needed to tidy up my Sonar install anyway and get rid of some of the baggage from installing some X1 demo stuff.

A clean install is quite a lengthy process. For me it was anyway, because I have many third party VTS's and VSTi's as well as various expansion libraries and they all needed installing,re-registering and then testing.

Anyway, I finally got to the stage yesterday afternoon where I could open an existing project. The first thing that I noticed was that the first CPU core was more than double the activity of the remaining seven. I must admit that I was a little disappointed with this because I was led to believe that Windows 8 managed core usage a bit better and was one of the reasons that I upgraded to W8. Here are some pics showing the CPU usage according to Windows Performance Monitor and Sonar's own CPU monitor:-







Both of the above screen shots were taken at the same time. As you can see, CPU 0 is running at around 10%.


I thought I'd have a go at fixing that. I should say, though, that I have already turned of "core parking" so I don't know whether that has anything to do with this issue. I should perhaps turn it back on, but I always though that turning it off was supposed to ensure that all cores are used and never parked. I ain't no expert though and could be a mile out with that assumption.


I had a look at the various tweaks I could make with my audio device settings and other preferences in Sonar, like changing the ThreadShedulingModel = 2, but nothing seemed to work really. I'm pretty crap at this sort of thing nowadays, and I change more than one thing at a time and then forget where I'm up to.

Even changing the latency settings for my QUAD-CAPTURE didn't really help. I even tried shutting down various bits and pieces in my Windows Startup just in case it was something there, although when I looked at the CPU usage, they were hardly taxing the CPU's at all. I then had a look at my graphics card settings and made sure that everything was set to use the NVIDIA device. Still no real help.

In one particular project I would always get audio dropout at exactly the same place. I could have tried freezing some synths and effects but I didn't want to do that. This did not happen when I was using Sonar on Windows 7, and the reason I spent loads of dosh on my current DAW was so that I didn't have to keep freezing and thawing my synths.

Then, the last thing I tried was changing my power settings. What a plonker... Once I set the power for High Performance I stopped getting the audio dropouts. At the place I was getting the dropout CPU 0 still peaks quite high but not so high as to stop the audio.


So, there you go... I suppose I should make notes of what I do and there is no doubt that I went through the same process with Windows 7 but I can't remember, as usual. My brain is getting a bit addled as I head towards my dotage........


2013/05/25 10:24:30
gcolbert
CPU 0 will always have a higher load than all of the other CPUs.  It is managing the context switching (being the boss of the other PUs) which requires work.  Load up a project with a bunch of synths/effects and things will show a more even distribution of work load, but CPU 0 will always be higher than the others. In fact, the more processors you have, the greater the workload is on processor 0 to perform context switching.

Sonar does spread out better with WIn 8 than it does with Win 7.

Glen
2013/05/25 11:54:31
synkrotron
Thanks for that insight Glen
2013/05/25 13:01:04
joden
Did you try turning off the "exclusive.." tag?
2013/05/25 13:09:15
synkrotron
Hmmm... No, I didn't, and I wouldn't know how to. I'll have a look...
2013/05/25 13:26:40
joden

- Right click on the speaker icon in the system tray next to the clock.

- Choose Playback Devices.

- highlight the audio device output you want to change and choose Properties

- Click the Advanced tab

- Uncheck the top option to disable Exclusive Mode

You may need to repeat this process for the Recording tab.

You will need to reboot to apply the change. That's it... Windows will no longer hang on to the device now.
2013/05/25 13:37:09
synkrotron
Okay,

In the Exclusive Mode part of the dialogue box there are two options:-

Allow applications to take exclusive control of this device and

Give exclusive mode applications priority

So, you are saying to uncheck the top one, and then the second one becomes greyed out.

I'll try that, but I can't understand why. I assumed that I would be giving, Sonar in this case, exclusive control of my sound device, and in Sonar, Preferences > Playback and Recording, I have unchecked Share Drivers With Other Programs, which I thought to mean that Sonar would take exclusive control of my audio device.

I'll give it a whirl anyway and let you know how I went on.


Incidentally, I always turn off Windows system sounds.

Thanks again.

andy
2013/05/25 13:47:27
joden
Actually it works the opposite - it gives the OS control - which over-rides anything you may have set in Sonar..
Once you open anything in Windows that accesses the device chosen as the default sound device, that's it - it REFUSES to let go of it for anything else to use.
2013/05/25 15:13:35
synkrotron
Brilliant joden, thanks for that. I've not had a chance to do it yet cos I'm busy with other things...
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account