Maximize Windows 8.1 Desktop PC For Sonar X3 Studio

Well, i'll chime in.
 
I believe it starts by knowing the system being used, and devices Put into it...from Bios settings, to windows and drivers....it all helps to know what you want to do with the machine, and what is not necessary for that , that may be installed as a device, with driver, or bloat ware preinstalled...hard drives, efficient power supply and surge protection.
 
And software that may interfere with the Process of X3 Studio...  Like problematic software, virus programs, firewalls (if causing issues), and or networking devices, internet/ or any "conflicting devices, or if having issues with other audio devices being used in Sonar" and physical IRQ sharing be checked out, and reduced...etc, with audio devices...Yes even ATI video cards can cause issues, with the HD audio being used, if so, with other audio onboard the MB, or other add on audio cards...So dependant on what and how you setup your system, can be the be all or end all.....
 
So, lots to think about....Not much in the description as to what you are using as a audio device, or hard drives, or add ons in your posting , so excuse my vague widely scoped replies  that apply to the base of all systems.
 
The more Memory you have the more reliable I find PC systems to be..I would definitely go 16gb ram.
The cpu seems to be the work horse in doing the record and playback , use of Plugins, and utilizing the devices, and running services for the OS...ect with sonar.., and running the engine of that.
 
So a wise choice is being over looked, or over ruled....By not updating the system cpu...things will slow down when bogged down with work loads...but it should work ok if all things are made easier for that to be done, without interruption by other tasks or services running in the background.
 
Knowledge of IRQ usage.
 
Some say it is not important anymore to worry about this IRQ usage, as Windows has virtual ones....But the physical truth is there are only so many of them on the motherboard , that page the cpu to be used...too many shared IRQs will cause hick ups in the processing of..X Y Z....and use of devices, as they get interference from this sort of paging, and calling services to use those devices or run them in background.
 
If something is asked to do a task, does not get done in time,...or is held until free use can be made of the cpu...it could cause glitches in the work load being asked to perform...if it does not cause too much issue, it could result in a glitch in audio.
Or too much could cause the system to hang...and become none responsive...and or crash, if a conflicting event occurs.
 
So that would be a start to understand.
 
Tweaking the services, like automatic updates...Using: "msconfig" and hiding all MS services first, and turning off third party auto updates, and sorting what gets loaded on boot up...could help stop unwanted actions being done by third party apps running on the OS, behind the sonar software.
And yes I turn off windows updates, and do it manually  .
 
Turning off redundant devices in control panel/ "system"/ "devices manager"....before using Sonar.
One can go a step beyond by defeating some things (devices not being or going to be used) in Bios.
 
So knowing the system you have is most important, and what you want to do with it.
And find the best setup to do that with....that system.
 
Write down your changes....Keep a log.
 
That is where I would start.
 
Oh yah, the usual, turn off the power saving features in control panel/power options,keep hard drive always on, and screen savers, and such off,...and any high performance tweaks for video " Best performance settings?"...might help to make it plain jane with no acceleration or just a few...could help gain a more robust and pleasant system performance with Sonar....but you have to test that out one step at a time....
 
Best of luck.
 
I tried this guy's tweaks out on win 98/xp/win7...: http://www.blackviper.com/service-configurations/black-vipers-windows-8-1-service-configurations/
 
But a lot of knowledge as to what you want to do...and when making tweaks always write them down, so you can restore things before updating the os.
other wise you will get page errors and corrupt updates.
.

Can you even see the CPU/Hard Drive usage meters? I used to see them in the bottom right in 8.5. I do not see a usage meter in X3.

Sir Les-Thanks so much for the comprehensive info.  I appreciate you taking the time to put that together for me.  I will look it over, although I must confess it seems a bit complex for my moderate PC skills.
 
Steve C-It is a combination of mostly MIDI/virtual instruments and audio to a lesser degree (maybe 1 or 2 vocal tracks).  Interface is a Line 6 Pod Studio UX2.  A few weeks back I inquired about ASIO drivers only to be totally confused about them.  I use the UX2 drivers to record audio but must revert back to ASIO4ALL to mix.  Many here as well as other equipment forums advised me that ASIO4ALL isn't the best driver to use but it's all i have available.  I monitor through cheap Ipod type speaker (all I can afford and sometimes headphones), so with this setup I'm kinda stuck with the ASIO4ALL.
 
koikane & Kev99-I know where the meters are.  I have to run a project later to tell you what they say, but if I remember correctly, the bottom meter is at around 50%.
 
 
Thanks All!
 
John B.
 
 

williamcopper
If you do some internet searching, try replacing your word "maximize" with "optimize" ... you'll get better search results.

That's true!  I've been using the wrong word.  You're right.  Thanks, williamcopper!

oh Johnbee58...Black vipers suggestions should be researched as to what those tweaks do, and if you need them services or not is dependant on your system and needs....So think it out slow and do a lot of asking, and seeking what tweaks he suggest do what to a system...and what is reliant on services being turned off, or **made manual**, instead of auto load at boot up.......if done....sometimes other services are tied together, and if you only defeat one from being loaded at boot....the other needing it gets screwed up and cannot load or waits for the other...causing page file errors to be written, and can cause more problems when doing so....So a give and take or make worse it can do younge Jedi....So focus.
 
Just take your time, write down what you do...test it...see if any improvements are noted....do the next one you feel is causing issues, if they persist, until you find the buggers that slow down or cause cpu usage to be over loaded, when using Sonar...If possible....ect...
 
Each system is different...and different software needs certain services...So be mindful, and do the leg work...only you can fix it at your local, unless you call in the geek squad!...and that costs moula...wink....and tweaking slow but sure, and right, can be undone....so no worries?....Right?
 
 

Johnbee58
Sonar X3 does run on this setup and I can get about maybe 10-15 channels running before I start to get the "crackling" sound indicating an overtaxed processor...

A crackling sound can be caused by several issues, and it not always indicative of "overtaxed processor." Some plugins can do this, as well as what you are doing at the time. I saw "ASIO4ALL" in your comments which has been hit-or-miss with many (the threads posted are often the misses, of course).
 
Things to consider...

1. When tracking, you need low latency, so audio buffers set low helps this... the counterpoint with low latency is it can become MASSIVE CPU usage (depending on plugins/synths used). When tracking (recording) a project with plugins already inserted, hitting "E" to bypass plugins will free CPU.
2. When mixing, the ASIO buffer can be increased... I track from 64-128 samples, mix from 128-256 typically, but "heavy handed" plugins can require mixing even higher to reduce CPU loading. Some plugins also have "look ahead" features which use more resources since they need to anticipate what is coming... they cannot be used with low audio buffers (simple fact) without causing issues.
3. ASIO4ALL is a "red flag" to many, as it is really using WDM mode, but "looks like" ASIO to other software. These drivers are invasive, and can actually cause issues with genuine drivers. If drivers exist for your interface, it is highly recommended to use them and completely uninstall ASIO4ALL (even having these installed can cause grief).
4. Keep an eye on when you insert plugins and how CPU/performance changes. Some are CPU heavy (especially at low buffers). If hitting "E" improves things dramatically, consider either using another plugin or increasing buffers.

To your original question... unfortunately there is no "cookbook" reference/solution for this... the user must understand what they own, what it does, and how it affects things.