How to Troubleshoot Wormlike Artifacts in Focus Stacks of Textured Surfaces

Zerene’s FAQ explains a specific mechanism behind worm trails: dust or defective pixels produce spots in the source frames. Alignment holds the subject steady while those spots shift relative to it, allowing the stack to retain a trail of false detail. Dark trails commonly indicate dust; bright trails can originate from warm pixels. Appearance alone is insufficient to identify the cause. Zerene Stacker FAQ

Open several original frames before alignment. At the same magnification, inspect the area associated with one conspicuous trail. Compare image coordinates, rather than following a particular grain or fiber across the frames. Record whether a spot stays fixed within the image while the subject changes position.

Use the following as a diagnostic sequence, rather than a classification based only on appearance:

What you find	Next check
A spot repeats at the same original image coordinates	Investigate a defect trail and correct the inputs
No fixed spot, but texture doubles or shifts between aligned frames	Inspect alignment and subject movement
Sources look clean, but one stacking method creates swirls	Check frame order, illumination and method settings
The affected texture is never sharp in any source frame	Revisit capture coverage before further processing

For confirmed dust or pixel defects, Zerene recommends removing them before stacking when prevention was not possible. Its dust-and-defects mask uses black marks on a white background, matching the source images’ size and orientation; this is a Pro-only feature. Alternatively, defects can be removed in an image editor before stacking, or trails retouched afterward. Zerene Stacker FAQ

Work on copies. Correct one representative area first, render again, and compare it with the untouched result. On a textured surface, inspect whether the correction has replaced a defect with a repeated grain, interrupted fiber or conspicuously smooth patch. Expand the correction only after this small test looks convincing.

Keep alignment enabled during this test. The documented mechanism explains why alignment reveals the trail, but the useful intervention is to address the unwanted spots while retaining alignment of the subject.

If you find no fixed defects, browse the stack from beginning to end. Confirm that focus progresses continuously through the surface, and look for brightness changes or subject displacement. Helicon Focus 9’s Stack Browser supports this inspection: its Show Adjusted control switches between original frames and frames with alignment adjustments applied. Helicon Focus 9 User Guide

Pay particular attention to repeated motifs. Pick one distinctive intersection, pore or scratch and watch whether it remains registered after adjustment. Inspect several locations, including the affected patch and an apparently clean area. This makes the comparison more informative than judging the overall image at a reduced size.

Frame order deserves its own check. Zerene’s DMap tutorial shows that randomly ordered focus positions can produce swirls and halos; exposure variations can produce similar effects. It recommends sequential focus order and stable illumination, with brightness correction available for some exposure variation. How To Use DMap

Correct an identifiable ordering problem before testing smoothing. If illumination changes across the stack, compare a render with the application’s brightness compensation enabled, while watching both the affected texture and its surrounding tone.

Make a second render using a different algorithm while keeping the source set unchanged. Zerene describes PMax as effective at preserving fine and overlapping detail, with possible increases in noise and contrast or shifts in color. DMap better retains smoothness and color, with different detail limitations. The developer explicitly recommends combining their strengths where necessary. How To Use Zerene Stacker

In Helicon Focus, Method B builds a depth map and requires consecutive image order; Method C uses a pyramid approach. These descriptions provide a useful comparison to test, but they do not make settings interchangeable between applications. Understanding the Focus Stacking Parameters

Compare the same crop at the same display scale. Include three features: an affected patch, nearby genuine fine detail and a surface edge. Prefer the result that preserves their structure together. A smoother patch is an improvement only if the neighboring texture still looks credible.

For Helicon Methods A and B, Radius controls the neighborhood analyzed when assessing focus. Increasing it can reduce artifacts but can also soften fine detail. Smoothing affects blending in Methods A and C and smooths the depth map in Method B. These are distinct controls, so test them separately. Helicon Focus 9 User Guide

For Zerene DMap, Estimation Radius controls the detail scale considered during focus selection; Smoothing Radius affects transitions between source images. Its contrast threshold helps exclude unreliable low-contrast information. Too little thresholding can let noise drive selection, while unsuitable radius values can create halos or lose detail. How To Use DMap

Use this controlled comparison:

1. Save a baseline render and note its settings.
2. Change only the focus-estimation radius; compare a smaller and larger setting.
3. Keep the better radius and test smoothing separately.
4. In Zerene DMap, adjust the threshold while watching which real details remain included.
5. Render the preferred combination at full resolution before accepting it.

For example, imagine a paper surface where a higher radius removes winding blotches but also merges neighboring fibers. That is an illustrative tradeoff, not a measured result. Keep the finer-detail render available and consider a local repair instead of applying the stronger setting everywhere.

When most of the stack is satisfactory, repair the remaining patches locally. Zerene allows retouching from individual input frames or other stacked outputs. It also documents stacking a selected subset of frames and merging that result into the full stack. How To Use Zerene Stacker

Find the source frame where the affected patch is clearest. If one frame cannot cover the patch’s depth, try a small substack containing the relevant focused region. Transfer the corresponding detail in small areas, checking texture continuity and the repair boundary after each pass.

Before retouching, confirm that usable detail exists. Zerene’s DMap tutorial demonstrates an important limitation near overlapping structures: a background region may never appear both sharply focused and free from foreground blur in any input. In such a case, source-based retouching has limited material to work with. How To Use DMap

Use the source-frame inspection to make the decision. Continue processing when a clean input patch or alternative render supplies the detail you need. Consider reshooting when the required texture is consistently blurred, displaced or obscured across the available frames.

For the next capture, keep the viewpoint and illumination stable, minimize subject movement, and use consistent focus increments. These are the capture conditions emphasized in the Helicon manual. Check a small trial stack before completing the full series. Helicon Focus 9 User Guide

Finish by inspecting the repaired crop beside its best source frame, then review the full image at its intended display size. Stop when the false trails are resolved and the real texture remains coherent. The strongest diagnostic evidence is the change you can trace from source frames to alignment, rendering and the final repair.

• FAQ: Frequently Asked Questions — Zerene Stacker
• How To Use DMap — Zerene Stacker
• How To Use Zerene Stacker
• Helicon Focus 9 User Guide
• Understanding the Focus Stacking Parameters — Helicon Soft