Audio tweaks

What this section changes

Raises audio thread priority, so on a busy PC they are less likely to run late. The buffer and latency are unchanged.

Applying it

1. Open w0a
2. Go to the Regedit Tweaks page in the left menu
3. Find this section and press Apply on the entries you want

Every entry has its own button, so you are not required to apply a whole section — Apply All at the top of the page is there for when you do want all of them.

Undoing it

Two ways, both of which work:

• Backups & Restore — puts back the checkpoint written before the change was applied. It

puts back everything applied after that point, later checkpoints included — the confirmation says exactly that before it starts.

• The Fix page — searched by symptom, writes the Windows default unconditionally. It does not

read a backup, so it works even if w0a's own backup file is gone.

The undo log lives at %ProgramData%\w0a\backup.json, outside your user profile.

The risk

Everything here is a documented value Windows supports; none of it is kernel-level and none of it is irreversible. The honest sentence is still this: a setting may have no measurable benefit for you. If you apply a change and feel no difference, you are probably right — these pages are not selling you a feeling, they are telling you what was changed.

If you want to measure it, the rule from reading the benchmark applies: change one thing at a time, and read the lows rather than the average.

First, the honest sentence

This box does not lower audio latency. The buffer between Windows and your sound hardware stays the size it was, so sound arrives exactly as late as before. What it raises is the scheduling priority of threads that tell Windows' multimedia scheduler they are doing audio work, so on a busy PC they are less likely to run late. Whether that removes a crackle on any machine has not been measured.

Box by box

Audio thread priority (MMCSS) — writes Scheduling Category="High" (REG_SZ) under HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Multimedia\SystemProfile\Tasks\Audio. Windows ships "Medium". Microsoft's description of the Multimedia Class Scheduler Service puts threads in the High category at priorities 23–26, below only certain system-level tasks, and Medium at 16–22. It reaches only threads that register with the scheduler under this task; a game that registers none gets nothing from it. CS2 is one: none of the 102 modules it loads is the scheduler's library, avrt.dll, so it never registers a task at all. The box asks for neither a restart nor a sign-out.

How to check it yourself

reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Multimedia\SystemProfile\Tasks\Audio" /v "Scheduling Category"

After the box it reads High; a clean Windows has Medium.

What this section does not do

It does not write Priority: Microsoft documents that for a task in the High category that value is always treated as 2, so writing it would change nothing. GPU Priority and SFIO Priority stay untouched too; Microsoft describes the first as not yet used and the second as not used. And it does not write SystemResponsiveness, the value every audio list names next: Microsoft clamps anything below 10 to 20, which is already the default, so 0 does nothing on a normal machine and raises one already set to 10 back to 20.

Outside this page

I hear footsteps after I see them goes through where audio delay actually comes from — the buffer, Bluetooth, resampling, effects — and why only the application can ask for a smaller buffer. The Audio card on the Fix page puts the category back to Medium; it also stops and restarts the Windows audio services. On the Optimizations page, Keep the game scheduler profile in the High category (MMCSS Games) is the same kind of setting for the Games task, which Windows already ships at High, and it has the same limit: a game that registers no task is not affected.