First, a warning:  After posting the above, my testing determined there is
quite a bit of processing needed to massage a raw image into a useful 16
bit image.  I don't know how to do that extra processing.  I looked at
other programs using the same code as libRaw and was unable to follow what
they were doing and empirically found even they were better than not doing
any extra processing, but not really correct:
The conversion to JPG done inside the camera does a better job of noise
elimination and a better job of interpolation than any program I've tried
for reading the raw file.  The JPG loses lots of range vs. the raw file.
I'd like to know how to get similar noise reduction and interpolation to
what the camera would do itself but preserve the range.  RawTherapee does
that badly;  Other programs do it worse;  My own code in my fork of Vigra
is still worse, likely bad enough to not really be any use.

It can import raw images and preserve the extra bit bits (that the JPG
format has thrown away) but the result is generally worse than the JPG
(depending on how much you needed the extra bits).  While it is more
convenient than first converting to tiff with RawTherapee, it isn't as good
quality.

I hope to someday more carefully study the code in RawTherapee and figure
out what I should have done.  But for now, I've set it aside and I'm
working on other aspects of Hugin++

So trying my code might be a waste of time, unless you know enough about
what ought to be done to fix it, or you are just curious.



On Sun, Jul 31, 2022 at 11:18 AM Tommy Hughes <[email protected]>
wrote:

>
> Hi, I want to try this but not sure how to build it?
>
>
I had a hard time myself in getting Vigra to build.  I'm incompetent with
Cmake and always fumbling around in the dark when it comes to getting Cmake
to find things.

I get things to work mostly by editing the CmakeCache.txt file and fixing
the NOTFOUND entries to point to the right places.  It would be more
correct to convince Cmake to find things, but with only one big exception
that I've run into, editing the cache to make it think an earlier run found
the thing works.
The hard part is guessing what it wanted:  Typically there is some file and
it wants the path of the directory that contains that file and if you
figure out what file you can find it and give it the directory path.  But
it just identifies the package it wants, which is split across multiple
directories and you don't easily know which of those it wants.

I assume you went directly to building my vigra without ever learning to
build the original vigra.  Mine is flawed in how it searches for libraw
(I'd really appreciate someone competent in cmake telling me what I should
have done).  It looks like more is wrong than that (things that would also
fail if you were building the official vigra).  But I'm not sure.

It certainly looks like you are missing some of the packages that are
described as optional here:
http://ukoethe.github.io/vigra/doc-release/vigra/Installation.html
such as libjpeg and libtiff
For practical use of vigra with hugin, those really aren't optional.

The problem that is almost certainly my fault is:
Using RAW   libraries: RAW_LIBRARY_RELEASE-NOTFOUND

My (fedora) build of my vigra has these lines in CMakeCache.txt
//Path to a file.
RAW_INCLUDE_DIR:PATH=/usr/include/libraw
//Path to a library.
RAW_LIBRARY_RELEASE:FILEPATH=/usr/lib64/libraw.so

I suggest verifying that those exist on your system (libraw is installed)
and then editing those lines in your CMakeCache.txt and rerunning cmake and
seeing how much gets fixed.

-- 
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/CALe0Q_%3Dcx7AL5nxZHKZ%3DpkEqyeHFxJeP_kij1hY%3D01-%3Dg%2B4AYg%40mail.gmail.com.

Reply via email to