Menu
▾
▴
Tree [8fdef7] debian/1.8.4 / History
Read Me
This is the README file for qtpfsgui v1.8.3
-------------------------------------------------------------------
Copyright (C) 2006,2007 Giuseppe Rota, <grota@users.sourceforge.net>
Webpage: http://qtpfsgui.sourceforge.net
Sourceforge: http://sourceforge.net/projects/qtpfsgui
Contents
---------
1. What it is
2. Dependencies
3. Compiling from source
4. Workflow in the gui
5. Changes
6. Contact and Links
1. What it is
---------------------------------------------------------------------
This is version 1.8.3 of qtpfsgui, a Qt4 graphical user interface that
provides a workflow for HDR imaging.
Supported HDR formats:
* OpenEXR (extension: exr, linux and Mac OS X only)
* Radiance RGBE (extension: hdr)
* Tiff formats: 16bit, 32bit (float) and LogLuv (extension: tiff)
* Raw image formats (extension: various)
* PFS native format (extension: pfs)
Supported LDR formats:
* JPEG, PNG, PPM, PBM, TIFF
Supported features:
* Create an HDR file from a set of images (JPEG, TIFF 8bit and 16bit, RAW)
of the same scene taken at different exposure setting.
* Save and load HDR files.
* Rotate and resize HDR files.
* Tonemap HDR images.
* Copy exif data between sets of images.
Raw image formats are supported -and treated as HDRs- via dcraw's code.
MAKE SURE YOU READ THE "Dependencies" CHAPTER IN THIS FILE.
Read section 4 (Changes) to read the changes for version 1.8.3.
The code is in part based on the existing opensource packages:
"pfstools", "pfstmo" and "pfscalibration" by Grzegorz Krawczyk and Rafal Mantiuk
"qpfstmo", by Nicholas Phillips.
"dcraw", by Dave Coffin.
Without their contribution all of this would have not been possible.
2. Dependencies
-------------------------------------------------------------------
Qtpfsgui has 6 dependencies (5 in windows):
1) Qt4 (www.trolltech.com)
2) exiv2 (www.exiv2.org)
3) fftw3 (www.fftw.org)
4) libjpeg (www.ijg.org)
5) libtiff (http://www.remotesensing.org/libtiff)
6) OpenEXR (www.openexr.com, **Linux only**)
On Windows you can satisfy all the runtime dependencies by downloading the ``Windows DLL Package V3'' available at http://downloads.sourceforge.net/qtpfsgui/qtpfsgui-windows-DLLs-V3.zip
On linux you have to compile the code and you need the aforementioned packages (and the ``devel'' or ``dev'' ones, depending on the distro's naming convention).
1) Qt4 is required because it's the framework the graphical interface was built on.
2) libexiv2 is a C/C++ library used to extract EXIF tags from LDR and RAW image files, and is required in order to extract the aperture, exposure-time and ISO tags from the input images (and for other exif-related functionalities).
3) fftw is required by the fast implementation of Durand tonemapping algorithm.
In particular qtpfsgui requires the "float" variety of fftw3.
4) libjpeg is required by the underlying dcraw's implementation for raw file formats.
5) libtiff is required because of the tiff load/save feature.
6) OpenEXR (www.openexr.com, Linux only)
OpenEXR hdr format is available only on linux platforms for now.
OpenEXR is a high dynamic-range (HDR) image file format developed by Industrial Light & Magic for use in computer imaging applications.
The package is also known as ``ilmbase'' on some distros.
As for the other dependencies, OpenEXR is required at runtime as well.
3. Compiling from source
-------------------------------------------------------------------
The build system is based on Qt's qmake.
The build description is contained in the project.pro file.
Running
> qmake
from the directory where there is project.pro creates the Makefile.
Qtpfsgui should be able to detect if your system has all the dependencies at the "qmake" step.
If something goes wrong drop me an email.
Then you can run
> make
to compile.
In linux you can also run
# make install
as root to install the qtpfsgui executable in /usr/local/bin.
WARNING:
In linux you have to make sure to install qt4 and qt4-devel, since most distros install only qt3. Once you have qt4 and qt4-devel installed you also have to make sure that you are using the tools from qt4 and not qt3. The tools are ``qmake'', ``uic'' and ``moc''. On ubuntu you can install the program ``galternatives'' that lets you pick from qt3's or qt4's executables.
Some people have experienced some problems using gcc 3.X.X. Switching to gcc 4.X.X seems to have solved the issue.
The Windows EXE was obtained on Windows XP using MinGW and MSYS.
In linux you have to compile the code and you need the packages mentioned in Chapter 2 (and the ``devel'' or ``dev'' ones, depending on the distro's naming convention).
If you want to compile the sources in windows you need to have a compiled
version of libexiv2 and fftw3. You also need Qt4 Opensource Edition by trolltech.
Also check the variables in the win32{} section in project.pro: they need
to be changed according to your setup.
4. Workflow in the gui
-------------------------------------------------------------------
See also the online help:
Help->Documentation...
Here I'll describe the workflow in qtpfsgui: pretty much the same
information can be found in the Help->About dialog.
From the main window you can see the buttons that enable the user
to work on HDR images:
"New Hdr..." launches a wizard that asks you to select the set of images
(of the same scene, but taken at different exposures) that are going
to contribute to the final hdr (supported input: jpeg and raw).
The wizard will also ask you which kind of configuration you want to use
to create the hdr from the source images: usually the first choice leads
to good results, so feel free to accept the default "Config 1" option
by pressing next.
Only if you feel that the results can be improved you can try one of
the other predefined configurations.
If you want to fiddle with settings you can check the "custom" option and
another page of the wizard will show up with a complete set of configurations.
It is worth mentioning that you should use the custom option as a
last resort because the predefined configurations (which are a sub-set of the
all possible configurations you can have in the custom configuration panel)
are known to yield good results.
Starting v1.5 there's also a new feature (BETA, results should be checked),
anti-ghosting: if you images are slightly misaligned or moving leaves and/or
wave ripples are in your image set, the resulting hdr has got blur (ghosting).
Enabling anti-ghosting should reduce this blur, but the feature is still beta
and very cpu demanding.
"Save Hdr as...", "Open Hdr..." and "Tonemap the Hdr...":
Once the hdr is loaded into the main workspace you can choose to rotate it,
resize it, save it (in one of the HDR supported formats) or to tonemap it.
Through "Open Hdr..." you can also choose to open an existing HDR image
format and load it into the workspace. The user can now load also a raw image file.
Clicking on the tonemap button will pop up a dialog that will enable you
to tonemap your HDR image and save to one of the plain LDR formats,
like PNG or JPEG.
The tonemapping dialog consists in a series of tabs (and related settings).
Each tab pertains to a different tonemapping operator (TMO).
You can also choose a working size different from the original
one (the TMO will be faster: this is useful for getting
a quick peek at the results of the current settings).
After you're satisfied with the results you can press the save
button to save the results to one of the plain LDR formats,
like PNG or JPEG.
NOTE:
The tonemapping step works like this (as a pipeline, some people would say):
(pre)gamma -> tonemapping operator -> (post)gamma
Now, postgamma is the usual run-of-the-mill gamma effect: it
roughly changes brightness.
The tonemapping operator transforms an HDR into a LDR.
The pregamma changes the gamma in the HDR before the tonemapping:
depending on the chosen tonemapping operator it can yield
unexpected effects like changing color saturation.
5. Changes
-------------------------------------------------------------------
v1.8.3 Giuseppe Rota <grota@users.sourceforge.net>
Added the possibility to load image files without exif data: the user will specify manually the difference in exposure values (EV or stops).
Added online documentation: manual,FAQ,hints.
The tonemapping dialog remembers the last used filename.
Fixed PowerPC compile-time alignment bug.
Fixed aperture=0 bug.
***WARNING***
The Windows users of v1.8.2 have to download the new ``Windows DLL Package V3'', make sure to get it at:
http://downloads.sourceforge.net/qtpfsgui/qtpfsgui-windows-DLLs-V3.zip
Read the Changelog file for previous versions' details.
6. Contact and Links
-------------------------------------------------------------------
All comments and suggestions concerning this package or implementation
of particular algorithm are very welcome. Please report bugs and
comments to Giuseppe Rota <grota@users.sourceforge.net>.
See also:
PFStools library:
http://www.mpii.mpg.de/resources/pfstools/
PFStmo web-page (a tone mapping library):
http://www.mpii.mpg.de/resources/tmo/
pfshdrcreate, a commandline tool used to create an HDR from a set
of LDR images (branch of pfscalibration), hosted on the same
sourceforge page as qtpfsgui:
http://sourceforge.net/projects/qtpfsgui/
PFScalibration, the original software from which the backend pfshdrcreate
was obtained (not needed for qtpfsgui):
http://www.mpii.mpg.de/resources/hdr/calibration/pfs.html
Dcraw: code used for raw images support.
http://cybercom.net/~dcoffin/dcraw/
