unom/punktfunk
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 16 Wiki Activity

docs(packaging/windows): note the host is x64-only (no ARM64)

Browse Source 
The host is NVIDIA/NVENC + SudoVDA coupled; Windows ARM64 has neither an NVIDIA
driver nor an ARM64 SudoVDA, so an ARM64 host would install but couldn't encode
or make a virtual display. Document the deliberate x64-only scope so it doesn't
get re-litigated. ARM64 stays client-only.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Enrico Bühler
2026-06-19 13:23:30 +00:00
parent 6e0507a9ee
commit 9d6ff77a02
1 changed files with 8 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
packaging/windows/README.md
+8
View File
@@ -3,6 +3,14 @@
A one-file, signed `setup.exe` for the punktfunk streaming **host** on Windows, published to Gitea's A one-file, signed `setup.exe` for the punktfunk streaming **host** on Windows, published to Gitea's
generic package registry (`punktfunk-host-windows`) by `.gitea/workflows/windows-host.yml`. generic package registry (`punktfunk-host-windows`) by `.gitea/workflows/windows-host.yml`.
## x64 only (no ARM64)
Unlike the client (which ships x64 + ARM64 MSIX), the host is **x64-only by design**. It is coupled to
an NVIDIA GPU (NVENC, via `nvEncodeAPI64.dll` from the driver) and the **SudoVDA** virtual-display
driver — neither exists on Windows ARM64 (no ARM64 NVIDIA driver; the vendored SudoVDA is x64-only). An
ARM64 host would install but couldn't encode or create a virtual display, so we don't build one.
Revisit if NVIDIA-ARM Windows PCs + an ARM64 SudoVDA ever ship.
## Why not MSIX (like the client) ## Why not MSIX (like the client)
The host installs a **`LocalSystem` SCM service** that `CreateProcessAsUserW`'s from Session 0 into the The host installs a **`LocalSystem` SCM service** that `CreateProcessAsUserW`'s from Session 0 into the