** Changed in: enblend
Status: New => Fix Committed
** Changed in: enblend
Importance: Undecided => Medium
** Changed in: enblend
Assignee: (unassigned) => Christoph Spiel (cspiel)
--
You received this bug notification because you are a member of Hugin Bug
Hunters,
First if all, this is one of the most stupid and thus misleading
bug-report titles I've seen for a long time! What about:
"Cannot blend images with different bit depth"?
- The input image's bit depth is so deeply encoded in both Enblend
and Enfuse that it would be very hard to extend their func
This report does not belong here at all. It is not a problem related to
the source code of Enblend (or Enfuse). Quite the contrary is true:
we have the feature of compiling with or without EXR support. Obviously,
the original poster's version was built without it. The error message
couldn't be
This report does not belong here. If the set of libraries on the user's
machine is incomplete, incorrectly set up, or plain broken, we can't help it.
** Changed in: enblend
Status: New => Invalid
** Changed in: enblend
Importance: High => Undecided
--
You received this bug notificat
This is not a bug, but standard UN*X behavior: options start with a dash;
GNU (long) options start with two dashes.
Every decent libc that implements getopt_long(3) ought to accept a
freestaning double-dash, i.e. `--' as option-end-marker.
Under Linux both Enblend and Enfuse honor this marker. S
The command-line parameter passed with
"--exposure-mu" does not define the "middle
gamma value", but the luminance Y (of an input
pixel) in the normalized luminance interval [0,
1] that gets the highest weight in fusing.
Probably, you can achieve what you want by
rewriting the definition of w_{\ma
ogress
** Changed in: enblend
Assignee: (unassigned) => Christoph Spiel (cspiel)
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/885324
Title:
Completely replace lcms1 by lcms2 in Ubuntu
Fixed in rev d0828152af73.
** Changed in: enblend
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/885324
Title:
Completely replace lcms1 by lcms2 i
Wrt the compilation error: your "config.h" is broken.
Symbol STRERROR_R_CHAR_P is meant to prevent exactly this problem.
Wrt to the exception: It has nothing to do with your bogus patch; the
novel highlight recovering algorithm, a 1D Brent minimizer, did not find
the required precondition.
(1) Th
Rev b50c132ee40c widens the search interval:
http://enblend.hg.sourceforge.net/hgweb/enblend/enblend/rev/b50c132ee40c
Hopefully, your "not bracketed" problems will go away with it.
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Enbl
** Changed in: enblend
Assignee: (unassigned) => Christoph Spiel (cspiel)
** Changed in: enblend
Importance: Undecided => Medium
** Changed in: enblend
Status: New => Fix Committed
--
You received this bug notification because you are a member of Hugin Bug
Hunters,
The OpenMP M4 check macro is up to date, so the check proper ought to be
ok.
You say: "I do specify the -fopenmp flag in my... I get perfect openmp
versions".
So, is the compiler ./configure uses when checking your system a _different_
compiler than the one you can successfully pass the "-fopenmp
Try the current development head, i.e. rev add97764deef or later.
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/787387
Title:
small artifacts in fused 16bit TIFFs
Status in Enblend:
Confir
Should be fixed in the current head, i.e. rev add97764deef.
Please test and close the report if the bug has been squashed.
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/752283
Title:
Blending
1. The option "-m" only affects the image cache.
If Enblend/Enfuse are built w/o it they automatically /
"naturally" use all available (virtual) memory.
2. You can get a more dynamic adjustment of the
image cache size by tapping the free(1) or vmstat(1).
tools or directly consulting /proc/meminfo.
1. Completely agreed: we'll see more RAM-loaded machines in the
future and thus the image cache will use more of its appeal.
2. You convinced me not to change anything in Enblend/Enfuse's
image cache sizing by showing my the code of sort(1). So much
code and ad hoc constants for so little.
** C
WRT"artifacts in dark areas are still there": We need a minimal
set of (preferably small) images that clearly show the problem. Please
attach them to _this_ bug report.
The faulty CIECAM blending, which was the cause for some weird
colored pixels is fixed in _both_ applications: Enblend and Enfus
Your proposal sounds sensible and I wonder why nobody came up with
something comparable before. Also surprising for me was the general
ignorance of your suggestions in the news group.
Adding all your technical-merit parameters would put a lot of baggage
into Enblend and Enfuse. The next day some
Without small images to reproduce the problem, this is fly-by-night-in-
deep-fog hacking.
Let's see whether we can narrow down the issue.
1. Please make sure you are using the _non_ image-cache version of Enblend.
We do not want to trip over an image-cache bug here. Though the image-cache
bu
Kay,
I think your idea to improve Enblend or Enfuse is really
worth being implemented. In fact I find your suggestion
so stunningly obvious that I wonder why it did not garner
more interest in the newsgroup.
My plan to implement your proposal would be to code
_none_ of it directly in Enblend
If you cannot trigger the bug anymore -- for whatever reason,
I'll close this issue and mark it as fixed.
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/787387
Title:
small artifacts in fused
** Changed in: enblend
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/787387
Title:
small artifacts in fused 16bit TIFFs
Status in Enblend:
Fix Com
Duplicate of #685105
** Changed in: enblend
Status: New => Invalid
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/985476
Title:
enfuse stops when 36 Mp 16bit Tiffs are used.
Status i
I have three different Vigra installations on one of my boxes
and never encountered your kind of problem. Anyhow, your
patch neatly separates different types of flags, so I
massaged it a bit and applied it as changeset
5d810b904e5d.
** Changed in: enblend
Status: New => Fix Committed
**
The linker invocation looks sick. It lacks (at least)
-lboost_filesystem -lboost_system
Presumably, the error msg comes from a missing
libboost_system. This is a configuration problem.
Are you using GNU's configure or cmake?
At the end of its run configure(1) tells you, whether
it has request
I don't have access to OSX, so you might want to ask
Harry van der Wolf or Ingemar Bergmark, who are the
Mac-builders in our team.
As you confirm that adding "-lboost_filesystem -lboost_system"
fixes your problem, you can also pass option
--with-boost-filesystem
to ./configure. It forces the
I have forwarderd the problem to Harry an Ingemar.
With respect to your problem with "--with-boost-filesystem":
I was (implicitely - as almost always) talking about the current
head of development in the hg repo. There, both Boost
libs get added with the "--with-boost-filesystem" option.
Anyhow,
Fixed in cb7d1cf15223.
** Changed in: enblend
Status: New => Fix Committed
** Changed in: enblend
Importance: Undecided => Medium
** Changed in: enblend
Assignee: (unassigned) => Christoph Spiel (cspiel)
--
You received this bug notification because you are a member
** Changed in: enblend
Importance: Critical => Medium
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/787387
Title:
small artifacts in fused 16bit TIFFs
Status in Enblend:
Fix Committed
Fixed in rev57a56d454739, though fix curtails functionality:
no alpha masks in output images.
** Changed in: enblend
Status: Confirmed => In Progress
** Changed in: enblend
Assignee: (unassigned) => Christoph Spiel (cspiel)
--
You received this bug notification because you
Export-with-alpha just does not _compile_ anymore with the new Vigra-library.
No trivial fix in sight. Patch highly welcome.
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/685877
Title:
Push VI
The fix's status of course is "committed" not "released".
** Changed in: enblend
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1039900
Title:
co
We now have a patch that re-installs all prior functionality
with respect to loading and saving images with alpha-channels.
However, the copyright of the new (it is in fact a complete
rewrite) file "impexalpha.hxx" must be sorted out before we can
add it to the repository.
--
You received this bu
LMAO! This reminds me of
http://www.youtube.com/watch?v=Qvk2wNWmB20
Solution: Use a 64bit version of Enblend
to construct images of 1GPx+.
** Changed in: enblend
Status: New => Invalid
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is sub
Yuval -
The copyright issue boils down to the
question whether the new file "impexalpha.hxx" is a
"substantial portion" of the old Vigra code
"impex.hxx" (The quote comes from Vigra's MIT
license.) We are sorting out this one.
On another side we still have problems with the
Graph Cut algori
The copyright problems were ironed out.
The new file "impexalpha.hxx" will be part of the Enblend
project under the same license as all other sources
namely GPL Version 2.
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Hugin.
https://b
I assume you build within the source tree. Prefer VPATH-builds
and the issue of overwritten *.1 and *.info files will go away.
The version labeling, e.g. "enblend-4.1-123deadbeef", is completely
intentional; it distinguishes and (almost) uniquely identifies
development versions. If you are fed u
If you can't stand how the automake-generated
"dist" target works, simply whip up your own.
Change all necessary "Makefile.am"; just make
sure you don't break existing functionality of
our build-system.
You have commit rights to the repo, so go ahead.
For extra points assign this issue to yoursel
The log file gives it away: "out of memory".
There are two ways Enfuse can be configured: one is with the so-called
"image cache" that ought to make the user independent of the system's
memory, but which is slow and non-parallel, and then there is the configuration
without image cache that is fast
Problems should be fixed in rev 29ec0c175c5a -- fingers crossed.
** Changed in: enblend
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/685877
Title:
According to Kornel this is a duplicate of
https://bugs.launchpad.net/enblend/+bug/1055303
i.e. not a bug, but outdated Vigra library.
** Changed in: enblend
Status: New => Invalid
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to
** Changed in: enblend
Status: New => Triaged
** Changed in: enblend
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1055303
Title:
Compiling for debug
** Changed in: enblend
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1023037
Title:
Enblend fails to build with boost 1.50
Status in Enblend:
Fix Co
** Changed in: enblend
Status: New => Fix Committed
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/752283
Title:
Blending errors when using CIECAM
Status in Enblend:
Fix Committed
B
Always nice when problems magically fix themselves.
To add my 2 cents: This error message or closely related ones
occur if the _product_ of (any) images' height*width exceeds
INT_MAX, which is 2147483647 on many of today's machines (even
so-called 64-bit systems). We cannot do much about it, beca
** Changed in: enblend
Status: New => Incomplete
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1101539
Title:
output from blending program cannot be found
Status in Enblend:
Incompl
Your output images indeed show a problem. Whether it is
related to Enblend or you feeding Enblend inadequate, i.e.
non-overlapping input images cannot be determined w/o
the actual input images.
Please supply your two (or three) input images which
allegedly cause the problem.
--
You received
** Changed in: enblend
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1101539
Title:
output from blending program cannot be found
Status in Enblend:
Inv
You supplied three input images to Hugin, namely
"_1020988.jpg", "_1020989.jpg", and "_1020990.jpg". As they
stand, they are _not_ suited for input in Enblend, because neither
are they aligned, nor do they have an alpha-channel.
To track down a problem, we need input image sets suited for
Enbl
"test_pano_2.zip" contains the same unsuitable files
as did your first zip archive. Don't you read my comments? Or
don't you know what you are doing at all.
Once again, we need two or more images we can directly
feed into Enblend, like so
enblend image1.tif image2.tif
Nobody gives a
Thanks for the patch! It has been applied to both branches.
So it will definitely make it into the first release of the brand
new `stable' 4.1 series.
** Changed in: enblend
Assignee: (unassigned) => Christoph Spiel (cspiel)
** Changed in: enblend
Status: New => Fi
** Changed in: enblend
Status: New => Incomplete
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1102174
Title:
Enblend 4.0 output better than Enblend 4.1
Status in Enblend:
Incomplet
Fixed in 4.1.1.
** Changed in: enblend
Importance: Undecided => High
** Changed in: enblend
Status: New => Fix Released
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1124837
Title:
Wish granted in rev 13c7fe6a2d25.
User-defined exposure weight functions implement the ideas.
The "extension" language is C++, though and not Scheme.
** Changed in: enblend
Status: Triaged => Fix Committed
** Changed in: enblend
Assignee: (unassigned) => Christo
Thanks for the _really_ minimal example. ;)
I tried the following spell:
$ enblend --fine-mask --no-optimize --primary-seam-generator=nft
img_7306-731700*.tif
with the tip of the development branch and got the following warning
enblend: images do not overlap - they will be combined witho
** Attachment added: "Enblend output image"
https://bugs.launchpad.net/enblend/+bug/1153546/+attachment/3568485/+files/a.tif
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1153546
Title:
b
> ... choosing nft doesn't make a difference
> with respect to my problem
You are using a pre-release of Enblend
version 4.1. Therefore, your default PSG is
NFT, I'm on the development tip and GC is the
default here, thus I had to force NFT and you
found no differences. Makes sense.
>
Please work on the _tips_ of either the development branch
(currently: http://hg.code.sf.net/p/enblend/code/rev/b0b27f8c7de1)
or the stable branch (currently:
http://hg.code.sf.net/p/enblend/code/rev/881360218998),
for your version is
(i) ancient, i.e. we won't fix anything there anyhow and
(ii) i
The patch is nonsense because all "Makefile.in"s
are re-generated by every run of configure(1).
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1155350
Title:
build with texinfo 5.1
Status in
** Changed in: enblend
Status: New => Triaged
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1155350
Title:
build with texinfo 5.1
Status in Enblend:
Triaged
Bug description:
The
Can we set the status to "Won't Fix" or better "Invalid"?
This looks like an Automake/Autoconf problem.
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1155350
Title:
build with texinfo 5.1
St
If you pull from the repo, you'll get pseudo-namespace free documentation,
for I dropped all prefixes "CFG::" and "src::". Maybe, crown-of-stupidity
Texinfo-5.x won't barf on this one.
OTOH, I'd rather replace Texinfo with Hevea than removing the dashes from
(Texinfo-)variable names like `visuali
THX for feeding the doc into Texinfo-5.1 again.
I'm still on makeinfo-4.13, so I cannot check myself yet.
Thus, the problem will remain unless someone sends us a patch.
On a medium time-scale I'm inclined to switch to plain LaTeX
and drop Texinfo. The vast majority of users doesn't read the
docum
THX for tracking down the problems in detail.
#1: Patch in my local repo; probably will be applied.
#2: Screwing up the output is not the way to go. We can
prevent unwanted whitespace from occurring by terminating
the relevant lines with `@c', though:
@classictimes{}@c
thereby
You can just bump the version forward.
Please adjust "configure.in" accordingly.
Patch is candidate for 4.1.2.
** Changed in: enblend
Status: New => Triaged
** Changed in: enblend
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Hugin
Try tip of development branch.
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1228601
Title:
Emblend Error Minimizer1D
Status in Enblend:
New
Bug description:
enblend: an exception occur
Read your own log file and you find Enblend's comment:
enblend: warning: only one input image given.
enblend: warning: Enblend needs two or more overlapping input images in
order to do
enblend: warning: blending calculations. The output will be the same as
the input.
which is correct
You ran out of disk space. Perhaps the partion where
/tmp gets mounted is small.
The particular version of Enblend you are using (ImageCache)
is best for systems with little memory, but lots of free disk space.
Prefer the version without ImageCache to benefit from lots of RAM.
** Changed in: en
We can't smell error messages. You must show them to us in the "Bug
Description".
** Changed in: enblend
Status: New => Incomplete
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1214004
** Changed in: enblend
Status: New => Fix Committed
** Changed in: enblend
Importance: Undecided => Medium
** Changed in: enblend
Assignee: (unassigned) => Kornel (kornel-benko)
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscrib
OK -- a few words from your chief
maintainer of Enblend/Enfuse.
1. ImageCache
Any ImageCache support has been removed
from the development branches of Enblend and
Enfuse. It won't come back unless some brave,
brilliant, ... hacker steps up and takes
responsibility for the code. Thus, I
Martha, my dear -
You are right, I cannot reproduce the problem here on any
of my (Debian/SuSE) Linux boxes.
If EXR is your only problem, I can suggest to you that you switch to
16-bit TIFF, 16-bit PNG, or 32-bit floating-point TIFF. EXR's `half'
float suffers from a short significant anyhow
Oops! Sorry, I was off-by-one in the
exponent. 8-/ The largest _signed_ integer
(`int') typically is 2**31 - 1, not 2**32 - 1.
The latter is correct for _unsigned_ integers
(`unsigned int'). However, your calculation
still holds even with the half-as-large limit.
> Another thing that would be
(1) You could re-run Enfuse with a higher verbosity setting.
See the Enfuse manual for a description of the levels.
(2) You could re-run Enfuse under the supervision of a debugger.
Keep your fingers crossed that your binary contains (enough)
debugging symbols.
This should give us more
complete => Fix Committed
** Changed in: enblend
Importance: Undecided => Medium
** Changed in: enblend
Assignee: (unassigned) => Christoph Spiel (cspiel)
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Enblend.
https://bugs.la
There you go: fixed in 4.1.2, i.e. rev ac3dd60b8c45.
** Changed in: enblend
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1214004
Title:
Enfuse
Fixed in 4.1.2.
** Changed in: enblend
Status: New => Fix Released
** Changed in: enblend
Importance: Undecided => Medium
** Changed in: enblend
Assignee: (unassigned) => Christoph Spiel (cspiel)
--
You received this bug notification because you are a member of
Should be fixed in 4.1.2.
** Changed in: enblend
Status: Triaged => Fix Released
** Changed in: enblend
Importance: Medium => Low
** Changed in: enblend
Assignee: (unassigned) => Christoph Spiel (cspiel)
--
You received this bug notification because you are a member
** Changed in: enblend
Assignee: (unassigned) => Mikolaj Leszczynski (rosomack)
** Changed in: enblend
Status: New => In Progress
** Changed in: enblend
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is s
THX keafert for trying out Enblend on large panos. You have
convinced me that we can close this issue, because "enblend
fails to blend large pano" is not a bug in the program. You
proved that it is plain user incompetence, using wanna-be O/Ss,
or, in summary nothing we can fix.
The sizes of more
THX kaefert for trying out Enblend on large panos. You have
convinced me that we can close this issue, because "enblend
fails to blend large pano" is not a bug in the program. You
proved that it is plain user incompetence, using wanna-be O/Ss,
or, in summary nothing we can fix.
The sizes of more t
** Changed in: enblend
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/685105
Title:
enblend fails to blend large pano
Status in Enblend:
Fix Commit
Check out rev 6d6c88dcdc63 or later. Keep optimization
switched off and -- at your discretion GraphCut -- to get
reliable results.
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/785803
Title:
** Changed in: enblend
Status: New => Incomplete
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/685875
Title:
severe ghosting in cloud row
Status in Enblend:
Incomplete
Bug descript
Check out rev 6d6c88dcdc63 or later. Switch off optimization
and -- at your discretion GraphCut -- to get reliable results.
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/721136
Title:
enblen
** Changed in: enblend
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/785803
Title:
Enblend --no-optimize produces black holes into panoramas
Status in Enbl
** Changed in: enblend
Status: New => Incomplete
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/989908
Title:
black lines from graph-cut seam generator
Status in Enblend:
Incomplete
Please add your (pair of) input images to this issue report
such that we can test with the latest revision of Enblend.
** Changed in: enblend
Status: New => Incomplete
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Enblend.
htt
Could someone please attach a suitable pair of input
images to this bug report? We have no test-cases
here.
THX!
** Changed in: enblend
Status: New => Incomplete
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Enblend.
https:/
@Lukas: (i) GraphCut is absolutely unchanged in 6d6c88dc,
(ii) after its recent re-implementation it is again WIP
according to its author.
Please run with NFT only to see whether this fundamental
step now works any better. BTW, GraphCut uses NFT as an
educated guess.
If you have a reasonably siz
Lukas,
THX for your minimal example! Admittedly, I cannot
reproduce your "foo.tif" with rev 6d6c88dcdc63, i.e.
current tip. I tried any image order, NFT, GC, w/optimizer,
and wo/optimizer. The result _always_ looked ok and
never showed any black areas. Moreover the seam line
(`--visualize'
@Frederic: Thanks for investigation the problem!
>From revision 502d69450811 Enblend and Enfuse require
at least Little CMS version 2.5. We hope to backport the patch
to the stable series soon.
** Changed in: enblend
Status: Incomplete => Fix Committed
** Changed in: enblend
Importan
WRT your original errors. They point to outdated OpenCL header files.
Ask your sysadmin to get the most recent versions from
http://www.khronos.org/opencl/
and install them in the appropriate place.
Next thing on her agenda is to update the OpenCL libraries to their
latest versions. Again, t
Technically, your Boost headers (and libraries) are too old.
So, this is not an Enblend/Enfuse problem.
I have just committed a patch that requires at least
Boost version 1.55 to build Enblend and Enfuse.
** Changed in: enblend
Status: Fix Committed => Won't Fix
--
You received this bug
** Changed in: enblend
Status: New => Won't Fix
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1305794
Title:
OpenCL enabled build fails
Status in Enblend:
Won't Fix
Bug description
This is not an Enblend (or Enfuse)
problem. Both applications rely on the Vigra
library for I/O of images of _any_ format, i.e.
the functions described in
https://ukoethe.github.io/vigra/doc/vigra/group__VigraImpex.html
This is in fact one of the main reasons to use
an imaging library as e
** Changed in: enblend
Importance: Undecided => Wishlist
** Changed in: enblend
Status: New => Triaged
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1316967
Title:
Maximum TIFF fil
g any of them to the stable branch.
** Changed in: enblend
Status: New => In Progress
** Changed in: enblend
Importance: Undecided => Low
** Changed in: enblend
Assignee: (unassigned) => Christoph Spiel (cspiel)
--
You received this bug notification because you are a m
Committed #0001 in
http://hg.code.sf.net/p/enblend/code/rev/18a9c1d411ac.
** Changed in: enblend
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/13323
We'd need a set of input images for Enblend that clearly reproduce
the problem preferably with the tip of the development branch.
Otherwise we waste our time with guesswork.
--
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Enblend.
https:
1 - 100 of 166 matches
Mail list logo
