Windows Optimizations-guide working with DAWs and plugins!

General discussions on songwriting, mixing, music business and other music related topics.
Post Reply
User avatar
Freddie H
Member
Posts: 510
Joined: Fri Apr 08, 2011 7:59 am

Windows Optimizations-guide working with DAWs and plugins!

Post by Freddie H »

I have made a Windows Optimizations-guide working with DAWs and plugins that has all the right and valid information, how to setup computers running windows system. Many have no real knowledge about this and there are tons of websites on the Internet state all kinds of bad advice and tweaks that often are counter productive instead of fixing anything.

I hope my guide will help you and answer some of your questions you might have.



AERO on Windows VISTA, Windows 7 Windows 8.1, Windows 10 - OS-X Cocoa Frameworks


AERO need to be ON to direct all graphic processing to use graphic card -GPU instead of the CPU. You don't want to use the CPU for the graphic representation in windows. Today, there are non benefits to disable AERO, just the opposite.

Any visual you see in windows are 3D,2D, API calls, GDI and DirectX and Windows programs/ apps include DAWs use your graphic card to run all 3D, 2D, API calls, GDI and DirectX visual acceleration in windows that are then connected to windows visual and graphical representations called AERO.


All graphical representation in windows is handle 100% by the GPU and the RAM on board of the graphic card when AERO is turned on. If you turn AERO OFF, all graphic visual get directed to the CPU again. (old behavior). Today that doesn't work because graphical visual in windows are programed and based on AERO and direct API calls, resulting in errors working with Windows, DAWs and other programs if you have AERO turn OFF.




API-graphical calls


So what is API calls? There are important technology included in Windows AERO interface that are very important part of windows interface. There are direct connections to the graphical representations that is called direct API calls. Developer use direct API-calls in example Cubase and other programs and the API-support is available in the form of the Windows Software Development Kit (SDK). SDK providing documentation and tools necessary to build software based upon the Windows API-calls that are associated to the Windows interface. Microsoft has provided the DirectX set of APIs as part of every Windows since Windows 95.


DSP coding will just increase every day so we will see more GPU based coding and add of more functions to the audio plugins use the GPU processing in example Cubase and Native Instruments in the near future. So it can be good idea to invest in a better graphic card without going crazy. In fact already today many 3 part manufactories base all their GUI code and API calls around AERO. This is true since Windows Vista and GPU processing and directed to the GPU and API-calls are used on both Windows VISTA 7 / 8.1, Windows 10 and OS-X, Linux and Ubuntu . On OS-X you can't disable their coca framework (Open-GL) and that is a good thing. I hope Microsoft will do the same and take away the legacy option so you can't disable AERO in the near future.



Windows XP background - History.


On Windows 95, 98 and XP all graphic were directed to the CPU only. On XP and older systems, windows and programs graphical representation and processing were directed to the CPU not the GPU on the graphic card.

There for it was recommend to use as so low graphic as possible because it took away CPU resources from the DAW programs and plugins. Its because all the programs, plugins and windows graphical interface shared the CPU. Today that old legacy behavior and operation is history.




About Process scheduler on XP to "background task".


This old tweak must be the most confused tweak since XP windows.
That tweak has been used and abused since Matthias Carsten at RME come up with this great tweak on XP only.

It was meant to be used with specific RME hardware on XP platform only to provide better low latency from 23ms to 3ms. Even Mattias Carsten that is the original founder of this tweak say as I do and Microsoft and all the tech Gurus in the world say the same thing; ---> on VISTA, Windows 7,Windows 8.1 and Windows 10 it should be set to PROGRAM.

Audio or ASIO are not a background task in windows.



MIDI


Some people ask if MIDI is a background task? No, its not a background task either.
Its a real time operation. MIDI messages are made up of 8-bit words, and are transmitted serially at a rate of 31.25 kbaud.



POWER Schema


POWER Schema shall always be set on "Performance-mode" even for Laptop. Check in "Device manger" manually. Make sure in "Power-management" on all USB port isn't set to sleep/disable.



BIOS

Disable all Speed step, C-wait and Sleep.
Hyperthreading shall be set to =ON
Turbo Mode can be ON as default. In some rare cases you can turn Turbo mode off.




UAC-User Account Control


You can go ahead and disable that in Windows VISTA, Windows 7 and Windows 8.1. In Windows 8.1 its no needed as in Windows 8.1 has another kernel core protection further down inside the core base that has stronger protections against bad code then UAC.



Windows hibernation

