Jesper W-2 wrote:
BUT it has somehow lost its HDR dynamic range. The file format is
still HDR (I tested both exr and TIFF/Float), but the actual pixel
data has lost its dynamic and is kind of remapped to LDR values.
I started out using Hugin to create the project, and then went on to
bruno.postle wrote:
EV (light value) is fairly standard, Hugin should be doing it the same
as exiftool (and does as far as I know).
It's a log scale where a value of 0.0 is defined as f/1.0 at 1.0
second with ISO 100), this is how it is calculated:
(2*log ($aperture) - log($et) -
]: http://wiki.panotools.org/Panorama_scripting_in_a_nutshell
[2]: http://wiki.panotools.org/Panotools (old and not complete)
2010/1/28 hdrpano rfc...@gmail.com
Does anyone know of any tool or method to automatically determine the
values
to use for cropping a circular fisheye, on the command
Does anyone know of any tool or method to automatically determine the values
to use for cropping a circular fisheye, on the command line? I'm pretty
sure the answer is no but just want to make sure...
--
View this message in context:
I'm trying to create control points in hugin with panomatic and getting a
weird problem. There are 3 fisheye images. The control points for 2 of the
image pairs are okay but for the 3rd, all the control points are outside the
crop circle. Anyone see this before?
--
View this message in
hdrpano wrote:
I'm trying to create control points in hugin with panomatic and getting a
weird problem. There are 3 fisheye images. The control points for 2 of
the image pairs are okay but for the 3rd, all the control points are
outside the crop circle. Anyone see this before?
To add
Bruno Postle wrote:
No idea, maybe you need to calculate the camera response of your
sensor for reuse in your template project.
Can you run the same project through photometric optimisation? i.e.
calculate vignetting and camera response, and see if you have the
artefacts in HDR
(part of the hugin
package).
Hope this helps.On Fri, Dec 4, 2009 at 2:29 AM, hdrpano rfc...@gmail.com
wrote:
Thanks for the replies! It would be nice to be able to do everything on
the
command line, including finding control points. But for now, I'm choosing
control points by hand
Bruno Postle wrote:
On Thu 03-Dec-2009 at 23:29 -0800, hdrpano wrote:
This doesn't work. I'm not sure what's wrong yet but the pano.exr
doesn't seem to be hdr. It looks like a very bright and washed
out ldr. Will investigate more tomorrow.
hugin_hdrmerge doesn't do any automatic
hugin handle all this black void in the image, is this ignored
in
blend fusing?
2009/12/3 hdrpano rfc...@gmail.com
Focal length: 8 mm
Focal length multiplier: 1
HFOV (v): 257.89
I enter the first two and hugin fills in the HFOV. Shouldn't that be
closer
to 180?
--
/O
--
/O
Thanks for the replies! It would be nice to be able to do everything on the
command line, including finding control points. But for now, I'm choosing
control points by hand and writing out a PTStitcher file, replacing the
filenames to stitch each exposure. For example, to create 5 panos for 5
Hi all, I'd like to script something to automate the creation of HDR pano.
I'm using a circular fisheye and taking 3 sets of exposures, 120 degrees
apart.
My first thought is to use hugin to generate the .pto and .pto.mk. Then
replace the filenames as needed. Does this sound like the right
12 matches
Mail list logo
