Spiker Stack manual · Documents Spiker Stack 2026.11.17a
SmartStack
When you know where a stack has to be right but not which engine or settings get it there, SmartStack finds out for you. You mark the regions that matter and say what each one asks for; SmartStack fuses every engine at those regions, searches the best engines’ own settings, scores every candidate the same way, and ranks whole-picture configurations you can apply to Stack or keep as pictures. Nothing it tries changes your stack until you say so.
SmartStack is reached two ways, and the ribbon tells you which you are on.
The Smart path. When an import has developed and been scanned, the Images list asks How do you want to stack this bracket?; SmartStack this bracket takes this path. The ribbon then reads Capture, Images, SmartStack, Touch up, Finish: the SmartStack step stands in for Align, Crop and Stack. Press Start on its card (or the button is already at work): the status reads SmartStack · aligning and cropping the stack first, the images are aligned to the reference and cropped to their common area exactly as Align and Crop would have done, and when that lands (Cropped — SmartStack is ready to run) the workspace below opens on those pixels. Mark the regions, pick a budget, run, and Keep image the candidate you like: on this path the kept image is the result (Kept … — it is the result; continue to Touch up), and Continue to Touch up takes it on. The step reads done once a kept image is the result. Adjust manually, on the card and beside Run SmartStack, returns to the Manual path: Align, Crop and Stack come back on the ribbon, and you land where the stack stands — Stack when it is cropped, Crop when it is aligned, Align otherwise. The choice is per stack and saved with the project.

The Smart tab on the Manual path. On the seven-step path SmartStack is the Stack step’s second face. The Stack panel opens with two tabs over a hairline, Manual and Smart: Manual is the engines and their settings as the Stack chapter describes them; Smart is SmartStack. You reach it any time two or more images have developed: the Smart tab, SmartStack… on the Images card, or File ▸ SmartStack…. The Stack card on the ribbon stays lit; going to any step leaves the face where it was, and the tab brings you back. Here SmartStack prepares the images for itself and the session’s own alignment stays untouched, as the next section describes.
Either way, while it is up the picture in the centre is SmartStack’s, a toolbar above it holds the region tools, the panel at the right holds the run’s controls, and once a run is on the Images list at the left fills with the candidates it produces.
The older adjustment matrix lives inside the same face as the Legacy sweep (Expert mode): the brute-force grid of the previous chapter, unchanged, for a baked and saved project. File ▸ Adjustment Matrix… opens it; while it is up, the Mode dropdown at the left of its toolbar returns to SmartStack. Standard mode never shows it.
Why. The adjustment matrix tries every combination of a fixed table and ranks the outputs against each other, so it can only say which of its own outputs did best, and only after you have baked and saved. SmartStack starts from what the frames themselves contain: how sharp the sharpest frame is at every point, which tones any frame shows, how much noise the camera left. Every score is measured against that, so a candidate’s score means the same thing in every run, on every stack, and a region you painted can say exactly what it wants.
Opening the workspace
The Smart tab is enabled once every image has developed and there are two or more of them; hovering the grey tab reads Needs two or more developed images. Nothing else is required: not an alignment, not a crop, not a saved project.
A stack’s SmartStack opens with an empty region list. Region roles › Subject, band and Background makes three in one step — a Subject region from the picture’s matte, a Clean Halo band along its edge that follows it, and a Background — with the Subject selected and the brush armed, so refinement begins at once. Settings › General › Start SmartStack with the three layers makes every stack open that way; a list you clear then stays clear for the session.
If the session has already been baked (Crop › Bake, Stack’s own bake, or the Smart path’s own align and crop), SmartStack works on exactly those pixels. Otherwise — the Smart tab on an unaligned Manual-path session — it prepares the images for itself the moment the face opens: the status bar reads SmartStack · Aligning and then SmartStack · Warping while it aligns the stack to the reference, crops it to the common area and warps every image, and the picture shows Preparing the images… with SmartStack aligns and crops the stack for itself; the session’s own alignment stays as it is. The session’s alignment, crop and results are never touched by this. When it is done the status reads SmartStack · images aligned and cropped — the session’s own alignment is untouched and the prepared reference image fills the view.

