Hugin 2014 and 2015 "No or only partial information about field of view was found in image file"

[Bob Mahar]

Hi,

Since Hugin 2014 and 2015 I get

"No or only partial information about field of view was found in image file"

when adding any image from my Pentax K-5.

Its also rather frustrating since on answering the dialog asking for the FoV you are prompted again... for each of the 300+ images selected.  Any other EXIF viewer I try shows expected crop factor and focal length.

To work around you cancel out, select all images, then specify Lens 0.

This was never an issue prior to Hugin 2014.

What does it want?

-- Bob

[Terry Duell]

Hello Bob,

This is curious.
I have never had any problems with JPG images from my Pentax K-30 or K-3
II.
Do you shoot RAW and then convert to JPG or TIFF prior to importing into
Hugin?
If you shoot JPG could you make a test image available (Dropbox or
similar?) that exhibits this problem?
What OS are you using?

Cheers,
--
Regards,
Terry Duell

[Terry Duell]

On Tue, 22 Dec 2015 15:24:14 +1100, Terry Duell <tdu...@iinet.net.au>
wrote:

>
> This is curious.
> I have never had any problems with JPG images from my Pentax K-30 or K-3
> II.
> Do you shoot RAW and then convert to JPG or TIFF prior to importing into
> Hugin?
> If you shoot JPG could you make a test image available (Dropbox or
> similar?) that exhibits this problem?
> What OS are you using?

Another thought, Hugin uses exiv2. Is your lens data in the version of
exiv2 used for your version of hugin?
If you need to you can check which version of exiv2 was used by starting
hugin then select Help -> About and select System.

[Gnome Nomad]

I sometimes get that. I usually click Cancel, then Hugin just brings them all in and gets the info correct.

But I usually use pto_gen (Hugin's 'Create PTO from images'?) to create the PTO file for panos. It always seems to get it right.

--
A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ
---
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hugin-ptx+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/554a83ce-680c-496d-a0e9-80aeb13d0480%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Bob Mahar]

These are JPG out of the camera.  Now that you mention the lens databases, seemed to start after the Hugin, et al, choice to switch lens databases after 2012.  IIRC it was lensfun previously.   This might also explain some of the issues I am seeing in terms of distortion correction.   OK, so I'll look there.

-- Bob

[Terry Duell]

Hello Bob,

On Sun, 27 Dec 2015 12:34:50 +1100, Bob Mahar <muhl...@gmail.com> wrote:

> These are JPG out of the camera. Now that you mention the lens
> databases, seemed to start after the Hugin, et al, choice to switch lens
> databases
> after 2012. IIRC it was lensfun previously. This might also explain
> some of the issues I am seeing in terms of distortion correction. OK,
> so I'll look there.
>

I'm sailing close to the edge of my memory and knowledge with this, and
may be steering you in the wrong direction.
I now do recall an issue with a new lens not being recognised because it
wasn't in the exiv2 data, but I think that really only affected hugin
knowing the lens name, I don't recall having issues with hugin not knowing
imported image parameters.
Having your lens in the exiv2 data does make it easier when it comes to
saving the distortion parameters.

[Bob Mahar]

Sort of an update...  it is definitely not bringing in the lens correction parameters.  Exiv2 does not have the Samyang 14 in its database - or so it seems.   This also explains some of my fairly recent failures where either rhe photometric or alaignment is wrong.  On looking back on those projects the distortion and vignetting settings are all zero, with the exception of Barrel, which is set when Barrel is added as a optimizable parameter.

This brings me to the next thing.... so on trying to create a lens profile using the Hugin lens profiling tool, there does not seem to be a means to select or define your own vertical or horizontal lines, only the automatic detection.   Am I missing some user interface element?  I remember being able to do this previously.

I should be able to crib the proper lens settings from successful bobs run using 2012 or 2013 version.

-- Bob

[Terry Duell]

Hello Bob,

On Thu, 31 Dec 2015 05:03:19 +1100, Bob Mahar <muhl...@gmail.com> wrote:

> Sort of an update... it is definitely not bringing in the lens
> correction parameters. Exiv2 does not have the Samyang 14 in its
> database - or so it seems. This also explains some of my fairly recent
> failures where either rhe photometric or alaignment is wrong. On
> looking back on those projects the distortion and vignetting settings
> are all zero, with the exception of Barrel, which is set when Barrel is
> added as a optimizable parameter.
>
> This brings me to the next thing.... so on trying to create a lens
> profile using the Hugin lens profiling tool, there does not seem to be a
> means to
> select or define your own vertical or horizontal lines, only the
> automatic detection. Am I missing some user interface element? I
> remember being
> able to do this previously.
>

Hugin Lens calibration GUI doesn't give you the option of defining your
own lines, it does it automagically.
You can load images, which contain vertical and horiz. lines, into
hugin-2015.0 and define those lines, optimise, then save the lens data.
Does that help?