Windows hibernation can be a good idea to take away to free up space especially if you use SSD on /C: Windows.
Check the Internet how to do that.



Virtual Memory -" page sys"- settings.


You'll receive many different opinions on how to deal with the page-file. Some will say that you should completely disable it. Their logic goes that Windows is inefficient at using the page-file, and if you have plenty of memory you should just disable it since RAM is a lot faster than traditional hard drives. By disabling Virtual Memory, you are forcing Windows to use the RAM instead of the disk.

The only problem is that windows Virtual memory and page-sys functionality doesn't work like that. Because Windows will never page-sys the applications you are currently working with anyway so it will not make your computer performance any faster by disabling the page-sys.

What can happen instead is that your apps are going to start crashing, since there's no virtual memory for Windows to allocate. And even worse, your system will crash or become very unstable.


So what settings and how to proceed?

On Windows VISTA, Windows 7, Windows 8.1 and Windows 10 or later, let windows mange your Virtual memory regardless how many gigs of RAM you have installed. I have 32GB RAM myself. Let Windows manage your Virtual Memory - page Sys-file on "C: drive"- only. Do not use any extra partition for page sys either.

If you have more then one harddrive installed in your system, set all other drives then "C:" to "None" page sys-file. You only need one.


On windows XP only, it can be good to manage your page-sys file yourself. Set virtual memory to X1,5 times the RAM installed in the computer. Set the same value of both Max and Minimum. But these settings are only for Windows XP.





Core parking on Windows 7 and Windows 8.1


Disable core parking can be a good idea on some systems. This is advance operation require "reg-edit" operation so if you have no experience with systems you can mess up your system completely. On Windows 8.1 its much easier. check the Internet how to do that.

http://forum.cakewalk.com/Windows-7-amp ... 61804.aspx




Best Regards
Freddie
Last edited by Freddie H on Fri Feb 06, 2015 4:59 pm, edited 1 time in total.
-Highly developed spirits often encounter resistance from mediocre minds. -It really matters!

User avatar
BriHar
Senior Member
Posts: 2159
Joined: Wed Dec 15, 2010 11:10 pm
Contact:

Re: Windows Optimizations-guide working with DAWs and plugin

Post by BriHar »

All you need to know in one place!
Thanks Freddie ;)
"...yes I think it can be easily done, just take everything down to Highway 61."

Sun Point Studio Turbenthal, Switzerland


Cubase Pro 10.5.20 - 64bit | Cubase AI 10.5 | WaveLab 9.0.10 - 64bit | PT10 | UR28M | UR44 | CMC-PD/4xFD/QC/AI/CH/TP | BCF2000 | Contour Shuttlexpress | Graphire Tablet | Cubendo Custom Keyboard | Lenovo E31 Workstation:Xeon E3-1225V2/3.2GHz; 14GB DDR3 SDRAM; 2x Intel-Flash520 SSD 180GB (C:/D:);1TB 7200rpm Sata3 (F:); DVD RW (E:); Ext. 3TB USB3 Freecom + WD 1TB; Nvidea GeForce GT 630 4GB DDR3 Video Ram AGP PCIE | Win 10 Pro 64 Bit

Woodcrest Studio

Re: Windows Optimizations-guide working with DAWs and plugin

Post by Woodcrest Studio »

Ditto! It better all be correct, or you.will pay for it! :lol: :P

User avatar
Freddie H
Member
Posts: 510
Joined: Fri Apr 08, 2011 7:59 am

Re: Windows Optimizations-guide working with DAWs and plugin

Post by Freddie H »

Thanks guys! ;) :D



Best Regards
Freddie
-Highly developed spirits often encounter resistance from mediocre minds. -It really matters!

User avatar
chi_mike
Junior Member
Posts: 106
Joined: Tue Jan 27, 2015 12:28 am
Location: Chicago
Contact:

Re: Windows Optimizations-guide working with DAWs and plugin

Post by chi_mike »

Disablae hibernation with SSD. Especially with a 256GB or smaller SSD. Also don't defrag an SSD.

You do this in the cmd , as an administrator

powercfg.exe /hibernate off
Software developer for Apple platforms / Composer
2015 iMac w/ 32GB, 6700K | Mac Pro 6,1 12 core
Nuendo 10.3 ( 3 copies!! ) / NI Komplete 12 / VSL Ensemble Pro 7
Presonus Quantum and Q4848
Saffire Liquid 56 ( backup )
Preamps from a 1968 Scully 280 and other cool gear.
I used to be dr_funk on the blue forum. now I code apps.
"Code Natively!"