Tip. If SmartStack’s own alignment turns out well, Diagnostics › Use this alignment in Align (Expert) hands it to the Align step, exactly as if Align images had produced it; the status reads SmartStack’s alignment adopted — Align shows it. The crop it chose comes along.
The toolbar
The strip above the picture is where regions are drawn. It stays on one line: when the window is narrower than the strip, the strip draws smaller, then with icon-only buttons whose names are in their hovers, and only a window narrower than the app allows would put Overlay Opacity on a second row. Its groups, left to right:
| Group | What is in it |
|---|---|
| Add region | A split button with the traced butterfly. Its main part adds a Detail region, selects it and arms the brush; the caret beside it (Region roles) opens the menu of roles: Detail, Clean, Smooth, Ignore, the Clean band, the Background, and Subject, band and Background, the three layers in one step. |
| Undo Redo Clear | Undo and redo region edits, and the corners of a Polygon outline in progress, and Clear, whose hover is Remove every region. |
| Draw | Pan (drag moves the picture, nothing is drawn), Box, Brush, Polygon, Lasso, Wand, the Subject tool’s two fills, Subject and Behind, then Stroke, which fills a region with a ring along another region’s edge, with a gear for the matte’s settings. |
| Brush | Shown while the brush is picked: Paint or Erase, then the brush Size in result pixels and its Softness, each in its own block. |
| Wand | Shown while the wand is picked: Tolerance (0 to 100) and Contiguous. |
| Overlay Opacity | How strongly the regions tint the picture, at the right edge. |
The selected region’s Feather and, once it is painted, its Grow sit under the list in the Regions section, as Selected region.
There is no picture switch on the toolbar: the Images list decides what the picture shows. Click an image and the picture is that input image, aligned and cropped as SmartStack prepared it — the reference until you pick one; ↑ ↓, the wheel or a click on the list steps through the stack, so each region can be drawn on the image that shows it best (the first image of a bracket often has the subject out of focus). A chip over the picture names the image, or the candidate on screen: its rank, engine and score. Click a candidate once a run has produced some and the picture is its full-resolution result.
The panel’s Run, Regions and Result sections stay where they were; in Expert mode Engines, Search, Scoring and Diagnostics join them. The candidates themselves head the Images list at the left. The Image backdrop shows the selected image as SmartStack prepared it, aligned and cropped; the Developed / Camera (JPEG) pill at the top right of the window works here too, with the camera’s rendering warped and cropped the same way, so a region drawn on one sits on the other. In one case the pill turns orange, knob and all, and says why on hover: the program no longer holds the warp that aligned and cropped these images, so the camera’s rendering cannot be placed over them; crop the stack again, or compare on the Images step. Every section folds, hover a section’s caption for what it is for, and the panel’s ?, in its title row, walks the toolbar and every section of the workspace; Details on the toolbar’s stop walks its groups, and on Run its two controls.
Regions
The eye on the section’s caption takes every region off the picture at once and puts the same ones back; each region’s own eye is left as it was. A run turns it on when it starts and leaves it on when it ends, so the result is seen clean; click it to bring the regions back. A run scores the picture where you tell it to look. Without regions it scores the whole picture with one general bundle, which finds an honest overall winner; with regions it scores what you care about, weighted as you say, and the whole picture besides. The Regions section is the same list as Stack › Review’s Pin ROI: regions you pinned there are already here, and vice versa.
Drawing
Pick a tool on the toolbar: Box drags a rectangle on the picture, Brush paints, Polygon and Lasso outline, Wand picks a colour, Pan puts the tools down, and the pointer becomes a hand that drags the picture. With the brush, a ring shows its size, Size sets it in result pixels, Softness fades its edge, and Paint / Erase say what a stroke does (holding Shift flips it for one stroke). For a straight stroke, hold L and click: the line runs from where the last brush stroke ended to the click, and the next click with L held carries on from there, so a pencil’s outline is a click per corner; with nothing painted yet, the first click only marks the start, and while L is held the line to come is drawn from there to the pointer. The key is Straight line under Settings › Shortcuts, the same one Touch up uses. Hold B over the picture and pinch the trackpad to size the brush, or hold O and pinch to set the overlay’s Opacity; a chip at the top left reads the value. While either key is down the pinch does only that: the picture neither zooms nor scrolls. Without either key a pinch zooms the picture, and a right-drag, or a drag with the pan key (Space) held, pans it whatever tool is up. Both keys can be changed in Settings › Shortcuts; B sizes the brush the same way in Touch up and on a Finish brush mask. Painting lands in the region selected in the list, so a stroke on an eye adds to the eye’s region and not to a new one; Add region starts an empty Detail region, and its caret one with the role you pick; either selects it and arms the brush for it. A painted region is exactly the pixels you painted; its box is the paint’s bounds. Feather softens the selected region’s edge, so a hard box does not score the pixels just outside it as if they were inside.
Polygon puts a corner wherever you click; a click back on the first corner, or a double-click, closes the outline, and Esc drops it. While you are placing corners, Undo takes the last one back, and Redo returns it. If the outline closes before you meant it to, or you lose it to Esc, a tool on the toolbar or a click on a region’s row, Undo brings it back as it was, with the Polygon tool up and its region selected, as long as you have not edited a region since. Lasso is the same outline drawn freehand: drag around the thing and let go. Either lands in the region selected in the list, or starts a Detail region when none is selected; hold Shift as it closes and the outline carves out of the region instead, so a hole in an eye’s region is a Shift-polygon inside it. An outline is filled exactly, with a soft edge at mask size, and it is kept as the corners you placed, so a saved project draws it again the same.
Wand selects by colour: click a pixel and every pixel like it joins the selected region (or starts a Detail region); Shift carves it out instead. Tolerance says how alike a colour must be, 0 for exactly that colour up to 100 for any; Contiguous takes only the pixels joined to the one you clicked, or, off, that colour anywhere in the picture. The wand reads the picture under the pointer — the image shown on Image, the stack’s sharpest composite on Result — so step to the image where the thing is sharp before you click. What a carve surrounds is kept: Shift-click the grass that leaked into an insect’s region and the insect stays. A chip reads Selecting… while the worker looks, and what it found arrives as outlines in the region’s list of shapes.
Grow, under the Regions list, widens (+) or narrows (−) the selected painted region by that many pixels at mask size. It is applied last and never changes what you drew, so a region grown to catch a hair line and brought back to 0 is exactly the paint again. Every outline, wand pick and grow is one undo step, and all of them save with the project.
The Subject tool
Painting around an insect’s hairs or a leaf’s torn edge with a brush is slow, and the brush is never quite where the edge is. Subject fills the selected region (or a new Detail region when none is selected) with the picture’s subject, found the way Touch up’s Matte finds it: where any frame is sharp, bounded by the colour of the backdrop, snapped to the picture’s edges. Behind fills with everything but the subject (a new region is Smooth), which is the quickest way to say “no sharpened grain out there”. Either fill replaces what the region held; the brush then refines it — Erase a leg that belongs to the background, Paint an antenna the matte let go — and the strokes ride with the region, so a saved project builds the same matte again and paints the same strokes over it.
The gear beside the two fills holds the matte’s settings: Choke (−1 to 1) pulls the matte in off the backdrop, or out when negative, and Feather (0 to 1) softens its edge. The default is pulled in a touch, so a Detail region stops at the subject’s hair line rather than a pixel into the backdrop it was blended with. The matte is cut from sharpness, so on its own it catches fur, hairlines and wing edges and leaves anything smooth inside the body out: an eye, a dark patch, a plain membrane. Fill holes (on by default) makes everything the matte surrounds subject too; Close (0 to 20 px at mask size) first bridges breaks in the matte’s edge up to that width, so a gap in the hair line does not let the fill out — raise it when the eye still shows through. Halo band turns the region from the matte into a ring along the matte’s edge: Outer (px at mask size) is how far past the edge it reaches, Inner how far inside, so a soft rim counts too. Moving any of them re-cuts the selected region; Reset returns to the defaults.
Region roles › Clean band around the subject makes that ring in one click: a Clean region named Halo band, cut from the Subject matte with a preset width (1.5 % of the picture’s long edge outside, a quarter of that inside), placed above the Background if there is one. The science of it: a halo is a few pixels wide along the silhouette, and the Clean bundle is an average over its region, so a Clean region over the whole background dilutes the halo with flat area where every term reads zero. A ring straddling the silhouette measures the halo where it happens. The ring follows the matte rather than an edge detector because the matte is already an edge-snapped silhouette, a halo is a low-frequency glow that no edge detector sees, and the false edges that would mislead one are background texture outside the subject, where a subject mask cannot suppress them.
Stroke is the same ring cut from a region rather than from the matte. Press it and a small panel asks From — any region but the Background and the other strokes — and the ring’s Outer and Inner widths (px at mask size, up to 256; the preset to start, then whatever you used last). Stroke fills the selected region with that ring, or makes a new Clean region named Band around … above the Background when nothing is selected; the brush then refines it like any fill. The ring is linked: it is cut again from the source’s paint every time, so a brush or polygon fix to the Subject moves the band with it, which is what the matte’s own band cannot do. With a stroke selected, the same panel shows its source and widths and every change retargets it in place, one undo step each. Removing the source empties its stroke (the dialog says so); the panel then reads (gone) and lets you pick another source. A project with a stroke in it is saved as v13.
Region roles › Subject, band and Background does the three steps at once: a Subject region filled from the matte, a Halo band stroked from that region, and a Background, in that order top to bottom, one undo step, the Subject selected with the brush armed. The band sits under the Subject, so the Subject owns its body and the ring’s layer is the halo side of the edge. A Background already in the list is kept. With Settings › General › Start SmartStack with the three layers on, this is also what a stack’s SmartStack opens with.
Tip. Subject for the thing the picture is about, fix its edge with the brush or the polygon, Stroke a Clean band from it, Background under everything. The preset does exactly that, and the band keeps up with every fix you make to the Subject afterwards.
Cmd Z and Cmd Shift Z undo and redo every change to the regions while you are on the Stack step: a drag, a stroke, a fill, a rename, a role, a weight, a removal.
The list
One ruled row per region, in the dress of Finish’s Layers list: an eye that hides it on the picture, so the regions around it are easier to see and paint (a hidden region is still scored: every region in the list goes into the run), a dot in its role’s colour, its name (double-click to rename in place), and at the right its ×, its weight as a chip (Expert), and its role as a chip in its colour; the role chips all take the widest role’s width, so they line up down the list. Clicking a chip opens its editor. The role chip’s also offers the colour this stack draws that role in — ten swatches or Custom for any colour, Reset for the default — so the tints can stay clear of the picture’s own colours; the choice is saved with the stack. The × removes that region and Clear on the toolbar, whose hover is Remove every region, clears them all; both ask first, and Undo brings a removal back while you stay on the step. A count reads n regions on the folded section’s caption.
The list is in layer order, top first. Where two regions overlap, the top one owns the overlap: the lower region is scored only where the layers above leave it, softly at a feather, so a pixel never counts twice and a Clean edge drawn over a Detail body carves its ring out of the body. Ignore is the exception: it is carved out of every layer and of the whole picture, whichever row it sits on. Drag a row to move it, or Move up / Move down in its right-click menu; each move is one undo step, and the tint on the picture changes with it, because a region is tinted only where it owns the pixels. Region roles › Background adds one region that owns everything the layers above leave; it reads background in its row, goes to the bottom of the list, draws no box, and there can be only one. A Background is the whole picture, so with one in the list a screening stage runs at a reduced size instead of a crop.

