
Enfuse 4.2 requires its input images to agree on bits per channel and numeric depth. A stack containing an 8-bit image and a 16-bit image does not meet that input contract. Choosing a deeper output with --depth is not the documented way to normalize incompatible source files; prepare compatible copies before fusion.
Inspect every source, not just its extension
Section 4.1 of the official Enfuse 4.2 package manual lists agreement on depths such as uint8, uint16 and float among the input requirements. The images must also overlap.
Two files both named TIFF can still contain different numeric representations. Inspect the actual per-channel data type using a capable image inspector. Record every member of the stack, including an intermediate that may have been saved through different export settings.
A single representative thumbnail is insufficient. The incompatibility belongs to the relationship among the inputs, rather than whether one photograph opens normally.
Choose one coherent preparation route
Return to the best available originals and export compatible copies using a deliberate common representation. Verify that the chosen external tool actually writes that depth and preserves the intended dimensions and color interpretation.
Do not describe widening an 8-bit image as recovering the precision of a higher-depth original. It can make the representations agree without restoring levels already discarded earlier. The palette-loss guide explains another case where a lossless filename does not establish that all original color information survived.
Keep the original files distinct from the normalized fusion inputs. Do not repeatedly convert the only copies while searching for a working combination.
Set output depth after inputs are compatible
The input-requirements section explicitly points to --depth for a different question: output depth. That separation matters when diagnosing a rejected input set.
| Decision | What must be established |
|---|---|
| Input preparation | Every source actually uses the common required depth |
| Fusion | The compatible sources overlap and represent the intended stack |
| Output encoding | The requested depth is supported by the chosen output format |
The Photoshop filter-depth guide addresses a single document's operation availability. It should not be treated as proof that changing an Enfuse output option changes every loaded input.
Recheck the stack before retrying
For a proposed diagnostic, compare the source inventory with the newly exported copies. Confirm that one forgotten JPEG or differently saved TIFF has not remained in the command's input list. Then request a separately named fused output.
If the files now agree on depth but fusion still fails, preserve the actual error and inspect the remaining documented requirements. Input profile consistency and matching resolution metadata are recommended practices in the manual, rather than interchangeable explanations for the hard depth requirement.
No source conversion or fusion command was executed here. Acceptance begins with compatible actual inputs; an output setting or a renamed extension is insufficient evidence.
Related tasks
- Why Is a Photoshop Filter Unavailable in One Photo but Available in Another?
- Why Does My PNG Lose Smooth Colors Even Though PNG Is Lossless?
Sources and scope
- Enfuse 4.2 official package manual: Enfuse 4.2 section 4.1: all input images must overlap and agree on bits-per-channel/depth uint8/uint16/float; explicitly distinguishes --depth output depth. Profile consistency and common resolution metadata are recommended practices, not equivalent hard requirements.
Research checked on 2026-10-23 (Asia/Shanghai). Official SourceForge archive returned HTTP 200; bundled 4.2 HTML was extracted and read locally. Public standalone HTML was unavailable and is not reported as readable. Enfuse 4.2 section 4.1: all input images must overlap and agree on bits-per-channel/depth uint8/uint16/float; explicitly distinguishes --depth output depth. Profile consistency and common resolution metadata are recommended practices, not equivalent hard requirements. No software/image command, comparison or printing test was executed; 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: William Liu / Pexels, Pexels License. This is an illustrative source photograph, not an application screenshot or a generated test result.