Сборки windows для музыкантов

Windows 10 tweaks, optimizations, and build tips for pro audio workstations / DAWs – Part 1 of 3

Permalink for the start of this guide: https://aka.ms/Win10AudioTweakGuide . Please use this link when sharing.

This is a long guide. It started out as a simple list of recommended tweaks, but weeks later, it evolved into this multi-part series. I hope you find it useful, despite its book-sized text. 🙂

This is Part 1 of 3. Once available, you will find the other posts here:

• Part 1: Introduction and PC picking/building
• Part 2: What to tweak proactively, and what to consider doing
• Part 3: What not to do when tweaking your digital audio workstation

There are many Windows tweak guides out on the net. Some are good, some are quite bad, some are simply outdated, and some suggest things that may ultimately make for a worse-performing workstation. I’ve avoided releasing a guide like this, because many folks follow tweak guides blindly, and end up with unstable workstations. Part of the reason for this is that very few tweaks will reliably increase performance across all types of PCs, DAWs, and audio interfaces.

But I felt it’s time to release the things I personally find valuable for a Windows music workstation, in the form of an unofficial and potentially unsupported tweak guide. This is part 1, which deals with decisions made before tweaking even starts. This is important, because so much of the train is set in motion here, at the beginning, when you pick your PC or components.

This tweak/tip guide will be full of caveats. Why? Because tweak guides should be full of caveats, of course. There are always implications and side effects to any choices you make when customizing a system.

My general approach for audio is to start with the things I know will be important to do, and then test my performance. If it’s within the range I want, I’m good. But I test with my ears, not by using tools. I recommend folks not get hung up with test results from DPC latency checkers or others unless there’s an actual audible audio glitch.

It’s important to note again that this is an unofficial guide. The tweaks and tips here are not necessarily supported by or recommended by Microsoft, the Windows team, or the companies involved in building the hardware and software you are using. I’ve put this out based on my own experience and research. As with any list of “tweaks”, use these at your own risk and expense.

That said, I’ve tried to provide enough information here for you to make informed decisions, rather than blindly following a list of changes. For that reason, the guide here is both longer, and requires more of your active decision making vs. a straight list of tweaks.

Also, some of these tweaks and suggestions will have different implications when on a desktop vs a gaming laptop vs a “thin and light” laptop or tablet. I note those when that’s the case. Personally, I use a desktop PC for my music creation because that affords me the best performance and expansion options all with the best possible thermal management.

I also keep my PC on the other side of a physical wall (cables pass through the wall, which is actually a decoupled double-wall) so I don’t have to consider any tradeoffs with cooling vs noise. That said, it’s still pretty quiet due to the large fans. Not everyone can do this, but if you can, it’s really a great setup with the best of all worlds.

Картинка с сайта: devblogs.microsoft.com

I’m making the assumption here that the PC you are tweaking is being used for primarily or exclusively DAW use. My own PC is the one I use for everything (video editing and rendering, gaming, software development, 3d CAD/CAM, music creation, general PC use), so I’ve personally made different choices in some cases. That said, my audio latency and performance are quite good, despite having made minimal tweaks.

Folks often ask about specs for my own PC, so here are my PC specs at the time of this writing. Most of my PC is a few years old now. I tend to update components every 3-5 years, on a rolling basis. I don’t regularly reinstall Windows or do any maintenance.

That setup was the right choice for my build at the time, and as of this writing, I am still using it. I’m not making any statement about it being the best system, lowest latency, or most suitable for you. I use a mix of hardware and software synthesizers, and primarily software effects (although I do have some hardware effects). As mentioned above, I also do non-DAW work on this PC (video editing, 3d modeling, software development, writing this blog post, graphics work, games, and more).

Here’s a photo of the basement wall behind me (approximately a third of my setup, and most of my modular gear — keyboards and other synths are on other side of the room)

Картинка с сайта: devblogs.microsoft.com

Almost all of that is attached to the PC either directly (USB), or through a USB MIDI interface (MOTU and iConnectivity). All of it is connected to my PC audio inputs.

Please note that I can neither recommend a system for you, nor comment on suitability of individual components you’ve picked. I cannot otherwise help you choose software/parts/components/PCs/etc. There are lots of helpful folks on forums who can help you there, and who can give you up-to-date advice.

Some (many) of the DAW software companies have their own tweak lists. They are a best attempt at covering the ecosystem of devices that run their products. I don’t recommend following any of them blindly, especially since some of them are really Windows Vista/7 information re-labeled as Windows 10, but do take a look at any additional information provided by your DAW or interface developer. They tend to know what works best with their own software, but aren’t always on top of keeping up with the latest releases of Windows or hardware.

