This is the FOV on the long side, right? not the narrow side. on a
crop (1.5) sensor?
On Feb 1, 7:44 am, Chris Parrish chris.parr...@swankinnovations.com
wrote:
Oops, forgot to post the two values:
These are with a Nikon D70...
RAW:
v133.377308103937 a-0.0140794442639724
On Jan 31, 3:25 am, Bruno Postle br...@postle.net wrote:
For some reason I don't see any GSoC 2010 related discussion in this
group :) Are we not attempting to do participate again?
How did we start it off in previous years?
Usually Yuv and me started asking who is willing and will be to
Am Monday 01 February 2010 schrieb Lajos Höss:
pano_projection_parameter'
You probably have to first install the corresponding pano13-headers (and
libraries)
Kornel
--
Kornel Benko
kornel.be...@berlin.de
signature.asc
Description: This is a digitally signed message part.
Chris, I've recoded some of this in python. If this is what you're
scripting, msg me and I'll send it to you.
nick
On Mon, Feb 1, 2010 at 4:11 AM, bruno.postle brunopos...@googlemail.comwrote:
On Feb 1, 6:28 am, Chris Parrish chris.parr...@swankinnovations.com
wrote:
I am building a script
I found that the export to PTmender script does not include the
parameters of the projection.
This bug should be fixed in rev 4956
Thomas
--
You received this message because you are subscribed to the Google Groups
hugin and other free panoramic software group.
A list of frequently asked
Hi Lajos,
I try compile the 4954 trunk hugin on UHU-Linux 2.1. I see this
error: Any idea?
current hugin trunk requires libpano version rev 1236 from subversion
repository. So you need to compile and install a libpano13 from
subversion repository. Then this errors should be gone.
Thomas
--
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
Actually, it looks like Hugin is not compensating for ISO Speed. The
values that it's using are more like:
( 2*log($aperture) - log($et) ) / log(2)
I'm not sure if that's a bug in Hugin or intentional.
And I can't find any documentation that shows that EXIFTOOL calculates
EV at all. Does/can
Ok, so perhaps I've found a Hugin bug. The EV's I posted earlier were
auto calculated by Hugin when I added my JPEGs to the project. I just
selected them all now and did a reset in the camera tab (selecting
only to reset the EXIF values), and now they are all properly
(consistently) calculated.
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) -
hdrpano wrote:
I had the same problem a month ago. Concluded that nona is unable to
preserve hdr when remapping. Let me know if you figure this out...
It should work, if you set the Camera response type to linear.
(Lens tab, photometric sub tab).
cheers,
Pablo
--
You received this
use the exiftool -n option to bypass the print formatting
which limits the number of decimal points displayed.
--
You received this message because you are subscribed to the Google Groups
hugin and other free panoramic software group.
A list of frequently asked questions is available at:
Use the exiftool -n option to avoid the print formatting which
is reducing the number of displayed decimal points.
The exiftool LightValue calculation uses these values.
- Phil
--
You received this message because you are subscribed to the Google Groups
hugin and other free panoramic software
On Sun 31-Jan-2010 at 16:54 -0800, Daniel M. German wrote:
Also, it would be nice if nona embedded the script in the output file
(the way that PTmender does).
..or at least wrote some EXIF metadata so the output from Hugin can
be loaded into Hugin with the correct Field of View
On Mon 01-Feb-2010 at 10:15 -0800, Chris Parrish wrote:
Ok, so perhaps I've found a Hugin bug. The EV's I posted earlier were
auto calculated by Hugin when I added my JPEGs to the project. I just
selected them all now and did a reset in the camera tab (selecting
only to reset the EXIF values),
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
A libpano13-2.9.17_beta1 (first beta snapshot) tarball has been
uploaded to sourceforge:
https://sourceforge.net/projects/panotools/files/libpano13/
This is an interim 'beta' primarily useful for users wishing to try
Hugin development snapshots, the
On Mon 01-Feb-2010 at 22:14 +, Bruno Postle wrote:
A libpano13-2.9.17_beta1 (first beta snapshot) tarball has been
uploaded to sourceforge:
https://sourceforge.net/projects/panotools/files/libpano13/
This is an interim 'beta' primarily useful for users wishing to try
Hugin development
Hi everybody,
I think it would be great if the build scripts of hugin should force
this version
--dmg
On Mon, Feb 1, 2010 at 2:25 PM, Bruno Postle br...@postle.net wrote:
On Mon 01-Feb-2010 at 22:14 +, Bruno Postle wrote:
A libpano13-2.9.17_beta1 (first beta snapshot) tarball has been
On Mon 01-Feb-2010 at 14:53 -0800, Daniel M. German wrote:
I think it would be great if the build scripts of hugin should force
this version
libpano13 installs a libpano13.pc file, so the way to do this is
in Hugin is with the cmake pkg-config module.
--
Bruno
On Mon, Feb 1, 2010 at 2:25
On Mon 01-Feb-2010 at 14:49 -0800, hdrpano wrote:
There's a warning from hugin_hdrmerge about only one input image but
again, I'm not sure if that's related.
Yes, why are you trying to 'merge to HDR' photos that are already HDR?
--
Bruno
--
You received this message because you are
Hi,
I already installed the libpano13 2.9.15 beta3 complete package.
I compile the newest (svn1259) trunk libpano13, the problem solved. Thanks!
Now i find the new useful forum messages, 2.9.17 beta1 libpano13. I
will recompile the autopano-sift-c too. Thanks, again.
Now has an another problem,
Hi,
* Should Hugin be calculating EV taking ISO speed into account?
I think it probably should. I had noticed this too with
auto-exposed photos, but ignored it.
Hugin is reading Exif.Photo.ISOSpeedRatings and using it for
calculation of the ev value.
So it should take the iso value into
22 matches
Mail list logo
