Private
Public Access
26 lines
1.1 KiB
Markdown
26 lines
1.1 KiB
Markdown
← [Back to Twitter thread index](../README.md)
|
|
|
|
---
|
|
title: "For Windows trying to standardize on HIGHEST_PRIORITY_CLASS, mixed with THREAD_P"
|
|
author: "NOTimothyLottes"
|
|
handle: "@NOTimothyLottes"
|
|
post_url: "https://x.com/NOTimothyLottes/status/2061937134756380682"
|
|
post_id: "2061937134756380682"
|
|
timestamp: "2026-06-02 22:24:56"
|
|
post_count: 2
|
|
reply_count: 1
|
|
repost_count: 0
|
|
like_count: 12
|
|
view_count: 1118
|
|
---
|
|
|
|
# @NOTimothyLottes — For Windows trying to standardize on HIGHEST_PRIORITY_CLASS, mixed with THREAD_P
|
|
|
|
## Post 1 (2026-06-02 22:24:56)
|
|
|
|
For Windows trying to standardize on HIGHEST_PRIORITY_CLASS, mixed with THREAD_PRIORITY_{IDLE,NORMAL,TIME_CRITICAL}. Which maps to {1, 13, 15} respectively. Then trying "Pro Audio" hack with AVRT to get whatever that gives in the 16-31 fake "realtime" bracket for highest.
|
|
|
|
## Post 2 (2026-06-02 22:27:06) — reply to Post 1
|
|
|
|
Linux mapping will be {SCHED_IDLE, SCHED_OTHER with 2 settings of nice} to match. Unfortunately SCHED_FIFO is locked out by default, but if the user blesses the right permissions will get better audio latency. Maybe pause/unpause will trigger auto latency re-adaption.
|