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
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), a
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
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:
http
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. W
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 i
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 wrote:
> On Feb 1, 6:28 am, Chris Parrish
> wrote:
> > I am building a script that batch creates PTO and PTO.MK files for
> > sets of p
On Feb 1, 6:28 am, Chris Parrish
wrote:
> I am building a script that batch creates PTO and PTO.MK files for
> sets of pano images. I do this based on templates of these files (I
> use a pano head allowing me to reuse the same script settings in these
> templates).
>
> The problem is that, while
