-
DarkRoom 0.19.1
StableBenchmarks / CPU and I/O (per commit) (push) Successful in 5m29sBenchmarks / Frame budget (on demand) (push) SkippedTraceability / Requirement traces (push) Successful in 1m8sBuild and test / Android (aarch64) (push) Successful in 30m34sBuild and test / android-image (push) Successful in 3s🐳 Android image / Build and push (push) Successful in 3sBuild and test / Desktop (Linux) (push) Successful in 48m59sBuild and test / windows-image (push) Successful in 2s🐳 Windows image / Build and push (push) Successful in 1sBuild and test / Layer separation (push) Successful in 48sBuild and test / Windows (x86_64, cross) (push) Successful in 35m51sBuild and test / Publish the release (push) Successful in 51sdtourolle released this
2026-09-28 23:58:06 +00:00 | 102 commits to master since this releaseA merged panorama now arrives in the library straight away, with a thumbnail developed as it will look in develop, and gets a cell two, three or four columns wide in the grid.
Panoramas reach the library. When a merge finished, the app started uploading the composite and rescanning at the same moment, and the rescan usually won: it listed the folder before the file was there, recorded the folder as scanned, and nothing looked again until the next sync — and even once found, the composite had no preview, so its cell was blank. Now the composite is catalogued the moment it is written, placed beside its sources by capture time, and the rescan runs after the upload rather than beside it. Two more ways a panorama went missing are fixed: a sync that ran during the merge could upload the first part of the file and mark it done (the composite is now written under a
.partname until it is whole), and two uploads could send the 800 MB file side by side (one at a time now). A second merge of the same frames becomes-pano-2instead of overwriting the first. (#83)Thumbnailed during the merge. The merge renders the composite's thumbnails from its finished image, through develop's own first-open path — the scene-referred pipeline, the default Tone Mapping and the as-shot white balance — so the grid shows what develop will, and never decodes a 20,000-pixel DNG to make one. Panoramas merged before this release fall back to the ordinary thumbnail path.
Wide cells for wide photographs. A photograph of about 2:1 or wider spans two columns, 2.45:1 three, and 3.46:1 or more four, with a thumbnail rendered at that width. A wide cell that doesn't fit the rest of a row starts the next one, so reading order is kept; Up/Down step by rows. With too few columns, and always on the tablet, it takes the whole row. Panoramas from other programs get wide cells too, from the size in their header. Panoramas merged before this release stay one column wide.
Design draft for learned denoise.
docs/dev/denoise.mdsets out the plan for FR-DEV-3g; nothing of it is built yet.Update tablet and desktop together. The new thumbnail sizes are stored under codes an older build reads as its normal grid size — harmless, but mixed builds show the wide cells on one device only. No catalog schema change (one partial index, created on first use).
The APK, the desktop binary, the Windows installer and SHA256SUMS are built by CI from this tag's commit.
Downloads