53 lines
3.0 KiB
HTML
53 lines
3.0 KiB
HTML
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
|
||
|
|
|
||
|
|
<head>
|
||
|
|
<title>Luminance HDR FAQ</title>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
|
||
|
|
</head>
|
||
|
|
<body>
|
||
|
|
<h1>FAQ for Luminance HDR</h1>
|
||
|
|
|
||
|
|
|
||
|
|
<dl>
|
||
|
|
<A name="name"><dt><strong>Q: What is the meaning of the name Luminance HDR?</strong></dt></A>
|
||
|
|
<dd>A: The name can be decomposed in 3 parts: Qt-pfs-gui.
|
||
|
|
<ol>
|
||
|
|
<li><strong>Qt</strong>: the program uses Qt4 (www.trolltech.com) to show its graphical widgets.</li>
|
||
|
|
<li><strong>pfs</strong>: the main backend library and original sourcecode base.</li>
|
||
|
|
<li><strong>gui</strong>: this stands simply for graphical user interface.</li>
|
||
|
|
</ol>
|
||
|
|
</dd>
|
||
|
|
|
||
|
|
<A name="tmop"><dt><strong>Q: What is the meaning of the various settings for tone mapping operator X?</strong></dt></A>
|
||
|
|
<dd>A: To answer precisely this question one would have to explain the inner workings of the tone mapping operator X, in terms of the original research paper.<br>
|
||
|
|
At the end of the day all that matters (to some people, at least) is to fiddle with the settings until you obtain a nice result.
|
||
|
|
</dd>
|
||
|
|
|
||
|
|
<br>
|
||
|
|
<A name="exiftiff"><dt><strong>Q: Why can't Luminance HDR transfer the exif tags to TIFF files?</strong></dt></A>
|
||
|
|
<dd>A: Because the library Luminance HDR uses to perform this task (exiv2) doesn't support writing to tiff files yet. It's in the working, though.</dd>
|
||
|
|
|
||
|
|
<br>
|
||
|
|
<A name="jpegorraw"><dt><strong>Q: Should I store JPEG or RAW files for HDR?</strong></dt></A>
|
||
|
|
<dd>A: Both give the same result, provided you capture all the dynamic range in the scene. This means that with RAW files you may need to capture less files than with JPEGs. On the other hand creating an HDR with JPEG files is more "lightweight" process (reduced memory footprint). </dd>
|
||
|
|
|
||
|
|
<br>
|
||
|
|
<A name="hdrformats"><dt><strong>Q: Where can I get information about all the various HDR formats?</strong></dt></A>
|
||
|
|
<dd>A: An overview (rather technical) can be found at http://www.anyhere.com/gward/hdrenc/hdr_encodings.html.
|
||
|
|
<ul>
|
||
|
|
<li>OpenEXR: Industrial Light and Magic format, widespread use, best compression ratios. www.openexr.com</li>
|
||
|
|
<li>LogLuv TIFF: see http://en.wikipedia.org/wiki/Logluv_TIFF and http://www.anyhere.com/gward/pixformat/tiffluv.html</li>
|
||
|
|
<li>Radiance RGBE: see http://en.wikipedia.org/wiki/Radiance_%28software%29#HDR_image_format</li>
|
||
|
|
<li>PFS: This format stores the binary internal (float) representation of images. It is very size demanding, and it supported only by pfstools/pfscalibration/pfstmo, Luminance HDR and a few other applications. On the other hand it is a lossless format and supports metadata (tags).</li>
|
||
|
|
<li>Float TIFF (aka 32 bit TIFF): very size demanding (similar to pfs above).</li>
|
||
|
|
</ul>
|
||
|
|
</dd>
|
||
|
|
|
||
|
|
<br>
|
||
|
|
<A name="immediatechange"><dt><strong>Q: Can we have the tonemapping dialog apply its settings as soon as the user changes a value? In other words, can we avoid having an "apply" button?</strong></dt></A>
|
||
|
|
<dd>A: Given how the tone mapping panel is implemented right now, this possibility has been discarded.</dd>
|
||
|
|
|
||
|
|
</dl>
|
||
|
|
</body>
|
||
|
|
</html>
|