How to determine commands for "Load Images..."

29 views
Skip to first unread message

Mikey

unread,
Jun 16, 2020, 12:14:00 PM6/16/20
to hugin and other free panoramic software
Hello in the Hugin GUI you can use the button "Load Images..." in the Simple view interface to load images. I noticed that it takes some time and it there appears to be some processing when a user loads images using this button in the GUI.

Is there a way to determine what commands are run when I import several images using this button? I noticed that Hugin will estimate the Yaw of each image and give a rough alignment when I import images using the "Load Images..." button. 

However, when I generate a pto file from the command using something like the following the project files are just simply generated and the yaw is not estimated. How can I determine what commands are run using the "Load Images..." button in the GUI versus generating a pto file using the command line below?

pto_gen *.JPG -p ${LENS} -f ${FOV} -o project.pto

T. Modes

unread,
Jun 16, 2020, 2:19:18 PM6/16/20
to hugin and other free panoramic software


Am Dienstag, 16. Juni 2020 18:14:00 UTC+2 schrieb Mikey:
Hello in the Hugin GUI you can use the button "Load Images..." in the Simple view interface to load images. I noticed that it takes some time and it there appears to be some processing when a user loads images using this button in the GUI.

Is there a way to determine what commands are run when I import several images using this button? I noticed that Hugin will estimate the Yaw of each image and give a rough alignment when I import images using the "Load Images..." button. 
I'm not sure I completely understand what you mean.
In the preferences there is an option "Automatically align images after loading".
When this option is ticked, then the images are completely aligned (with the assistant) after loading. The equivalent at the command line is here hugin_executor --assistant.
When this option is disabled, then the images are roughly distributed (depending on number of images and field of view). But this is done dumb without taking the image content into account. It just puts the first image left and the last one on the right (or when there are more images in several rows). But this is no estimation and no calculation. (From the command line something similar can be achieved with pto_var).

Thomas
Reply all
Reply to author
Forward
0 new messages