Still with me?
I changed the semantics of --snapshot_facet=...
If this value is not passed explicitly, it defaults to -1. This tells
lux to render source-like snapshots, fusions and stitches not to the
shape and projection of a given facet, but to the *projection and shape
given in the PTO file's p-line*. I also added code to process the
cropping information in the PTO file. In sum, producing images which are
similar to the output other PTO-processing software renders is now quite
easy: Load the PTO, and press Shift+P (to stitch) or Shift+U (to fuse)
to the target specification given in the PTO. In batch mode the same
mechanism can be used, so for stitches use --next_after_stitch=yes and
--snapshot_like_source=yes, and for exposure fusions
--next_after_fusion=yes and --snapshot_like_source=yes.
Because cropped images could only be provided with correct metadata if
the target format was spherical (using GPano metadata, which are only
good for spherical) I finally decided to provide lux-specific metadata
which work for all projections lux can handle and describe image
projection and cropping. lux produces images with these metadata set,
And when it loads such images it will processed cropped images correctly.
Please not that lux still does not process all infomation in the PTO: it
ignores masks, stacks, and 'image active' flags, and also all
specifications of the type of output except for it's size, projection
and cropping, so @Thomas: if you specified in hugin that you want an
exposure fusion, you won't get it automatically in lux: in lux you have
to press 'U' or 'Shift+U' for a fusion, which may explain your failure
to do an exposure fusion.
Again @Thomas: concerning the long loading time of your panorama: lux is
memory-hungry, but there are ways to make it work with less memory (and
load faster). You can try this flag, which keeps lux from building a
good amount of interpolation structures which are not strictly necessary:
--build_pyramids=no
If your images still don't fit into memory, try
--facet_squash=1
Which is an emergency measure only and reduces resolution to one half.
Third @Thomas: during the time lux sets up, there is really nothing in
it which might respond or with which you could interact. If the blank
screen bothers you, start in windowed mode (-W or --fullscreen=no), or
just Alt-Tab to something else: it's not your computer which is
unresponsive, only lux, while it builds it's interpolators. While it
does that, it will use a lot of CPU, though, and the system may respond
sluggishly.
Kay
--
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/e140fb82-1cdd-7702-138d-cab099be8bf3%40yahoo.com.
