Hi, can you upload one of these JPEG files somewhere?
--
Bruno
The images work in Hugin/linux (I only tested the first one).
Strange.
Cheers,
Seb
> It is not as bad as it sounds, because usually you have enough control
> points to make the focal length/HFOV/equivalent a parameter determined
> during optimisation. Just make sure you do not enter a completely
> crazy value at the start, optimisation will later sort it.
I think the original problem was that the image could not be open by
hugin at all, while improper reading of exif data might be a subsequent
problem.
P.S. I do not use hugin on Windows, so cannot say.
Milan Knizek
knizek (dot) confy (at) volny (dot) cz
http://www.milan-knizek.net - about linux and photography
start with exiftool - it comes with hugin and is in the hugin\bin folder
of the Windows installation.
from a DOS windows, run exiftool with the -U option, i.e.
C:\> exiftool -U image.jpg
and post it here so that we can see what kind of exif data is available
if any.
Yuv
thanks. It looks OK.
> Field Of View : 47.3 deg
> Focal Length : 6.8 mm (35 mm equivalent: 41.1 mm)
as a work around, enter these values when asked.
I am puzzled as to why hugin can't read them - I've tried to open the
files you posted earlier and it prompts me to enter HFOV and Focal
Length as well.
Yuv
I could open the files here, on Windows, with the same hugin version you
are using. The only thing that hugin did not recognize where FOV and
focal distance for which you have been given a workaround with the
exiftool -u command.
This is just temporary. As Gary pointed out, reading EXIF takes care in
an upstream library, exiv2. All hugin binaries for Windows known to me
are currently built against version 0.16 of exiv2. in the meantime there
has been 0.17 and 0.17.1 which are probably available in most linux
distributions (explaining the different behavior) and 0.18pre (that
introduces TIFF writing).
I have tried to build 0.17.1 on my windows box and failed. I have had
more success building the debug version out of SVN. I'll improve on that
and feed it into a future hugin windows binary when I have time. Or
maybe somebody else step in in the meantime.
Until then, use the workaround.
Yuv
note that hugin *opens* project files, not images. Images are added to a
project. what are you doing to "open" the images?
Yuv
no, you are doing it the same way I do that with the images you posted a
couple of days ago, with the same version of hugin you are using.
I am at loss explaining what is specifically wrong in the chain of
events on your computer.
on my computer it is "only" the exif data. I'll try to get a newer
version of exiv2 and build a newer version of hugin with it and hope it
improves for your images on my computer.
in the meantime, on your end, if you have access to a different
computer, try installing hugin on it and see if it can process your images.
sorry I can't be of any more help.
yuv
I would also propose to first try if hugin can at least read some other
image file type like TIFF or PNG. If so, you can also try to re-save
(not just copy) your camera JPEGs as JPEGs with another program or
possibly strip EXIF data from the files.
If you do not have a program for converting file types, try IrfanView
(www.irfanview.cz - also in the Czech language), it has a batch
processing functionality as described here
http://www.irfanview.cz/tips.php#davkova_konverze
There are also programs, which can remove metadata from JPEGs (i.e.
EXIF, IPTC, etc.) - e.g.
http://www.rainbow-software.org/programs.html#JPG%20Cleaner
best regards,
Milan Knizek
Only one other user has managed to reproduce your problem, and this
was because he had Cyrillic characters in the path. Have you any
"special" character in your path/image names? are the two Windows
versions the same in terms of regional/language/character set
settings?
Cheers,
Seb