I have just forked Hugin++ from the latest revision of Hugin and
fastPTOptimizer from the latest revision of libpano13 and merged my changes
into them.
The updated sources and the Hugin++ build for Windows can be downloaded
here:
https://sourceforge.net/projects/huginplusplus/files/development/
That'll work fine.In -fsr mode, it will compare that brown color to the
expected blue color, determine a zero probability that it is actual sky,
and thus leave the color as is.
In normal mode, blending starts 50% of the way between the green line and
the yellowish line at the top, so it
On Friday, February 11, 2022 at 8:07:30 PM UTC-5 eljef...@gmail.com wrote:
>
>
> I would greatly appreciate reports on compilation problems. I have NOT
> worked with the CMake files, I've only updated my local Makefile.
>
It compiled fine for me (using the CMake changes Thomas gave you) on
I just finished building a fork of hugin and a fork of libpano13 and
unmodified enblend on Windows using MSYS2 / mingw64
I tested barely more than opening an existing project, so there is a good
chance some operations won't work because of errors I made in building.
I ran into a massive string
I would appreciate some suggestions on what operations in Hugin are slow *and
*likely to be significantly affected by the quality of code generated by
the compiler.
Most slow operations in image processing are dominated by cache misses, so
the compilation quality makes no actual difference.
Hmm, give that link another try -- I haven't used google drive in that way,
and I think I needed to change the access so anyone with the link can get
it.
Answering your final question -- yes, full sky replacement will replace all
pixels that are likely to be sky. Internally, a very
Thankyou.
On Saturday, March 5, 2022 at 11:01:24 AM UTC-5 eljef...@gmail.com wrote:
>
> https://drive.google.com/drive/folders/1ds5QHI4qNYqXOLNexS0Ov6Ll14HnhkSV?usp=sharing
>
> Hopefully you can see those files.
>
Not yet. I clicked on the "request access" button.
>I retract my advice
https://drive.google.com/drive/folders/1ds5QHI4qNYqXOLNexS0Ov6Ll14HnhkSV?usp=sharing
Hopefully you can see those files. I retract my advice to use darktable's
retouch tool -- there is a lot of sensor dust.
I ended up scaling the image by 50% because it was taking so long, but
skyfill did
I also uploaded updated binaries:
https://bitbucket.org/kfj/pv/downloads/lux-1.1.0-pre-2.deb
https://bitbucket.org/kfj/pv/downloads/lux-for-windows-portable-1.1.0-pre-2.zip
Kay
On Saturday, March 5, 2022 at 10:20:07 AM UTC+1 kfj wrote:
> Am 04.03.22 um 17:13 schrieb Robert Clausecker:
> >
> >
Am 04.03.22 um 17:13 schrieb Robert Clausecker:
I've now started working on the packaging.
Great!
Could you tell me which git commit your prerelease is based on? I need
something to work off.
I noticed that your master branch is still on a 2021-12-15 state and
development seems to be
10 matches
Mail list logo
