
Keep the exposure-stack grouping but unlink image position when Hugin must align handheld bracket members individually. Membership says which photographs belong together; linking position forces them to share geometric variables. A bracketed set is not proof that the camera stayed still between exposures.
Key Takeaways
- Grouping a stack and linking its positions are separate decisions.
- Small handheld shifts can require independent alignment.
- Correct stack labels do not establish a ghost-free final image.
Identify the relationship you need
For a hypothetical bracket, three exposures show the same view at different brightness levels. They belong to one capture group, but a hand movement displaced a window edge in the darker frame. Treat those two observations independently.
Do not dissolve the group merely to permit alignment, and do not force identical positions merely to preserve its identity. The HDR bracket inventory explains input grouping through another editor; it does not establish Hugin's positional constraints.
Compare the source frames before editing the project. A moving curtain is different from a camera shift. Aligning the background cannot make two curtain positions physically identical.
Preserve membership while allowing movement
In Hugin's Advanced or Expert interface, inspect the image table and its stack assignments. The Photos-tab manual documents New stack, Change stack and the position-link choice.
For an approximately aligned stack, select its members and uncheck Link for image position. Keep the stack number appropriate to the capture group. Do not unlink every lens or photometric variable as an automatic consequence; the supported reason here concerns position.
The documented stack-assignment dialog likewise separates linking positions from assigning stack membership. Follow the installed interface's labels rather than assuming every release presents an identical dialog.
Check alignment against stable content
Generate or inspect correspondences appropriate to the actual stack, then calculate geometry with those positions permitted to vary. On a project copy, compare a stable edge near the center and another nearer the boundary.
This is a proposed comparison, not a reported alignment test. Look for coherent improvement across the view rather than accepting one well-matched corner. If only a moving subject disagrees, reconsider source contribution instead of warping the background to satisfy it.
Use the panorama seam diagnosis to keep source movement and incorrect geometry distinct.
Review the composed output
Confirm that every expected bracket member remains associated with the intended view. Then inspect a rendered proof for duplicated subjects, broken edges and unacceptable exposure transitions.
If alignment remains poor, review the correspondences and capture assumptions. Unlinking supplies freedom to solve positions; it does not supply missing overlap or guarantee that a scene with depth can be perfectly reconciled. Keep the original project until the geometry and final source contributions have both been accepted.
Related tasks
- Lightroom Cannot Detect HDR Panorama Brackets: Audit the Input Groups
- How Do I Repair a Panorama Stitch Without Duplicating a Building?
Sources and scope
- Hugin Photos tab — Stacks: Advanced/Expert New stack and Change stack; uncheck Link by image position for approximately aligned handheld brackets while retaining stack membership.
- Hugin source documentation — stack assignment dialog: Stack assignment explicitly distinguishes Link position, Don't link position and retaining existing assignments; handheld sets may need position fine-tuning.
Official Hugin manual sections were actually opened and read on October 23, 2026 (Asia/Shanghai). Commands, comparisons and acceptance checks are proposed rather than performed. Historical FAQ descriptions are not claims about every installed release; verify the interface and source version before changing a project.
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: Pignatta / Pixabay, Pixabay Content License. This is an illustrative source photograph, not an application screenshot or a generated test result.