Max Lyons Forums

[Punkie]

Hello folks

In Hugin controlpoints are created by Autopano SIFT-C. Already version 2.5. A lot faster then Autopano SIFT(not as fast as Autopano). Does someone know if it possible to use the Autopano SIFT-C controlpoint generator of Hugin as plugin in PTAssembler and what are then the parameters?

Kind regards,
Henk Tijdink

[maxlyons]

[TKSharpless]

Hi Max,

Hugin's autopano-sift-c is a single executable that generates a
.pto file directly without an intermediate xml file. Its command line is backward compatible with autopano-sift but its most useful modes require the use of new command line options. Moreover, few of the old autopano-sift options actually work. Besides being a lot faster, the main change from autopano-sift is an option to process fisheye images in stereographic projection, which often improves CP quality.

You would definitely have to provide new support to run this program as a plugin. On the other hand it it is easy to run it from the command line and it should be possible to import the resulting .pto into PTAssembler (BTW the current Hugin writes .pto's that PTAssembler can't read -- but APSC's .pto's are very basic).

One of the new features is that you can give it a PanoTools style project file instead of a list of file names and formats, so it is quite easy to use "off to the side" of Hugin. I have not tried it with projects written by PTAssembler, but it is likely they would work.

I will try this and report back later...

Regards, Tom

[TKSharpless]

Hi again

Testing with PTAsm 5 and the version of APSC shipped with Hugin 0.7, I find...
1) APSC can't load .ptp files written by PTAsm, because the file names are hidden in comment lines.
2) PTasm can load control points from the .pto files produced by APSC.

So here would be a possible scenario for using APSC with PTAsm:
First, modify APSC to be able to load image info from .ptp files. Then process each project like this: 1) load the files in PTAsm & save project; 2) run APSC with "APSC proj.pto proj.ptp" -- the 1st name is the output file name, the 2nd is the specification file; 3) load proj.pto back into PTAsm (drag-n-drop works fine).

Running APSC from a project file like this is the best way, because it needs to know the field of view of each image, and the stitchers put that info in project files. This would enable multi-lens stitching, for example.

I could easily make the required mod in APSC if there is interest in using it with PTAsm.

Regards, Tom

[maxlyons]

Tom,

Thanks for all the research into this. I'm not going to have much time to look into this for the next week or so, but when I do get some time, I will take a look and see what it would take to be able to invoke APSC from within PTAssembler. That would seem to me to be the easiest approach...one that wouldn't require the user to switch back and forth between applications. By the sounds of it, it shouldn't be too hard to modify PTAssembler to work with APSC. I'll let you know how it goes once I get some time...

Max

[maxlyons]