For lux, you need a PTO file as input if you want to stitch. I don't now
about the templates and things you're using.
so instead of one pto per folder, so it can get the warping settings
identical over all files, i need one pto per image file set?
So, first you have to make the PTO - there are panotools scripting
programs to make one from a set of images - and then you feed the PTO to
lux. But it does replace the 'warping' with nona and the merging with
enblend.
all those similar pto files just for the imagenumber does sound a bit
excessive.
but hey, if that's the way.
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 ;)
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.
--
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/38cec6af-905d-4678-a59a-cd7186b54242%40gmail.com.
