
Registration data is not necessarily a sequence of already aligned pixels. Siril separates finding features, computing transforms and applying those transforms. If the selected method saved only the mapping, stacking may still require an exported registered sequence.
Identify which stage actually completed
Open the sequence used for the intended stack and inspect the registration operation that produced its data. A successful computation and an available registration indicator do not establish that new transformed images were written.
The Siril 1.4.4 registration manual explicitly separates these stages. Different methods combine them differently.
For a real night-sky session, record the source sequence, chosen reference and whether the process created registered image files. Keep that record with the processing branch so an untransformed source is not mistaken for the final aligned input.
Respect the limited on-the-fly stacking case
The manual describes a special case in which stacking can use pixel-wise shifts directly. That avoids saving new aligned images but does not establish that arbitrary rotation, scale or perspective mapping can be handled the same way.
It also explains that subpixel shifts used through that route are rounded to pixel precision. Decide whether the resulting alignment contract suits the intended photograph; an absent export step is not automatically a benefit if the required precision or transformation differs.
Do not dismiss an export warning simply because another sequence once stacked successfully without creating registered files.
Apply the stored transformation deliberately
Use Apply Existing registration when the computed mapping needs application. Confirm the sequence and reference first, then review the output registration choices.
The operation can apply interpolation or the supported Drizzle route. Choose the reconstruction path appropriate to the inputs rather than processing the same branch repeatedly to make a warning disappear.
Review framing as well. Maximum coverage and common-area framing express different retained regions. This article does not prescribe one framing choice for every session or promise that the full image area overlaps.
The lens-versus-perspective guide illustrates why transformation models matter; its editing controls are not Siril registration commands.
Inspect pixels, not only registration status
Open the intended output sequence and compare recognizable stars near the center and edges across representative frames. Confirm that the new sequence is actually the one being stacked.
If residual disagreement remains, investigate the chosen model and source evidence. The panorama disagreement guide explains another setting where a completed alignment operation is not proof that every feature can coincide.
Retain the untouched captures and computed registration until the result is accepted. This guide proposes a workflow check; no frames were registered, resampled or stacked here.
Related tasks
- Why Are Product Edges Still Curved After I Straighten the Photo?
- How Do I Repair a Panorama Stitch Without Duplicating a Building?
Sources and scope
- Siril 1.4.4: Registration — Registration process and Apply Existing registration: Detection, transform computation and application are separate. Integer shifts may be consumed by stacking without saved aligned images; other transforms require application/export. Apply Existing registration uses stored data and offers output framing and interpolation/Drizzle.
Official Siril documentation was opened and read on October 23, 2026 (Asia/Shanghai). Versioned references identify 1.4.4; legacy StarNet controls are explicitly distinguished from the newer 2.5 Python integration. Acquisition, registration, processing and acceptance checks are proposed, not performed. The cover is decorative.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: Mariya Eskina / Pexels, Pexels License. This is an illustrative source photograph, not an application screenshot or a generated test result.