I also work with a number of good DAW PC OEMs (companies that build DAW PCs). They tend to do even more for their systems. If you buy a custom DAW PC from a DAW OEM, and they do something different from what I indicate here, I would trust them to know what is the most stable thing for their system. They know the subset of hardware they target, and they know what they need to be able to support over time. They also know which subset of software they support, and how to get the most from it.

I want to point out one thing many folks don’t realize, and the proliferation of tweak guides (including this one) doesn’t help: you can get perfectly fine audio performance from most quality PCs without doing any of this. You don’t have to tweak the PC in most cases. Of course, the PC ecosystem is huge with many different PCs, DAWs, and devices out there, so your mileage may vary. But don’t go into a PC purchase assuming that, to be usable for any audio, you’ll have to do a ton of customizations.

Ok. Enough with the disclaimers. Before getting into the tweaks, let’s start with some general guidance.

Agree, disagree, or otherwise have an opinion on anything here? Please drop me a note in the comments.

Acceptable audio latency

Unless you are trying to get audio latency down to the absolute minimum you can, because that’s your hobby (much like overclocking PCs, or performance tuning cars), it’s usually not worth doing the additional hard work and stability troubleshooting to knock off another ms or so from your round-trip latency; the additional tweaks have diminishing returns and increased risk of instability in many cases. The majority of your performance is going to come from picking a good audio interface with good ASIO drivers.

I’m not talking about folks building custom systems for orchestral arrangement with 500+ tracks. Those folks will have their own information to go by, and rather unique needs which may push them further than most folks need to go (including restricting to known hardware that may be several generations old). But rather I’m targeting the vast majority of musicians out there who want to ensure they get the most reasonable and stable performance from their PC.

Remember, sound travels approximately one foot per millisecond. So the typical stage monitor, for a guitar player, is around 5-12 milliseconds of latency away from them (if not using in-ear). For those of us with studio monitors, they are usually 2-5ms away. Headphones have less latency, but only if wired. Wireless and Bluetooth protocols add their own latency in communications to the headphones.

Tip: Unless you prefer tweaking over making music, don’t get hung up on the last millisecond or three.

How to pick a PC

If you haven’t already picked the PC you plan to use for audio production, you have some decisions to make. The decisions you make here will completely influence your options when it comes to actual tweaking.

Consider a desktop instead of a laptop

If this is a dedicated DAW PC, and you don’t currently gig or otherwise take your performance on the road, consider a desktop rather than a laptop. Desktops have more expansion options, and most importantly, much better thermal management which include larger (quieter) fans. I know many musicians who hate the loud fan on their laptops once they kick into heavy production. Larger fans can spin more slowly while moving the same amount of air as the much smaller fans in a laptop. Slower typically means quieter. High-quality name-brand fans here also make a difference in airflow and bearing noise.

Additionally, laptops and tablets are very prone to throttling the CPU to reduce heat. The last thing you need while recording is the CPU to slow down. This happens a lot with any consumer laptop that is optimized for size and weight rather than heat dissipation. Note that you can mitigate this a bit with dedicated active cooling pads for your laptop should you need to, but those little fans still tend to be quite loud.

My son had a gaming laptop (he now has a desktop). Whenever he spun up a more intense game, the fan went into full jet engine mode. The CPU didn’t throttle, but that’s because this was a fat laptop, with more cooling. But boy was it loud. I’d never use it for DAW work. I ended up building him a gaming PC for his birthday, spurred on by the failure of one of the fans in the laptop (I’ve replaced those fans, but it’s really a backup/friend PC now.)

And note that this isn’t just a Windows PC thing, it happens across the board with laptops of all sorts. But in the PC world, we have a decent choice to build or buy a desktop as an alternative. I have friends who use actively-cooled laptops that run other operating systems, and they are no different when it comes to noise levels or heat.

Desktops also tend to give you more options for USB connections, as well as the ability to use wired networking rather than wireless. These are both extremely important for systems that will use many external devices.

There are many professional musicians who have completely different gigging vs home studio rigs. They often have desktops in the studio, and laptops for gigs/road. If you can swing this type of setup, you get the best of both worlds. You can use tools like OneDrive to automatically synchronize your data files between them.

Finally, you can upgrade a desktop PC over time vs having to throw it away and replace it. For my own build, I’ve used the same case across a number of builds. I’ve also brought memory (which was over-specc’d), drives, and the audio interface over from past builds. I’ve replaced the motherboard and CPU cooling for each build, and the video card in-between builds. Not only does this reduce overall cost, but it’s generally better on the environment to reuse rather than throw away or even recycle. Also, because I own a retail license to Windows 10 Pro (rather than an OEM version), I’ve been able to move that from build to build over the years.

