Normally with enfuse you provide differently exposed images to generate
output that has a combination of the best exposed bits - To do this
Hugin turns off any exposure correction. The result is not a normal
photo at all, the exposure varies in different parts of the image.
With 'zeronoise' you s
Just don't optimize the parameters of the "fixed" photograph.
Should be quite doable with the new xyz displacements.
** Changed in: hugin
Importance: Undecided => Low
** Changed in: hugin
Status: New => Fix Released
--
You received this bug notification because you are a member of Hu
On December 4, 2010 03:08:12 pm tmodes wrote:
> The "instant" crash is fixed (rev. 57fcdd6c2c89). A warning shows
> currently only up in default branch (rev. ed99ae8486d6), not sure if
> this should also go into 2010.4 branch, because it introduces new
> strings for translations.
If the trade-off
It is now blending the 57th image on my 64-bit machine. It has 1Gb of
memory allocated. This should have been entirely possible on my 32-bit-
machine too. It might be enblend 3.2 on the 64-bit machine, so then it
would be a regression of 4.0 that it can't handle the larger panos
anymore.
OK. Testi
This is a duplicate of another bug. I'm not able to quickly find that
one to mark it as "duplicate", but to make it disappear under the radar,
I'm going to mark it as "fix released" but in fact the problem is still
there.
Apparently Enblend 3.2 will create a "bad stitch" in the case of
"excessive
The "instant" crash is fixed (rev. 57fcdd6c2c89). A warning shows
currently only up in default branch (rev. ed99ae8486d6), not sure if
this should also go into 2010.4 branch, because it introduces new
strings for translations.
What's about the original report, is point 2 still valid?
--
You rece
The first can be achieved by setting "MAKEFLAGS=-j 2" or higher.
The second one is also already possible: run nona with -t 1
See description in the help on panotools:
http://wiki.panotools.org/Panorama_scripting_in_a_nutshell#Parallel_make
--
You received this bug notification because you are a
- "Export" saves all cp detector settings, not only the selected one (therefore
point 1 and 4 are invalid)
- The missing extension is fixed in repository.
- I can not reproduce the empty setting file (on windows it is correctly
saved). I added a "Flush" to explicitly save it. This hopefully fixes
Wow..- I commented on this one and I don't recall if it is the old
preview or the fast preview? currently we need the old preview because
the fast one still can't display HDR images, but sooner or later we'll
hopefully get rid of the old preview
** Tags added: preview
--
You received this bug n
** Tags added: errormessage usability
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/678891
Title:
SVN: Window with error of autopano exceeds screen size
Status in Hugin - Panorama Tools GUI:
** Tags added: crash optimizer photometric
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/678890
Title:
photometric optimisation seems to ignore image settings
Status in Hugin - Panorama Tools G
** Changed in: hugin
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/678926
Title:
remapping of single HDR image
Status in Hugin - Panorama Tools GUI:
** Changed in: hugin
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/678933
Title:
decimal precision
Status in Hugin - Panorama Tools GUI:
Fix Released
Public bug reported:
Applies to Harry's new beta2 of Hugin-2010.4.0 bundle as of 4 Dec 2010.
- clicking "Export" in Prefs -> CP Detectors if no entry is selected
opens a file dialog that assumes that a setting could be exported.
Instead, the Export button should be greyed if no entry is selected
Yuv, I was not talking about auto-cp-finders. It's the interactive tool
I started all this about.
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/679162
Title:
Different FOV's -> Weird estimations
P.S. And in this case, it's fine to have nona NOT use multiple CPUs. Let
"make" handle the parallelism. -> Also a wishlist item for "nona":
option not to use MP. (if not already, couldn't find it...).
--
You received this bug notification because you are a member of Hugin
Developers, which is sub
** Tags added: enblend
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/679974
Title:
Allow assignment of "image priorities"
Status in Hugin - Panorama Tools GUI:
Triaged
Bug description:
Dea
It seems it depends on something I don't have under control. I just
tried 4 times to reproduce this, and it didn't happen.
(but I didn't report it the first time it happened. I only reported it
when it happened to me again!)
--
You received this bug notification because you are a member of Hugin
Tomas, Currently the progress reporting is already much better than
before: previously autopano-sift would update the gui continuously and
the text output only every now and then. This resulted in lots of CPU
time wasted for updating the screen, which could have better been used
in working on findi
Ad's pano is 0.8 Gigapixels and crashes with a bad alloc on "nona",
while mine is 0.5 Gpixels, and crashes at the "enblend" step Bug #685105
. (he's on windows, I use Linux).
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https:/
Having different modes to indicate control points would be good. The
exact way to implement this has not yet been fixed:
What I would suggest is less of a change I think:
If you click on a point in the preview (in "cp mode") with the control
point tab selected it will (try to) add the controlpoin
I agree, Saving the control point accuracy can benefit some automatic
processing.
** Changed in: hugin
Importance: Undecided => Wishlist
** Changed in: hugin
Status: New => Triaged
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed
That setting is for the assistant, not for the "images tab".
Wishlist item: Make these the same anyway. Users expect it.
** Changed in: hugin
Status: New => Triaged
** Changed in: hugin
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member
Could you attach your pto file and your ".mk" file?
It seems that the "make process" cannot spawn a new process for a simple
case. What happens if you open a "command" terminal and type "make" and
"gnumake"? (I expect one of them to fail with command not found.)
Next use notepad to edit makefile.
** Changed in: hugin
Status: New => Incomplete
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/683698
Title:
error during stitching
Status in Hugin - Panorama Tools GUI:
Incomplete
Bug
Public bug reported:
Enblend failed with:
enblend --compression=LZW -m 1200 -w -f135659x3947+0+1091 -o pano8110_l.tif
...
enblend: info: loading next image: pano8110_l.tif 1/1
enblend: out of memory
enblend: std::bad_alloc
This is a simple 0.5Gpixel panorama I shot. And agreed, Hugin di
26 matches
Mail list logo
