-
DarkRoom 0.23.0
StableBenchmarks / CPU and I/O (per commit) (push) Successful in 8m42sBenchmarks / Frame budget (on demand) (push) SkippedTraceability / Requirement traces (push) Successful in 1m22sBuild and test / Android (aarch64) (push) Successful in 47m15sBuild and test / android-image (push) Successful in 3s🐳 Android image / Build and push (push) Successful in 2sBuild and test / Desktop (Linux) (push) Successful in 1h31m5sBuild and test / windows-image (push) Successful in 3s🐳 Windows image / Build and push (push) Successful in 2sBuild and test / Layer separation (push) Successful in 53sBuild and test / Windows (x86_64, cross) (push) Successful in 55m3sBuild and test / Publish the release (push) Successful in 1m58sreleased this
2026-10-05 02:28:44 +00:00 | 9 commits to master since this releaseThe neural models — face indexing, AI denoise, scene grading, masks, the panorama fill — now run on an Intel GPU, try any other GPU through WebGPU, and use every processor core on Windows and in the Flatpak, where until now they ran on one.
Intel graphics run the models. On an Intel integrated or Arc GPU the models now run through OpenVINO. Measured on a Raptor Lake laptop's Iris Xe, model by model against the same laptop's processor: 2.5× faster face detection with the thorough detector, 3.4× faster scene grading, 4× faster AI denoise with Fast and nearly 6× faster panorama border filling. The app itself chose the Iris Xe there at first launch, in its own log. The first launch prepares each model for the GPU in the background, a few seconds each, and the processor serves meanwhile. Linux needs Intel's OpenCL driver (
intel-compute-runtimeon Arch). Windows has that driver with the graphics driver, and the installer carries the runtime, but the Windows path has not yet run on Windows hardware.Any other GPU is tried through WebGPU. A graphics card no vendor-specific path covers — an AMD card on Windows or without ROCm, a phone's Mali GPU — is tried through WebGPU, on Vulkan or Direct3D 12. The app times it against the processor at first launch and keeps whichever is faster. It is unmeasured on that hardware so far; where it loses, nothing changes.
Every core on Windows and in the Flatpak. The Windows installer and the Flatpak now carry ONNX Runtime, so even without a usable GPU the models run on every core — 8 to 10 times faster than the single core they had before. The Arch package carries it too and no longer needs
onnxruntime-cpu. Each desktop package grows by about 110 MB for the two runtimes it ships.The right runtime when several are installed. A machine can now hold the bundled Intel and WebGPU runtimes beside a CUDA runtime fetched for an NVIDIA card or the distribution's ROCm build for an AMD one; the app loads the one that fits the graphics card, so an NVIDIA or AMD card keeps its own faster path.
Phones without a Qualcomm chip. The APK carries a second, generic runtime (32 MB) for phones the Hexagon path cannot serve, and tries their GPU through WebGPU — untested on such a phone so far. A Qualcomm device never loads it, and a phone that does not say who made its chip is treated as Qualcomm's, as before.
A steadier choice of accelerator. The first-launch timing now warms the GPU up before measuring it — a cold integrated GPU lost to the processor in two tries of three — and Settings names the accelerator that lost to the processor, not one the runtime was never built with.
Install over 0.22.1 as usual; the first launch re-measures the accelerators once.
The APK, the desktop binary, the Windows installer and SHA256SUMS are built by CI from this tag's commit.
Downloads