Am 10.04.21 um 13:38 schrieb Harry van der Wolf:
Hi,
I did not forget about lux.
I was already doubting you... ;)
8 days ago the graphics card of my laptop gave up. Yesterday finally my
new laptop arrived after 4 days delay in the warehouse.
This morning I downloaded the latest lux from git and compiled it.
I got in general good results, but also ran it on a series of test
images and got strange effects on the edges. Note that I took a lux
version of 8~10 days old which had the same issue but also "dark areas"
in the images. As that is now "solved" in this latest version, I did not
include those images.
I tested 1.0.8 quite throroughly, so it's probably best if you pick that
version, just use
git checkout 1.0.8
to get precisely that version.
I first run align_image_stack on the images which delivers a pto.
Then I run lux with
lux -W \
--blending=hdr \
--snapshot_like_source=yes \
--snapshot_facet=1 \
--snapshot_prefix="${PREFIX}" \
--snapshot_extension=$SUFFIX \
--aeb_auto_brightness=yes \
--next_after_fusion=yes \
--build_pyramids=no \
--build_raw_pyramids=no \
--quality_interpolator_degree=1 \
--snapshot_threads=4 \
"${PTO}"
See attached my luxfuser.sh script, but renamed as luxfuser.txt
In my Google drive you will find 2 examples ...
The lux.jpg has strange "cadres" around the image.
The output is correct, even if that may be unexpected. I'll explain: you
specify '--snapshot_facet=1'. This means 'create output which covers the
same area as facet #1 (the second facet). Because the facets don't
overlap perfectly, some of the output does not have input from all
contributing images and looks different (namely the stripes along two of
the edges).
The easiest way to deal with this issue is to rely on the PTO: I've
recently coded p-line processing and changed the semantics of
'snapshot_facet'. The default for 'snapshot_facet' is now -1 (note the
minus) which tells lux: 'when doing snapshots/stitches/fusions with
snapshot_like_source, produce output as specified by the pto file's
p-line'. When I coded the p-line processing, I also added output
cropping. To get a correctly cropped result, try this:
First, you need a PTO with proper cropping info (note the -C):
align_image-stack -C -p br.pto *.JPG
Next, you call lux like this:
lux --snapshot_like_source=yes --next_after_fusion=yes br.pto
... plus any other parameters you may need. Note that these parameters
are only needed when you don't have enough memory, maybe your new
computer has enough memory now:
--next_after_fusion=yes \
--build_pyramids=no \
--build_raw_pyramids=no \
--quality_interpolator_degree=1 \
And if you're batching the job anyway, you can omit the
--snapshot_threads=4 \
lux will pick a 'good' value automatically.
p-line processing is quite a recent addition, but it's in 1.0.8 for
sure. Please let me know if this solves your issue!
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/12b1c0a8-a552-c643-2a5e-e809ce4fba28%40yahoo.com.
