-
DarkRoom 0.13.5
Benchmarks / CPU and I/O (per commit) (push) Failing after 6m16sBenchmarks / Frame budget (on demand) (push) SkippedBuild and test / Desktop (Linux) (push) Failing after 45sBuild and test / Layer separation (push) Successful in 25sTraceability / Requirement traces (push) Failing after 38s🐳 Android image / Build and push (push) Successful in 1sBuild and test / android-image (push) Successful in 2s🐳 Windows image / Build and push (push) Successful in 1sBuild and test / windows-image (push) Successful in 1sBuild and test / Android (aarch64) (push) Failing after 2m20sBuild and test / Windows (x86_64, cross) (push) Failing after 3m1sdtourolle released this
2026-09-20 13:24:51 +00:00 The white balance picker reads a patch, and the manual shows it working.
- The picker averages a patch, not a photosite. The probe was a
point sample of a noisy sensor - the shader fetches the source at one
position per output pixel - and two painted-white air conditioners on
the same wall answered +37 and -50. The tap is now narrowed to the
patch of the canvas around the click, a couple of percent of its
width, and rendered with interpolation on so every sensor pixel under
it is sampled and averaged; void and clipped pixels are left out, and
a patch more than half unusable is refused. - The manual's white balance recording shows a correction. The old
one sampled a red brick wall and moved the sliders by three units. The
frame is now dragged cold first and a white air conditioner picked, so
the swing is visible, and the text says the picker is absolute and
refuses a blown highlight.
darkroom-0.13.5-arm64-v8a.apkis the release-signed Android build (API
28+, arm64).darkroom-desktop-0.13.5-x86_64-linuxis the desktop binary.
SHA256SUMScovers both.Downloads
- The picker averages a patch, not a photosite. The probe was a