Op 23-Apr-24 om 8:11 schreef 'Kay F. Jahnke' via hugin and other free
panoramic software:
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 already experimented with that :)
just made almost 10.000 pto files this morning.
alas it'll still take until this weekend before i'm able to test.
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
since this method would entail generating a million extra pto files, i
would obviously welcome it.
and that might be a lot, but also take into account that with
nona>enblend, the system creates and destroys twice as many temp images
and i have no problem accepting that.
so what's best is probably personal and i might be the only one
interested in templating the filename.
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"
thanks, much appreciated. i'll see if i can make this work.
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.
for me, the text editing way is much easyer because i only have the
folder and image number that i need to change and i can automate that.
--
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/272df08f-83c3-4c02-bfe1-0e760b5f47ce%40gmail.com.