Tip: If you don’t need to take this PC on the road, or otherwise need it to be portable, a desktop is almost always the better choice. You could always get a separate laptop for road use if you require one in the future. Because the laptop would not be a desktop replacement, it doesn’t necessarily have to have the same high specs you’d require if it were your main studio PC.

Build or Buy

Building your own PC is a hobby in itself. It’s easy enough to build a working PC to handle gaming, web, and more, but not always simple to build an optimally performing PC for audio. In general, you will not save money when building your own PC. Instead, you get to pick exactly what you install into it, rather than choose a pre-configured system, that was not designed with audio in mind.

You can also buy a new audio-focused DAW PC, built by companies that specialize in this. This gives you someone to turn to if something doesn’t work, and also gets you up and running much faster. In the case of PCs built by custom DAW OEMs, you are also guaranteed to have a musician-quality PC ready to run. There are many PC DAW builders out there, but here are two shows I’ve done with current and former DAW Builders:

Computer Music Week

DAWbench Radio Show

Tip: If building a PC is not part of your hobby or interests, strongly consider a custom/dedicated DAW PC builder.

Ok. Let’s get into some decisions around building your own PC.

Custom PC Build tips

Let’s say you’re going to build your own PC. Remember, you’re not likely to save money here, but rather you get to make every decision that goes into the build.

What should you consider?

Start with good components

By “good” I don’t necessarily mean “top of the line”. Plenty of folks make great music on i5 and similar processors, integrated graphics, and 8-16GB memory. In fact, sometimes those i5s do better than i7s in thin laptops due to less thermal throttling. Instead, I mean to purchase quality, name-brand components that have a good reputation in the community. That includes everything from the power supply to the case fans to the memory.

When it comes to memory, I recommend new builders use the memory compatibility list the motherboard manufacturer releases. Most memory will just work, but the compatibility list will remove all doubt and help ensure you are able to get memory that performs to spec in your setup. How much memory you need will depend upon your use, but I personally recommend 32GB if you can, especially if you have integrated graphics and you work with sample libraries. Most everything will work well enough on 16GB, of course. 8GB can be stretching it and will be limiting, but folks still use it with the limitations in mind. I have 64GB in my PC not because I use that much with a DAW, but because some of the other work I do on this PC really benefits from the additional memory.

Is it worth getting memory that is faster than the minimum requirement for your CPU and motherboard? In many cases, the answer is “yes”. There’s a price/performance trade-off, but if you go a couple steps higher, and the memory has an XMP setting (a profile for describing the memory’s preferred settings) that you can enable with your motherboard, it’s worth doing. Audio, video, and graphics work all tend to be memory-intensive, so it’s usually worth boosting just a little there when you can. Keep in mind that rated speed is not the only consideration, as various latency values also play a part. You can go nuts researching this on overclocking and gaming forums.

Tip: Budget components often have budget performance over time.

Minimize what you put in the box

Do you really need a discrete graphics card? Is your DAW PC the right location for a video capture card? The more things you add to your PC, the more work you’ll have troubleshooting any potential additional latency or instability. I’m not saying to completely avoid these things (in fact, I have both a video capture card and a discrete video card in my build), but just to be aware that you will potentially add issues with these devices. What issues you run into highly depends upon the quality of the devices and drivers, how your motherboard is set up, and how much experience you have building PCs.

That said, sometimes, a discrete graphics card will actually help your performance. But this was in specific cases reported on forums, with specific graphics-hungry plugins.

Tip: Keep it simple. The more you put in, the more complex any troubleshooting will be.

Know how your motherboard works

If possible, before purchasing your motherboard, or certainly afterwards, read the manual. The manual typically includes information such as which PCIe slots share resources with each other, or with specific M.2 slots or Thunderbolt ports. In many motherboards, you’ll also find that certain SATA ports share resources with PCIe slots or other on-board devices. This information, factored into your build decisions, can make the difference between a great DAW PC and an unusable one. Knowing this in advance will help prevent issues where you may, for example, max out the M.2 slots with drives, only to find that there are no PCIe lanes left for that audio interface after you added that video card.

Another thing you’ll learn from the manual is which USB ports are CPU/chipset vs. being run from an on-board hub. This seldom makes a real performance difference, but it can help you in prioritizing connections and partitioning the tree of USB devices to maximize bandwidth and minimize interruptions. For example, I would try not to put a USB Audio interface on the same branch of the tree as mouse, touch, webcam, and keyboard. I would also try to minimize the devices (like on-board hubs) in between the CPU and the audio interface.

Knowing this information will help you plan your build in a way that minimizes potential conflicts and maximizes performance where it’s needed.

Tip: Read the motherboard manual. 🙂

Start with a current set of firmware