The role is what the region asks of a candidate. There are four, and the choice is the one decision that most changes what wins:
| Role | What it asks for | Mark it on |
|---|---|---|
| Detail | Sharp wherever a frame was sharp. The candidate must keep every bit of sharpness any frame recorded there, without inventing more. | An eye, antennae, hairs, the texture that makes the picture. |
| Clean | No halo, ghost or doubled edge. The candidate must not glow, ring or double where a near edge crosses a far background. | A leg against the sky, a bright rim in front of something dark, a hair over the background. |
| Smooth | No sharpened grain on a flat surface. The candidate must leave a smooth surface smooth: no noise sharpened into texture, no seams between frames. | A background, a plain wing membrane, an out-of-focus flower. |
| Ignore | Not scored, and carved out of every other region and of the whole-picture score, whatever its place in the list. | Anything that cannot be stacked and should not count: a moving leg, a blown highlight. |
Two things are the same for every role and need no region: a candidate must never show a tone no frame shows, and must never invent fine structure. These are checked everywhere, and a candidate that fails them is rejected outright (see Scoring).
The weight (×0.25 to ×4) says how much a region counts next to the others. A region’s say also grows with its area, but only up to about 4000 pixels, so a small eye at ×2 is not drowned by a large background at ×1.
Regions are drawn in the prepared picture’s own pixels, whichever image is under them: the image you drew on is a backdrop, not part of the region, because a region says where the result is scored and the scorer reads every image’s evidence there. If the session is re-cropped or re-aligned afterwards, a region’s row reads re-pin: it was painted for other pixels, the run skips it, and you redraw it where it now belongs.
Tip. Three regions are usually enough: one Detail on the thing the picture is about, one Clean on the edge most likely to halo, one Smooth on the background. More regions make the score more particular, not more exact.
Running
The Run section is where a run starts and where it reports.
Quick · Balanced · Thorough set how much searching a run may do; hover one for its size in trial units. Quick (about 50 trial units) fuses every ticked engine once at your regions and refines the best two only briefly. Balanced (about 120) screens the best few engines over their own settings and refines each. Thorough (about 300) screens wider and refines at length. A trial unit is one full-resolution fusion, so the time depends on the stack: a 13-frame, 20-megapixel stack runs Quick in about a minute and Balanced in under two on a recent laptop. In Expert mode, editing any Search, Engines or Scoring value marks the choice Custom; Use as my defaults makes your Expert values the starting point of every new project.
Run SmartStack starts the run. Its hover says what it does: Fuses every ticked engine at the regions, then searches the best ones. Candidates land in the run folder beside the project (or the app’s cache for an unsaved session). The run folder is <project>-smartstack/<run id> beside a saved project; an unsaved session’s runs go to the program’s cache folder, and saving the project later keeps the run’s record with it. The button reads Preparing the images… while SmartStack aligns, Tick at least one engine when the Engines section has none, and Another job is running while anything else runs.
Once running, the section is the run’s: the engine and the stage the search is at under a spinner (Edge Detail · Screening) and Cancel across the width where the run button was. Under them the Run status card names the run with a chip reading Running, then Finished, Cancelled or Failed; a bar fills as the trials land; and a table lists Trials done against planned, Elapsed, and Best so far with its engine and composite score. Once the run ends the table adds the Stage it ended at and what it Spent in trial units. The status bar carries the same progress as for every job, with the usual estimate.
While it runs, the picture is the run’s: the regions leave it (they were read when the run started) and it follows the best candidate so far, switching to Result and selecting each new leader as it is parked. The list is the candidates that keep their full picture: the best few overall, the best for each region you drew (its row says kept for the region), and the Combined. Each arrives with its picture, so you can click any row the moment it appears and the picture stays on it for the rest of the run; a candidate that a better one pushes out leaves the list. A candidate whose picture is not there yet, or whose picture was let go to make room, keeps the last picture on screen under a chip reading … — waiting for the run until the run ends and it is read. The regions come back over the picture when the run ends, and the selection is yours again.