User avatar
Starsprinkler
Member
Posts: 354
Joined: Sat Dec 29, 2012 2:35 pm
Contact:

Re: Windows Optimizations-guide working with DAWs and plugin

Post by Starsprinkler »

That's nice of you Freddie.

Here's an official Steinberg article on the subject as well:
https://www.steinberg.net/nc/en/support ... -daws.html

beerbong
Member
Posts: 847
Joined: Thu Apr 07, 2011 6:06 pm
Contact:

Re: Windows Optimizations-guide working with DAWs and plugin

Post by beerbong »

awesome list.. Although there is quite a bit of difference between Freddy's tweaks and Cubase "official" list of tweaks here https://www.steinberg.net/nc/en/support ... -daws.html.

For example SB says to disable Hyperthreading. I think that article is very outdated and it's sorely in need of a "official" update.

As well the *Steinberg* article still says to set Processor Priority to Background.. A bit confusing there..

cheers
BB - Intel Quad/RME/Nvidia Video, RME Raydat, Win10 Home
Cubase 8.5 64 bit / Cubase 9.5 / Wavelab Elements / Halion 6 / Padshop Pro

User avatar
Alex_Hayes
New Member
Posts: 1
Joined: Mon Jan 15, 2018 2:18 pm
Contact:

Re: Windows Optimizations-guide working with DAWs and plugins!

Post by Alex_Hayes »

Thanks Fred

User avatar
peakae
Grand Senior Member
Posts: 3303
Joined: Sat Jan 05, 2013 8:15 pm
Location: Bedroom
Contact:

Re: Windows Optimizations-guide working with DAWs and plugins!

Post by peakae »

I wish Steinberg would change their power scheme to not allow usb ports to go to sleep.
That must generate some unnecessary support requests.
Cubase Pro 10, Wavelab Elements 9, I7 3770K , win10x64, 16Gb Ram, RME Raydat, Steinberg MR816x, Motu 828mkII, Behringer ADA8200, Yamaha moXF6, Steinberg UR242, Yamaha THR 10, Grace Design m900, CMC TP, CMC CH.

djgraver
Member
Posts: 546
Joined: Mon Jul 11, 2011 10:21 pm
Contact:

Re: Windows Optimizations-guide working with DAWs and plugins!

Post by djgraver »

how to enable aero on w10 ?
Win10 x64;Core i5-4670;16GB RAM;SSD system HDD library;Nvidia 1050Ti 4GB
Cubase (always last update)

User avatar
peakae
Grand Senior Member
Posts: 3303
Joined: Sat Jan 05, 2013 8:15 pm
Location: Bedroom
Contact:

Re: Windows Optimizations-guide working with DAWs and plugins!

Post by peakae »

Win10 is using aero, high contrast schemes may confuse some programs.
Cubase Pro 10, Wavelab Elements 9, I7 3770K , win10x64, 16Gb Ram, RME Raydat, Steinberg MR816x, Motu 828mkII, Behringer ADA8200, Yamaha moXF6, Steinberg UR242, Yamaha THR 10, Grace Design m900, CMC TP, CMC CH.

djgraver
Member
Posts: 546
Joined: Mon Jul 11, 2011 10:21 pm
Contact:

Re: Windows Optimizations-guide working with DAWs and plugins!

Post by djgraver »

peakae wrote:
Sun Mar 04, 2018 9:54 pm
Win10 is using aero, high contrast schemes may confuse some programs.
You mean, high contrast scheme it's aero?
Win10 x64;Core i5-4670;16GB RAM;SSD system HDD library;Nvidia 1050Ti 4GB
Cubase (always last update)

User avatar
peakae
Grand Senior Member
Posts: 3303
Joined: Sat Jan 05, 2013 8:15 pm
Location: Bedroom
Contact:

Re: Windows Optimizations-guide working with DAWs and plugins!

Post by peakae »

They are all Aero in Win10.
If you get an "Aero missing" error it is most likely a gfx driver that needs updating or a gfx card that is really old, or some of the visual fx are turned off.
Cubase Pro 10, Wavelab Elements 9, I7 3770K , win10x64, 16Gb Ram, RME Raydat, Steinberg MR816x, Motu 828mkII, Behringer ADA8200, Yamaha moXF6, Steinberg UR242, Yamaha THR 10, Grace Design m900, CMC TP, CMC CH.

Post Reply

Return to “Steinberg Lounge”

Who is online

Users browsing this forum: No registered users and 1 guest