Your laptop, desktop, or motherboard manufacturer will almost certainly have BIOS updates available. Read the notes and check online forums for problems. If they look reasonable, update to the latest before you even install the OS. Staying with an old BIOS will often mean you lose compatibility with later processors and memory. Many motherboards in the past have required BIOS updates to work with Thunderbolt 3 as well.

When looking for BIOS problems, keep in mind that people on the internet generally don’t start threads to tell you that the BIOS update works as expected. Instead, like anything else you look up, you’ll typically find problem reports disproportionately represented in discussions. What you’re looking for are audio-specific reports, or trends of obvious big problems. A single problem report is not likely to be a trend. Similarly, a report about dropped FPS in a game is not likely to be relevant to music creation.

The same goes for updates to your audio interface firmware.

Tip: Try to update your BIOS firmware before you install Windows

Understand the difference between Windows 10 editions

I’m often asked which edition of Windows 10 I recommend for musicians. In general, I recommend Pro, because it has more knobs you can turn to control aspects of the system, especially anything that uses Group Policy, or has to do with updates. But outside of that, most folks with a basic DAW can do fine with the Home edition, as long as they understand the limitations.

So, when in doubt, get the Pro edition. But if your PC came with Home edition installed, you don’t necessarily have to upgrade to Pro.

Note that some PCs come with what is known as “S Mode” (formerly Windows 10 S). This is fine for the majority of consumers out there, but not for musicians at the time of this writing. You can switch the PC out of S mode, so you can install the DAW software and other tools you need to produce music.

Tip: Windows 10 Home is fine, but Windows 10 Pro will give you more options for control over the PC. You can upgrade at any time, but it’s easiest to start with the one you want to keep.

Talk to others

There’s a huge community of PC builders out there. Ideally, you want to participate in a segment which specializes in DAW PCs. You can find forums and threads in places like Gearslutz, KVR, and more. If you just do a web search, you’ll get an unbalanced view because most people post their problems, not their successes.

I can’t help you with PC or component recommendations, but I do recommend checking out the various music forum DAW Build PC threads. Technology changes every year, so these tend to be quite active.

Tip: There’s a great community of audio PC builders. Tap into it.

Don’t rely on latency-reporting apps to decide if your PC is usable for audio

I sometimes get reports from folks who have perfectly usable systems, and are making music with them, but tried out a latency monitoring application and saw poor results. These types of apps are really only useful once you’ve already run across glitching or other issues. Instead of relying on these reports, trust your ears. Only if you hear a problem should you turn to these apps to get some indication of what may be the cause.

Tip: Use your senses, not a benchmarking app.

Bonus: Consider installing Power Toys

Musicians often want to remap keys and have greater control over managing windows on their desktop. The open source Microsoft PowerToys makes those, and more, very easy to do. You can download and install them for free. You can even contribute your ideas (or code!) to help make the product even better.

Microsoft PowerToys Documentation Microsoft PowerToys Github Repo

PowerToys is delivered out of the box because it makes it easier for us to iterate out of cycle with Windows, and also makes community contributions possible.

Tip: The PowerToys Fancy Zones is especially nice for window management.

Bonus 2: Consider Microsoft Edge (Chromium)

Oh, and one of the first things many people do, usually by old habit when setting up a new PC, is install Google Chrome. Chrome is a good browser, but keep in mind that the current version of Microsoft Edge is based on the open source Chromium project (Microsoft is one of the biggest contributors to that project) so is compatible with all the same sites and markup that Chrome is. It also supports Web Audio and Web MIDI, and I’ve had zero issues using it on sites that recommend Chrome. You can (if you want) sync favorites and more between Windows, macOS, iOS, and Android. It even has some pretty nice privacy tweaks, and easy switching between home and work profiles.

I beg forgiveness for the marketing-like blurb, but please do check it out.

This video is almost a year old at this point, but is still useful. Also, for once, it seems like I can actually recommend that you read the comments. 🙂

Tip: The new Microsoft Edge Browser, based on Chromium, is not the same as the old one. Check it out.

What’s coming

In the remaining two parts of this series, I’ll talk about what we would normally think of as tweaks, which ones to apply, which ones to question, and which ones to stay away from. I’ll also recommend steps to take when things don’t go as planned.

If you have your own PC building tips (specific to DAWs), or disagree with any advice here, please do mention it in the comments below.

The DAW PC tweak series

This is Part 1 of 3. Once available, you will find the other posts here:

• Part 1: Introduction and PC picking/building
• Part 2: What to tweak proactively, and what to consider doing
• Part 3: What not to do when tweaking your digital audio workstation

Permalink for the start of this guide: https://aka.ms/Win10AudioTweakGuide . Please use this link when sharing.