Sorry, I’ve exhausted my knowledge on how hugin might be calculating and using
these numbers; it doesn’t seem to match the theory written up in the links I
put up.
Would any of the developers / support guys have any thoughts on this for Kai?
Don
> On Sep 18, 2018, at 11:04 AM, Kai M wrote:
>
Hey Donald,
i tried everything to calculate. But i cant figure out the parameters. The
Exif Data is readable. The Distance was 40cm from the object. Do you think
its possible to calculate it in Pixels?
Best Regards
Kai
--
A list of frequently asked questions is available at:
This is where I would have to switch into experiment mode. Maybe someone with
more experience on this could help.
Was you camera at about 60 cm from the object as my calculation in the previous
response showed? Did hugin have access to all the exif data in the image so it
knew focal length
Hello Doanld,
Thank you very much for your answer. Slowly I understand it. But I have
another question:
I move the camera with an accuracy of <1mm over the target. Now I want to
try to skip the step of CP detection and calculate the positions of TRx TRy
myself and create a pto file.
Perhaps this link might help … I had to read it very carefully a few times …
even though English is my first language.
The picture in the link is from the perspective of someone looking down on you
standing at the origin 0,0,0.
>From your camera's point of view taking the picture looking at the
It is just a 2D Object. Stitching works very well if i only optimze TRx and
TRy. But i try to understand in which dimension these Parameters. On a
camera movement of round about 30cm i get a TRx of 0.521 . I try to
understand this number.
--
A list of frequently asked questions is available
Kai, is this a 3D object? I believe Mosaic Mode is meant for 2D images like a
picture or mural. A 3D object will introduce parallax errors that will make it
hard to stitch unless you are really careful in placing control points and then
masking out any overlaps.
Kind regards from Canada.
Don
