Releases: halideworks/gloam
Release list
Gloam 1.8.1
Gloam's first public release. The app has been shipping and auto-updating for a while;
this is the version the repository is opened up around, so the notes below cover what
changed in 1.8.1 and the docs that now exist for people arriving for the first time.
New
Install preflight warns when a calibration and a live regrade disagree about tone.
Gloam's live gamma correction assumes your display presents SDR at roughly gamma 2.2,
which is what an uncorrected Windows display does. If you install a calibration built for a
different curve (BT.1886, or true piecewise sRGB) and leave a live Gamma 2.2/2.4 regrade
switched on, the two stack imperfectly and shadows end up approximate rather than accurate.
Gloam now says so before installing, and names the fix: set that display to Windows Default
for calibration-accurate viewing. It is a warning, not a block. Running both is a
legitimate trade if you prefer the regrade, and you can continue.
This does not affect HDR calibrations, and it does not change any of the calibration math.
Documentation
- Troubleshooting guide: SmartScreen on install, a profile that
stops applying after a Windows update, a game that resets your gamma, colors going wrong
after a driver update, and where every file lives. - Golden fixture contribution guide: if you own an
OLED, QD-OLED, wide-gamut LCD, or mini-LED display and a colorimeter, you can contribute a
measurement recording that permanently pins Gloam's behavior on that panel class. No code
required. - Contributing and security policy, issue templates, and a rewritten README.
The README now states plainly which displays are validated by recorded measurement data
(two mid-range LCDs) and which are expected to work but unvalidated (OLED, QD-OLED,
wide-gamut LCD, mini-LED). The second list is the honest one: the code handles those panels,
but nothing pins that handling yet.
Whitepaper corrections
Three claims were overstated and have been tightened:
- The description of how the live ramp composes with an installed calibration profile now
states the actual bound (exact against a gamma 2.2 target, approximate otherwise) rather
than implying it is always exact. - The drift model now says why a time-only correction is defensible on panels with
automatic brightness limiting, instead of asserting it. - Refinement refusals are now documented as what they are: recorded with their reason,
shown in the report, with the previous best measured state kept rather than replaced.
Internal
The codebase was renamed from HDRGammaController to Gloam throughout: projects,
namespaces, and solution. This is invisible in use: the application, its install location,
your settings, your calibration profiles, and the update chain are all unchanged. It matters
only to anyone reading or forking the source, which is rather the point this week.
Every fire-and-forget async event handler now runs behind a guarded boundary, so an
unexpected failure in a button handler logs instead of taking the process down with it.
Upgrading: installed builds update automatically on next launch or restart. Nothing to do.
Fresh install: GloamApp-win-Setup.exe below. Per-user, no administrator prompt.
Gloam 1.8.0
Gloam 1.7.8
Gloam 1.7.6
Gloam 1.7.5
v1.7.5 v1.7.5: v1.6/v1.7 features (HDR color loop, tone-map, dose scheduling…
Gloam 1.5.2
Ship the golden-fixture measurement CSVs the blanket *.csv ignore ate The v1.5.2 release build failed: GoldenReplayTests could not find native-measurements.csv on CI because .gitignore's packaging-artifact *.csv rule silently excluded the fixture recordings from the release commit (locally the untracked files still satisfied the tests). Negate the rule for tests/**/Fixtures and commit the recordings. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Gloam 1.3.0
v1.3.0 v1.3.0 - color-math accuracy overhaul, calibration correctness and HD…