I should say now that on HDR panoramas stitched from many (e.g. 35+)
exposures, now I am almost always getting this bug, which renders the
entire HDR black. If I stick the EV=0 and EV=+2 exposures then I get a
usable HDR, but when include the EV=-2 exposures I get a black output.
--
You received
Also agree that the TIFF workaround does not work in the latest version
of hugin on OpenSuSE 11.4
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/678694
Title:
EXR files quietly clipped (black rec
wxWidgets stores long integers in the Windows Registry as DWORD keys
that are 32-bit unsigned integers. Hugin was reading these as signed
integers, so anything above 2047 was read as negative and displayed as
1; values above 2047 were properly saved, just displayed incorrectly. I
committed a fix fo
** Summary changed:
- windows 7 not full access c:/
+ windows 7 not access c:/
** Summary changed:
- windows 7 not access c:/
+ windows 7 not access %systemdrive%
** Description changed:
sorry me rus...
Windows 7 = not full access to %systemdrive% ...
give me configuration button thi
** Attachment added: "log file"
https://bugs.launchpad.net/bugs/780228/+attachment/2121913/+files/fuk.log
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/780228
Title:
windows 7 not full access
Public bug reported:
sorry me rus...
Windows 7 = not full access to %systemdrive% ...
give me configuration button this compilled patch
or
use system patch (hugin) this create subdir tmp.
please next time ... bug=windows
** Affects: hugin
Importance: Undecided
Status: New
--
Yo
** Attachment added: "Error log and Proj files.7z"
https://bugs.launchpad.net/bugs/780208/+attachment/2121880/+files/Error%20log%20and%20Proj%20files.7z
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net
Public bug reported:
Creating a pano named "IMG_9036-IMG_9080" fails while naming it
"IMG_9036-IMG_9080 full" works just fine. Weird. Same exact image set,
same control points. I tried remaking the pano, and it failed again on
the default name. I changed it to "IMG_9036-IMG_9080 2" and it worked
f
64 bit
2011.0.0.8f1447ab8649 built by Matthew Petroff
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/761231
Title:
Image cache memory can't be set above 2047MB
Status in Hugin - Panorama Tools G
Are you using a 32-bit or 64-bit build?
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/761231
Title:
Image cache memory can't be set above 2047MB
Status in Hugin - Panorama Tools GUI:
Confirme
On May 8, 2011 04:29:43 PM Bruno Postle wrote:
> In your testcase _MG_7851_hq.JPG really is grayscale and the other two
> are RGB, so the error message is correct.
*blush*. I thought there was no such thing as grayscale with jpeg
compression.
> Were these images processed by ImageMagick?
yes,
I can now confirm that what I saw in comment #3 is not related to this
thread. My error was due to an image being in the wrong format. It
also caused bug 779563. I will file e separate ticket for that. Apology
for the thread hijack.
Agree that manually limiting the number of cores should not be
12 matches
Mail list logo
