Guide

Troubleshooting Common CieloStitch Problems

If your stitch fails, looks wrong, or takes more memory than expected, start with the checks below.

Start with the simplest checks Focus on input quality first

Before troubleshooting

  • Make sure you are stitching one coherent panel set from the same target and session.
  • Check that neighboring images have enough overlap.
  • Try a smaller subset before assuming the full workflow is broken.

Stitch failed or alignment looks poor

The most common causes are weak overlap, inconsistent input quality, or panels that do not actually belong together. Check the data first before changing many settings at once.

  • Start with Auto engine if you are not sure whether Simple or Cielo is more appropriate.
  • For wide horizontal sweeps, consider cylindrical projection before forcing more aggressive alignment.
  • If Translation or Affine are too rigid, try Homography or APAP on a representative subset first.

Visible seams or blending artifacts

Visible seams usually mean neighboring panels differ too much in exposure, tone, sharpness, or alignment quality. Better source consistency is usually more valuable than aggressive correction.

  • If the problem is a localized double edge, the newer ghost-aware seam handling may help more than a wider global blend.
  • Inspect the strongest overlap and seam-stress areas first instead of changing many controls at once.

Some panels were ignored or mismatched

This often points to weak shared detail, outlier frames, or captures that differ too much from the rest of the set. Remove the questionable frames and retry with the strongest subset first.

The desktop app now also lets you exclude an image from the current run without removing it from disk, which is often faster than rebuilding the whole test set.

Output looks incomplete or distorted

Incomplete mosaics can come from missing coverage, weak overlap, or a panel sequence that never formed a reliable chain of matches. Distortion can also reflect limits in the source capture rather than a simple software setting problem.

Performance or memory issues

Larger mosaics naturally need more memory, storage bandwidth, and CPU time. If a job feels too heavy, reduce the test case first, confirm your system is appropriate for the project size, and then scale back up.

When to adjust capture workflow instead of app settings

Some problems start before the software ever sees the files. If the inputs are inconsistent, have too little overlap, or lack usable detail, no combination of settings will fully compensate. In that case, the real fix is a better capture plan.