On 22.04.24 12:29, Maarten Verberne wrote:

all those similar pto files just for the imagenumber does sound a bit excessive.
but hey, if that's the way.

There's nothing stopping you from modifying the PTO files as text files with any old text processing tool. But lux needs a PTO file which does not contain any placeholders or such.

I'll take your post as an inspiration, though, and think about ways how to make templating possible with lux. I already have some (undocumented) code which I think could be bent to the task - I'll post again if I can figure something out. It will probably need additional command line parameters or a .lux file wrapping the .pto

You'll have to refer to exiftool decumantation for that.

I did, but i wasn't clever enough to make it work. let's leave it there ;)

Yes, exiftool is quite a mouthful. This is another thing on my list - I'd like to have settings in lux which pick a given set of attributes from the source file(s) and move them to the target. I already handle EXIF metadata (you can have a selection displayed in the status line), but so far the only metadata I write to the output are the ones describing the geometry and cropping of the image. In my scripting, I use something like this to propagate the metadata:

    exiftool -overwrite_original \
             -tagsFromFile "$SOURCE" \
             -All:All \
             '-DateTimeOriginal>FileModifyDate' \
             "$TARGET"

Just make a single PTO first, see how it stitches with lux, and if you get the knack of it, you can try several in one go. Good luck!


i've just downloaded lux 1.2, but one imageset is no test for me, so i'm going ahead with making a bunch of pto files. only than can i compare different light conditions throughout the day and see how it runs as i would use it.

Making PTO files with scripting tools from the hugin toolset is not difficult. I use pto_gen, cpfind and autooptimiser. I prefer making a new PTO for every batch of images, to be sure the registration is correct. And when I fuse stacks, I use align_image_set, which can also expert PTOs.

--
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
--- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/hugin-ptx/e2bd62d2-c92b-49ba-8d61-5467df742e4c%40yahoo.com.
  • [hugin-ptx] lu... 'kfj' via hugin and other free panoramic software
    • Re: [hugi... David W. Jones
      • Re: [... 'kfj' via hugin and other free panoramic software
      • Re: [... Maarten Verberne
        • R... 'kfj' via hugin and other free panoramic software
          • ... Maarten Verberne
            • ... 'Kay F. Jahnke' via hugin and other free panoramic software
              • ... Maarten Verberne
                • ... 'Kay F. Jahnke' via hugin and other free panoramic software
                • ... Maarten Verberne
                • ... 'Kay F. Jahnke' via hugin and other free panoramic software
                • ... Maarten Verberne
                • ... 'Kay F. Jahnke' via hugin and other free panoramic software
                • ... Maarten Verberne
    • Fwd: [hug... David W. Jones
      • Re: [... 'kfj' via hugin and other free panoramic software
        • R... David W. Jones
          • ... 'kfj' via hugin and other free panoramic software
            • ... David W. Jones

Reply via email to