The stages a run passes through, in order:
| Stage | What happens |
|---|---|
| Baseline | Every ticked engine is fused once, at the project’s own settings for it, at full resolution. |
| Screening | The best few engines (the top by composite, plus whichever engine did best at any one region) each try a spread of their own settings, at a reduced size that ranks quickly. |
| Survivors | The best of each engine’s spread are fused again at full resolution. |
| Refining … | The best of each searched engine is refined one setting at a time at full resolution; the stage names the setting and the sweep. |
| Combined | With regions, the best candidate at each region is composited over the whole-picture winner, each region’s part weighted exactly as the region is scored, and the result is scored like any other candidate. It is skipped when the winner is already best at every region. |
| Finalists | The best candidates overall are reported, best first. |
Cancel stops after the trial in progress. Every candidate so far stays in the list and on disk, and the button becomes Resume SmartStack, which continues the same run: recorded trials are reused and only the rest run. Forget run drops the run from the project; kept images stay. A run whose folder has been moved reads The run folder is not where the project left it.
Why no estimate in the section. A trial’s length depends on the engine and on whether it runs at full size or screened, so the run only knows its pace once each engine has been timed. The status bar shows an estimate as soon as it has one, the way it does for every job.
The candidates
Once a run starts, the Images list at the left is where the candidates go: a Candidates section heads it and the images fold under it as Source images, both sections with a chevron, so the list you were working from is still there, under the list you now want. Folded, the caption reads Candidates · n with a dot while the run is on. The same two sections run across the strip when the list is docked under the picture, the candidates as cards after a tile that holds Keep n.
Candidates lists every scored candidate, best first, at the image rows’ geometry. Each row shows a checkbox, a thumbnail with its rank in the corner, its engine and id (Pyramid · #12, Combined for the merged candidate), its composite score and the stage it was made at, and one bar per region whose width is the region’s say and whose fill is the candidate’s score there, so a row that is high overall but empty at your Detail region is easy to spot. A ≈ after the score marks a tie: the candidate is within the noise of the one above it, and the run cannot honestly say which is better. Hover a row for its id, stage, every region’s score, the trial units it cost, and, for a refinement step, the candidate it stepped from; a Combined’s hover lists which engine each region took; a rejected candidate’s hover says why.

The checkbox ticks a candidate for Keep n above the rows; Shift-click ticks every row between the last tick and that one, and ⌘-click (Ctrl on Windows and Linux) on a row ticks it without showing it. Keep n saves every ticked candidate as a kept stack, one after another (Keeping n candidates… under the rows while they go, Keeping… on each row still waiting). The ticks are the session’s, not the images’ selection: the toolbar’s actions on selected images do not see them. The button reads Wait for the run to finish while the run is on and Tick the candidates to keep while nothing is ticked.
The ★ at the right stars a candidate and the eye under it takes it out of the list; Show hidden (n) beside Keep n brings the hidden ones back. Stars and hides are saved with the project. A candidate you have kept carries a Kept pill. Right-click a row for the same marks and Keep image.
Click a row and three things happen: the picture switches to Result and shows the candidate’s full-resolution result; holding X flips to the reference image, with the chip B · Reference — release X for the candidate; and the Result section opens for it. While Result is up, ↑ and ↓ step the candidates, best first, and stepping is a flip, not a reload: the zoom and pan stay exactly where they were, so a detail can be compared across the ranking; the chip over the picture reads the candidate’s #rank · engine · score, with — opening… while its picture is still on its way, during which the last picture holds the pane. Once a run is idle every parked candidate is read ahead, nearest the selection first, so after a few seconds every step is instant and stepping back never reads again. Click an image in Source images and the picture shows that image behind the regions again, and the arrows walk the images as ever. Only the best few results stay parked in the run folder, so an older candidate may read No picture for this candidate; its settings still apply.
Result
Result is everything about the selected candidate, and the actions on it.
The head reads its name (SmartStack #12 · Edge Detail, or SmartStack #31 · Combined), its composite, the stage it was made at, and Kept if it was. A rejected candidate reads Rejected: and the reason.
| Action | What it does |
|---|---|
| Apply settings | The session takes this candidate’s engine and settings; press Stack to reproduce it. The status reads Settings applied from … — press Stack. |
| Undo apply | Puts the settings back as they were before the last apply, with the status Settings restored — … undone. The same chip shows at the top of Stack › Engines until you change any engine setting by hand. |
| Keep image | Saves the candidate’s full-resolution result as a kept stack, named after the candidate and recording the run it came from; the status reads Keeping …. Kept stacks appear in Touch up’s Stacks and in Stack’s compare picker. Several keeps queue up (Keeping n candidates…): Keep n in the Candidates list queues every ticked candidate at once. |
| Compare in Stack | On the Manual path: goes to the Stack step with the kept stack as the B side of Compare with, so X flips between your current result and the candidate. Needs the image kept first. |
| Continue to Touch up | On the Smart path, in Compare’s place: the kept image is the result, and Touch up paints source images onto it. Lights once a kept image is the base. |
| Save as subject… | Makes the candidate’s engine and settings a saved subject, as Stack › Subject would. |
A Combined candidate is kept, compared and continued like any other, but it has no single engine and settings to apply, so Apply settings and Save as subject… are off for it, with the hover A Combined candidate has no single settings; its Settings vs project is the list of regions and the engine each took.
Settings vs project lists every setting the candidate changes against the project’s current engine settings, in the words of the Stack step. Regions gives the candidate’s score at each region and the region’s weight. Metrics is the full table of what was measured: each term, its raw value, its goodness from 0 to 1, and its weight in the bundle; click a column head to sort. Warnings the scorer raised, such as a region skipped as stale, close the section.

How a candidate is scored
Every score is measured against the frames themselves, never against the other candidates, so the numbers mean the same thing from run to run. The frames it reads are the developed images, the same 16-bit pixels Align and Stack work on; the JPEG previews the camera embedded, which the list shows while an image is still developing, are never scored. The noise every term is read against is measured on those frames; when they are RAW, the ISO and sensor levels each file declares give a ceiling on what its sensor could have left, so a subject whose fine texture fills every frame is not mistaken for noise. A measurement outside that ceiling is noted in the run’s warnings.
- Sharpness kept: how much of the sharpness the sharpest frame has at each point the candidate keeps. 1.0 is all of it. A little more than any frame counts as sharpening and is penalised; a flat region, where no frame has detail, does not score this term at all, so noise can never read as detail.
- Tones no frame has and Colours no frame has: how many pixels fall outside the range the frames span there (the colours as chromaticity, each channel less the luma, so a lifted or dipped black is read once, as a tone, not three times as a colour). A blend of frames leaves that range only by a share of the local contrast (an engine that blends across scales lays one frame’s fine detail onto a base mixed from the others, which lands a few per cent of the local swing outside the per-pixel range on every textured surface), so a pixel further outside than a fifth of the local contrast was invented. On a flat area the local contrast is nothing and the frames’ noise alone sets the bound.
- Invented fine structure: fine detail stronger than any frame has anywhere near that point.
- Ringing at depth edges and Halo glow at depth edges: overshoot and low-frequency glow along the edges where near meets far, the signature of a halo. The glow is what a tile engine leaves when it copies a soft frame’s edge beside a sharp one, and it carries the most weight of the whole-picture terms: on a stack of pencils it is the one term that tells a fringed candidate from a clean one.
- Steps no frame has: a slope steeper than any frame has at that point, counted only where it runs along a line. A depth engine that quantises its map leaves contour bands on a backdrop, terraces whose every step is a slope no frame has there; an edge engine leaves a glow ridge with a flank; a tile engine leaves a fringe with an edge. A blend’s haze is a mix of the frames’ own slopes and stays under their ceiling, and its grain points every way at once, which is why the term asks for a line (the slope’s direction agreeing across a 21-pixel window). On a backdrop it is the term that tells a terraced candidate from a clean one; along the subject’s outline every engine reads some, so the Clean bundle is more lenient there.
- Edge matches one frame: along those edges, whether the candidate looks like one frame or like two laid over each other, the signature of a ghost or doubled edge.
- Seams between frames, Pixels from a far frame, Engine unsure: the engine’s own record of where each pixel came from, for seams on flat surfaces where the frames differ (a seam where every frame holds the same value changes nothing and costs nothing), pixels taken from the wrong depth, and places the engine could not decide.
- Grain and Texture on flat surfaces: noise relative to the frames’ own, and detail where no frame has any.
Each role is a bundle of these terms with weights: Detail leans on sharpness kept and invented structure, Clean on ringing, glow and ghosting, Smooth on grain and false texture; the whole picture has a bundle of its own. A region’s score is its bundle’s weighted mean; the composite is the regions’ weighted mean (70 %) and the whole picture (30 %), or the whole picture alone when there are no regions. A term that cannot be measured, because the engine made no provenance or a region is too small, is left out and the bundle re-weights; it is never a penalty.
Two checks reject a candidate outright, before any score: tones far outside any frame’s, and invented structure over the whole picture. A rejected candidate stays in the list, its hover saying why, so you can see what an engine did and why it lost, but it never wins. Every composite carries a noise floor from the measurements it is made of; two candidates closer than that are a tie, the ≈ in the list.
Why measured against the frames. The adjustment matrix’s scores were relative to the batch: the best of a bad run looked as good as the best of a good one. SmartStack’s are absolute: 0.9 at a Detail region means the candidate kept nine tenths of the sharpness the frames had there, whichever run or stack it came from. That is what lets a run on Monday be compared with a run on Friday, and what lets a region say “sharp” rather than “sharper than the others”.
Expert sections
Standard mode keeps Run, Regions and Result. Expert adds the four below; their values apply either way.
Engines
A checkbox per engine with its one-line character. Every ticked engine gets a baseline; the best few are then searched. Untouched, the list follows the Stack step’s ticks; All ticks every engine and Stack’s ticks follows Stack again. The gear beside an engine (… ranges) opens its numeric settings with a lo and hi each: the design samples and the refinement steps stay between them, so you can keep a search inside the values you trust. Reset in the popover frees them again. An engine that would not fit in memory at this stack’s size is skipped.
Search
How a run spends its budget. Design points is the opening spread per searched engine, at the screening size; Survivors how many of them are re-fused at full resolution; Refinement steps the coordinate steps per engine at full resolution. Shortlist is how many engines are searched (the top by composite, plus the best per region) and Shortlist cap the most it may be; Finalists how many candidates are reported best first; Keep rasters how many full-resolution results stay parked on disk for Keep image and the Candidate view. Trial units is the budget itself: a full-resolution fusion is one unit, a screening trial costs its share, and baselines always run. Runtime limit, min stops new trials after that many minutes (0 for none). Seed makes a run repeatable: the same seed and settings replay the same trials; Random draws a fresh one per run, recorded with it.
Screening view sets the reduced size the screening stage ranks at. Auto crops around the regions when the crop saves enough, else halves the resolution above 6 megapixels, else uses the full frame; Crop, Half and Full force one. Screening only ranks: every survivor is fused again at full size, and nothing scored only at the screening size is ever reported. A half-size trial means an engine’s spatial settings cover twice the pixels; a crop changes the picture’s overall statistics. Both are why the survivors run again.
Scoring
The bundles’ weights. Pick a bundle (Detail, Clean, Smooth, Whole picture) and the sliders beneath set how much each term counts in it; a count of changed weights shows in the caption. Whole-picture share is the whole picture’s part of the composite. Region area chooses how a region’s say grows with its size: Saturating (one observation, levelling off at 4096 px) or Proportional (without limit, so a large background outweighs a small eye). The two Reject sliders set the thresholds of the outright rejections. Reset scoring returns every value to the defaults.
Diagnostics
The facts of the preparation: Stack size, Crop, Alignment (solved by SmartStack, the session’s bake or the session’s), the alignment’s Residual and Fallbacks, and Use this alignment in Align when SmartStack solved it. Keep diagnostics is a preference saved with the run; it changes nothing in this build’s output. Run folder shows where the candidates are.
The Legacy sweep
Legacy sweep (Expert mode only; Standard mode never shows the sweep) is the adjustment matrix of the previous chapter, unchanged: it needs a baked, saved project, and once a run exists its outputs line up in the strip at the left and the gallery in the centre as before. File ▸ Adjustment Matrix… and Adjustment Matrix Results open the Smart tab in this mode; the Mode dropdown at the left of the sweep’s toolbar returns to SmartStack. The two modes keep their runs separately; a variant kept from either is a kept stack like any other.
Status messages on this step
| Message | When |
|---|---|
| SmartStack · preparing the images | The workspace opened on a session that is not baked; SmartStack is aligning and warping for itself. |
| SmartStack · images aligned and cropped — the session’s own alignment is untouched | The preparation finished. |
| SmartStack ready | The session was already baked; nothing had to be prepared. |
| SmartStack · aligning and cropping the stack first | The Smart path started on an unaligned stack: Align, then the crop, then the workspace. |
| Cropped — SmartStack is ready to run | The Smart path’s align and crop landed; the workspace is open on the baked images. |
| Kept … — it is the result; continue to Touch up | A keep landed on the Smart path and became the base. |
| Manual path — Align, Crop and Stack are back on the ribbon | Adjust manually was pressed. |
| SmartStack run … started / resumed | Run SmartStack or Resume SmartStack was pressed. |
| SmartStack finished | The run ended by itself. |
| SmartStack cancelled — the candidates so far are kept | Cancel was pressed. |
| SmartStack stopped: … | The run failed; the message says why. |
| SmartStack’s alignment adopted — Align shows it | Use this alignment in Align was pressed. |
| Settings applied from … — press Stack | Apply settings was pressed. |
| Settings restored — … undone | Undo apply was pressed. |
| Keeping … | Keep image is exporting and importing a candidate. |
| The kept stack is not loaded yet | Compare in Stack was pressed before the keep finished. |
| Reading the run… | The project was reopened and the run’s candidates are being read from its folder. |