On Nov 11, 1:28 pm, "bruno.postle" <[email protected]> wrote:
> On Nov 11, 1:10 pm, kfj <[email protected]> wrote:
>
> > I've taken up work again on my pto parser in Python.
> > The syntax I am refering to comes along as a
> > comment, but it seems to contain relevant information nevertheless.
> > Examples are
>
> > #-hugin  cropFactor=1.60931
> > (in a pto file generated by hugin)
>
> > #-imgfile 2856 4290 "/home/kfj/Bilder/IMG_0068.tif"
> > (in a pto generated by panomatic)
>
> They are comments, so they are ignored by nona etc... when stitching.
> The #-hugin lines are used by the hugin GUI to store non-critical
> metadata as key=value pairs.  Your parser should at least  preserve
> them, though we don't have a spec.
>
> The #-imagefile lines are not used by hugin, they might be something
> to do with ptgui.

Yes, PTGui, PTStitcherNG, and possibly others, use #-imagefile lines
for the source image dimensions and file names (though I believe both
still accept a name at the end of the o line).  So if you want to
handle PTGui project  files you should extract the data from these
lines.

The main dialects of PT script (libpano12, Hugin/libpano13, PTGui and
PTAssembler) are diverging steadily, because there is no pressure to
keep them together; and of course there are subdialects associated
with some of the tools in each of those packages.   So I think you may
have taken on a thankless task.  A couple years ago I tried to make
APSCpp work with all 4, and though it just needs the file names,
angular dimensions and projections, I found a few irreconcilable
differences.

Cheers, Tom
>
> Have you looked at Panotools::Script which has a perl parser for .pto
> files? Perl and python are  not so different...
>
> --
> Bruno

-- 
You received this message because you are subscribed to the Google Groups 
"Hugin and other free panoramic software" group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Reply via email to