Artefacts after enfuse

Bug #1576862 reported by Alex Fliker on 2016-04-29
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Enblend
Undecided
Unassigned

Bug Description

Source files: https://fliker09.tk/sharedstuff/Source.zip
Result: https://fliker09.tk/sharedstuff/Enfused.tiff
WARNING! Big files.
Command: enfuse --depth=16 -o Enfused.tif {1..7}.tiff
These color pixels drives me crazy, I can't understand why they appear...
If additional information required just ask!

Christoph Spiel (cspiel) wrote :

See the Appendix B of the current Enfuse Manual on `How to Report Bugs',
in particular version of binary and image set size.

Alex Fliker (fliker09) wrote :

It is actually A.2 :) But anyway thanks for pointing!

So, the missing information is:

1) enfuse --verbose --version
enfuse 4.1.4

Extra feature: dmalloc support: no
Extra feature: image cache: yes
  - environment variable TMPDIR not set, cache file in default directory "/tmp"
Extra feature: OpenMP: no

Supported image formats: BMP EXR GIF HDR JPEG PNG PNM SUN TIFF VIFF
Supported file extensions: bmp exr gif hdr jpeg jpg pbm pgm png pnm ppm ras tif tiff xv

Supported following globbing algorithms:
  literal
    Do not glob. Treat filenames as literals.
  none
    Do not glob. Treat filenames as literals. (alias)
  sh
    Glob like UN*X shells do. Like "wildcard" plus '{', '}', and '~'. See glob(7). (alias)
  shell
    Glob like UN*X shells do. Like "wildcard" plus '{', '}', and '~'. See glob(7).
  wildcard
    Glob with wildcards '?', '*', '[', and ']'. See glob(7).

Version 4.1.4+dfsg-5/unstable - Thu, 28 Jan 2016 19:34:42 +0100

Copyright (C) 2004-2009 Andrew Mihal.
Copyright (C) 2009-2015 Christoph Spiel.

License GPLv2+: GNU GPL version 2 or later <http://www.gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by Andrew Mihal, Christoph Spiel and others.

2) Kubuntu 16.04 amd64

3) "image set size" - do not understand what do you mean. Can you please clarify?

Christoph Spiel (cspiel) wrote :

If using option `--no-ciecam' or future-proof option
`--blend-colorspace=identity' fixes the problem this
report is a duplicate of #752283.

Alex Fliker (fliker09) wrote :

Yes, --no-ciecam helped, thanks! Before your comment I didn't know that enblend has the same problem - I confirmed that after solving the issue with enfuse. Why CIECAM is enabled by default if it is known to produce problems (and actually worse looking results)? And one more thing --blend-colorspace=identity is unknown to both enfuse and enblend (newer version is needed?).

Christoph Spiel (cspiel) wrote :

For information on any option, like, e.g. `--ciecam' or `--blend-colorspace'
consult Chapter "Invocation" of the Enblend and Enfuse manuals. The
history of options ("new", "withdrawn", etc.) is only recorded in file
"NEWS", though.

To get a glimpse of the mathematics behind blending colors and thus
why the RGB-cube is a stupid choice please read chapter "Color Spaces"
in the same manuals and deepen your knowledge by following the links
in the text.

Changed in enblend:
status: New → Fix Committed
Alex Fliker (fliker09) on 2016-09-23
description: updated
description: updated
description: updated
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers