-
DarkRoom 0.19.0
StableBenchmarks / CPU and I/O (per commit) (push) Successful in 5m27sBenchmarks / Frame budget (on demand) (push) SkippedTraceability / Requirement traces (push) Successful in 1m2sBuild and test / Android (aarch64) (push) Successful in 29m53sBuild and test / android-image (push) Successful in 2s🐳 Android image / Build and push (push) Successful in 2sBuild and test / Desktop (Linux) (push) Successful in 50m11sBuild and test / windows-image (push) Successful in 2s🐳 Windows image / Build and push (push) Successful in 1sBuild and test / Layer separation (push) Successful in 38sBuild and test / Windows (x86_64, cross) (push) Successful in 35m28sBuild and test / Publish the release (push) Successful in 1m10sdtourolle released this
2026-09-27 23:50:48 +00:00 | 113 commits to master since this releaseEdits now work on the scene as the camera recorded it, with a new Tone Mapping control to fit it to the screen — every photograph renders differently from 0.18, so update the tablet and the desktop together. Also: panoramas too large for the GPU open in develop, presets live in folders and a menu on the tool rail, and a panorama can leave a frame out.
Scene-referred editing (D19). The camera's colour is converted before the edits instead of after, so exposure, white balance and the rest work on the scene as recorded, highlights beyond white included. A new Tone Mapping control — Contrast and White Point — fits the result to the screen at the end, replacing the per-camera base curves. A film stock is now the last step: every other adjustment decides the exposure the negative receives. Sharpening, noise reduction and the tone curve no longer clip recovered highlights. Tone Mapping does nothing on a JPEG.
- Every photograph renders differently. Raw frames come out a little darker, with more contrast and fewer clipped highlights. Update the tablet and the desktop together: two devices on different builds render the same edit differently. Previews rendered before the update keep the old look until they are rendered again.
Panoramas too large for one texture. Linear DNGs bigger than the GPU can hold — a 22927×8966 Lightroom panorama, or DarkRoom's own merged composites — now open in develop instead of as a read-only preview, pan and zoom smoothly, and export at full size in tiles. Clarity, texture and dehaze preview at the same strength zoomed in as they export. (A patched rawler 0.7.2 is vendored to decode DNGs wider than 16,700 pixels.)
Presets in folders, on the tool rail. Presets open from a Presets entry at the foot of the develop tool rail: a menu beside it applies one in a click, and "Save or manage…" opens the sheet. They are filed in folders that open and close — Film holds Colour, Cinema and Black and white — and naming one "Folder/Name" files your own. Lightroom imports keep their subfolders.
Panorama. Blown highlights stay white instead of turning pink, in the preview and in the merged DNG. On the panorama page, untick a frame to leave it out; the rest re-align in a fraction of a second. A frame that cannot be placed no longer ends the job — its row names it, and Merge waits until it is unticked.
Known issues. Now that merged panoramas open at full size, the experimental border fill shows a repeating pattern along the top edge and a smear in a corner (#79). The wheel stops at 16× fit, short of 1:1 on a very wide image — double-click reaches 1:1 (#80). Tone Mapping's sliders stay live while a film stock replaces them (#81).
No catalog schema change. The sidecar gains two view-transform settings, written only when moved.
The manual is re-recorded under the new pipeline, with new pictures of Tone Mapping and of navigating a giant panorama.
The APK, the desktop binary, the Windows installer and SHA256SUMS are built by CI from this tag's commit.
Downloads