Skip to content

OriginStack 2.19.0

Choose a tag to compare

@hd152 hd152 released this 31 Oct 01:56
· 173 commits to main since this release
9b61766

Which download?

You have Download
Windows, want it installed OriginStack-2.19.0-setup.exe
Windows, no install (one file) OriginStack-2.19.0-windows-x64-portable.exe
Windows, no install (folder) OriginStack-2.19.0-windows-x64.zip
Mac with Apple silicon (M1 or later) OriginStack-2.19.0-macos-arm64.zip
Mac with Intel OriginStack-2.19.0-macos-x86_64.zip

| Linux | OriginStack-2.19.0-linux-x64.tar.gz |
The desktop app can switch Phase 4 steps off and on after a run, lets you pick any frame in the
recent-frames table to view it, and runs Phase 1 faster; the Gaussian blur and bilateral kernels
are quicker too.

Added

  • The desktop app can switch the post-processing steps of a finished run off and on. A
    "Post-processing steps" panel under the preview has a box per step the run used (denoisers,
    deconvolution, star reduction, local contrast, final sky flatten and others); ticking or
    clearing one redoes only that step and the ones after it and updates the preview and the
    files the run wrote. On a full Sunflower-size frame a late step takes 3-8 s instead of the
    22 s a whole Phase 4 takes. Background and chroma steps redo the whole of Phase 4. The
    starless sidecar of --remove-stars is not rewritten by a toggle. A "Show without stars"
    box in the same panel previews the image without its stars (the inpaint remover, run on the
    finished image) and saves <stem>_starless.jpg next to the preview; the stars-in files are
    left as they are. Not offered for runs with
    --uncertainty-propagate, --error-aware-stretch, --hdr-combine, --annotate or a
    multi-session combine.

Fixed

  • Re-running a session from the _config.toml an --auto run saved now processes the frames
    the same way. --auto asked for per-frame gradient removal on nebulae and galaxies, but it
    decides after the frames are already processed, so the step never ran on the --auto run
    itself; only the saved config switched it on, which made the re-run slower and changed which
    frames passed the quality gates. --auto no longer asks for it.

Changed

  • Faster Gaussian blur and bilateral filter (astro_native 0.63.1). The Gaussian blur behind the
    background, sky and star-detection steps now runs tap by tap with a run-time AVX2 path: on a
    2033x3041 frame at sigma 1 / 3 / 8, 24 / 63 / 177 ms became 14 / 18 / 40 ms, with bit-identical
    output. The colour bilateral filter is about 1.5x faster, also bit-identical. The crate's source is
    split into one module per domain; no behaviour changes. Kernel timings only: the effect on a whole
    run was not measured.
  • The desktop app's per-frame thumbnail strip is gone; the RECENT FRAMES table does its job. Click a
    row, or step through the rows with the arrow keys, to see that frame in the preview. The frame stays
    up while the run continues; picking a stage from the drop-down goes back to following the run. Every
    processed frame now gets a thumbnail (--ui-frame-every defaults to 1, was 5), made from a copy
    averaged down to thumbnail size first, which costs about a tenth per thumbnail of stretching the full frame
    did. Through the app, Phase 1 of a 158-frame Sunflower session took 44 s, against 64 s before
    (three runs each, alternating, spread under 1 s). A frame rejected before it was rendered
    has no thumbnail and says so. Previously a frame picked from the strip was replaced by the latest
    stage at the next update during a run.
  • A mosaic tile much fainter than its neighbours (shot through cloud, haze or dew) is now
    named in a warning. Its brightness cannot be matched to the others, so its outline shows in
    the mosaic; before, that happened without explanation.