RawPedia - User contributions [en]

Color Management

2018-03-27T10:11:32Z

Agriggio:

== Input Profile ==
=== No Profile ===
No input color profile will be applied. The color matrix will use "1" along the diagonal and "0" everywhere else.

* Raw files will show the camera's native RGB color. They will only be demosaiced and white-balanced.
* Non-raw files will be displayed without any embedded input profile applied, including no gamma correction, which means they will look bright.

This feature is generally only useful for didactic and scientific purposes. For example if the camera has recorded colors far outside of the conventional gamuts, using no input profile ensures that no color clipping occurs.

=== Camera Standard ===
Looks for and uses a color matrix from the DNG file, from camconst.json, hard-coded in RawTherapee, or from [https://en.wikipedia.org/wiki/Dcraw dcraw], whichever one it finds first, in that order.

A ''color matrix'' is a matrix of 3x3 constant values which is multiplied with the camera's native RGB colors to convert them to colors which are as natural as possible. A color matrix works best (i.e. provides more accurate colors) when the white balance is close to what the matrix was calibrated for. The camera standard matrix is calibrated for [https://en.wikipedia.org/wiki/Illuminant_D65 D65], i.e. 6500K. Do not worry if the white balance is quite far off from that though, color will be reasonably accurate anyway.

For applications where the most accurate and fine-tuned color is not of highest importance, such as landscape photography, the color matrix will provide good colors. An advantage of color matrix processing compared to lookup table-based DCP and ICC conversions is that it's purely linear, i.e. a dark and a bright color of the same hue and saturation is translated the same way. This makes it robust and may be the best choice if you will be exporting images for processing in an HDR application or other application when a predictable linear color response is important.

=== Auto-Matched Camera Profile ===
Uses RawTherapee's camera-specific DCP input profile that can provide more accurate colors than the standard matrix (and fall back to legacy ICC profiles if no DCP is available). Available for some cameras, these profiles are stored in the /dcpprofiles directory (or legacy /iccprofiles/input) and are automatically retrieved based on matching the exact make and model of the camera as it appears in the info section in the Editor to the filename, e.g. "Canon EOS 5D Mark III.dcp".

In other words, if "''Auto-matched camera profile''" is selected, RawTherapee will try to do the following, in this order:
# locate a DCP profile in /dcpprofiles
# if DCP is not found, locate an ICC profile in /iccprofiles
# if DCP and ICC are not found, revert to the camera standard color matrix.

If you want to contribute a camera profile, DCP is the preferred format.

Some of RawTherapee's profiles are single-illuminant (Daylight/D50), while others are double-illuminant (Daylight/D50 and Tungsten/StdA). Some include a tone curve, others do not. They strive for accurate colors (i.e. not a specific "look"). Most accurate colors will be achieved for white balances close to the calibration illuminants.

Camera profiles work in the normal range, from black up to clipping. If you enable highlight reconstruction, new data is added above the clipping level and if you bring it into visible space (by negative exposure for example), that range will not be naturally covered by the profile. However, RawTherapee will linearly extend the profile to cover this range too, colors there will get the same correction as the brightest colors of the same hue and saturation in the normal range.

=== Custom ===
Specify a custom DNG Profile (DCP) or ICC camera input profile stored on your computer.

DCP is a format specially designed for camera profiles and RawTherapee should support the most recent DNG standard (where DCP is defined), so you can for example use all those provided via Adobe's DNG converter.

ICC profiles on the other hand are more tricky. ICC profiles can be used for a multitude of purposes (printers, displays etc) and since they're not designed specifically for camera profiling, different vendors have chosen different approaches for their ICC profiles. In practice this means that the input image must be pre-processed in some specific way for the profile to work. The profile itself lacks information of how to do this pre-processing, which means that if you are using a third-party profile RawTherapee may not do the expected pre-processing; results will vary.

==== Third-party DCP support ====

A DNG Camera Profile, DCP, is the preferred camera profile format for RawTherapee. All elements of the 1.4 DNG specification is supported, with the exception of the black render tag (see below). A DCP can be a pure matrix profile, it can have a LUT (typically 2.5D) to improve the colorimetric accuracy, and then it can have an embedded curve and a separate "look table" on top. It may also add an exposure offset. All those elements can be toggled via checkboxes. However, although it is possible few third-party profiles have been designed to produced the intended color with anything else than all their elements enabled. For example, the tone curve itself changes color appearance so if you disable an embedded tone curve to get a linear profile you can't count on that the color is as intended.

The typical third party profile would come from Adobe Camera Raw / Lightroom, and RawTherapee supports them. Many of Adobe's profile lack tone curve, but in Adobe's world that does not mean that no tone curve should be applied but that Adobe's default curve should be applied. RawTherapee will therefore identify Adobe profiles (from the copyright string) and add the default curve to those (which you can toggle with the tone curve checkbox).

Adobe's DNG converter may add a "baseline exposure" to the DNG file. Adobe's DCP are designed to work with that baseline exposure and then produce a default output which is about the same brightness and contrast as the camera's own JPEGs. RawTherapee can honor this baseline exposure (NOT YET IMPLEMENTED), but this is of course only available when opening a DNG file converted by Adobe's DNG converter. If you instead open a native raw file there will be no baseline exposure and Adobe's DCP may then make a too bright or dark rendering. You can simply adjust with the exposure slider of course.

The DCP format also has a black render tag. This indicates if the raw converter should do "automatic" black subtraction or not. RawTherapee ignores this tag, you can do manual black subtraction with the black slider. As many of Adobe's profiles indicate auto black subtraction and Adobe Camera Raw / Lightroom does it, RawTherapee will in comparison in those cases render a bit lower contrast and brighter shadows.

==== Third-party ICC support ====

RawTherapee has specific support for ICC profiles bundled with Capture One and Nikon NX2, so those should work well. Older ICC profiles are not likely to work well though (typically the image becomes extremely dark with unsupported ICC profiles).

Some ICC profiles apply a tone-curve and desaturate bright highlights for a more "film-like" look. Those profiles may not work well together with [[Exposure#Highlight_Reconstruction|Highlight Reconstruction]]. If you see a radical change in contrast when you apply your ICC profile it has applied a tone-curve and then you should not use it together with [[Exposure#Highlight_Reconstruction|Highlight Reconstruction]].

Unlike DCP profiles, ICC profile processing may cause clipping of extremely saturated colors during conversion. In practice this is rarely if ever a problem, but still DCP should be considered the primary choice if available.

Note on using Capture One ICC profiles: RawTherapee applies the ICC before exposure adjustments, as the intention is that camera profiles should only be used to make the camera more accurate, not really to apply a look (you design the look using the tools instead). Phase One's ICC profiles contain a subjective look though, which means that they typically contain "hue twists", for example saturation in the shadows are increased a bit extra. This means that if you have an underexposed file and push it a few stops those hue twists have been applied on the dark image before exposure adjustment and will thus be in the wrong places after pushing, that is you don't get the same look as in Phase One's Capture One. Therefore it's recommended to have the right exposure out of the camera when using Phase One ICC profiles. You should also apply a suitable RGB "film curve" for example by using the curve tool, as those ICC profiles are designed to be used together with that.

We are aware that LUT ICCs should typically be applied after exposure (just as DCP Looktables are applied), and that would support for example Capture One profiles better. This may be fixed in a future version.

=== DCP Illuminant ===
Some of RawTherapee's profiles are single-illuminant (Daylight/D50), while others are double-illuminant (Daylight/D50 and Tungsten/StdA). If a dual-illuminant profile is loaded the "DCP Illuminant" setting will be enabled and you can choose which illuminant to use. The actual DCP standard (part of the DNG standard) does not provide this choice, but instead an interpolation between the two illuminants is calculated based on the chosen white balance (there will only be an interpolation if the white balance is in-between both illuminants, otherwise the closest is picked). This "interpolated" mode is the default setting of "DCP Illuminant" and for any normal use you do not need to change this.

You can however choose to base the color rendering on one of the specific illuminants. In some cases this might produce more pleasing color. It can also be interesting for diagnostic purposes to see how large (or small) a difference there is in color rendering between the illuminants, but, as said, for general use this setting should be untouched.

=== Use DCP's Tone Curve ===
Some DCPs contain a tone curve which may be used to add contrast and brightness to provide a film-like look. This is mainly used for profiles simulating camera maker settings. The tone curve checkbox will be disabled for profiles which do not contain a tone curve.

The curve mode used by the DCP tone curve is the same as the Exposure tool's "[[Exposure#Film-Like|film-like]]" mode, meaning you can reproduce the effect using the Exposure tool's tone curves in film-like mode. When contrast is applied with a film-like curve the appearance of the colors will change and overall saturation is increased, except for bright colors which instead are de-saturated. Some profiles which have curves embedded are pre-corrected for this color appearance change and will thus not provide the intended look without the curve applied. Most will however work well without the tone curve applied especially if you add a similar curve yourself using the Exposure tool's curves, but if you want to see exactly how the profile designer intended the colors to look you should enable the tone curve.

While the input color profile is applied at the first stages of the [[Toolchain_Pipeline|toolchain pipeline]], the DCP tone curve is applied later in the pipeline at some point after the Exposure tool.

=== Use DCP's base table ===
This enables the DCP "HueSatMap" lookup table which is used to add non-linear corrections on top of the basic matrix. This is an advanced user setting and unless you want only the pure matrix result should leave it on. It's grayed out if the loaded profile lacks a HueSatMap table.

=== Use DCP's look table ===
This enables the DCP "LookTable" lookup table which is intended to add a subjective look on top generally together with an embedded tone curve. That is if you disable the DCP curve and looktable you may get a neutral "colorimetric" profile, if the DCP was designed that way which is not always the case (if the DCP has both a look table and a base table it's likely that it is, but if it only has a look table it will probably not work well with it disabled). Disabling individual DCP elements are considered advanced user settings, normally you would leave this on.

=== Use DCP's baseline exposure offset ===
The DCP may indicate an exposure offset that corresponds to an offset of the exposure slider. The purpose of this is typically to make the brightness of the image match the brightness of the camera's own JPEGs, which can be useful if you're shooting with auto-exposure. Currently this offset is applied "under the surface" so you don't see it on the exposure slider.

Note that if you are using Adobe's proprietary profiles those are expecting that the DNG's "baseline exposure" tag is applied too (the profile's offset is added on top). Currently there is no support for the DNG tag so you need to find that out on your own (using exiftool for example) and then set that offset using the exposure slider if you want to get the exact same brightness as in Adobe Camera Raw.

=== Save Reference Image for Profiling ===
Clicking this button saves a linear TIFF image before the input profile is applied. This file can then be used for profiling, i.e. creating a new ICC camera profile. There are various commercial software out there to make ICC profiles, but you can also use the free and open-source Argyll. For DNG profiles there is DCamProf as an open-source alternative.

Cropping, resizing and transform (rotate) will be applied so you can use that to make the output more managable by the receiving software. Argyll is very picky for example and want no more than the test target visible in the image.

You can also choose if you want to export with white balance applied or not. For ICC profiles you should export with white balance applied, but if you intend to make a DNG Profile ColorMatrix (or a DCRAW style color matrix) you should export without.

== Working Profile ==
The default working profile is ProPhoto and should not be changed for normal use.

The working profile specifies the working color space, which is the color space used for internal calculations, for instance for calculating saturation, RGB brightness/contrast and tone curve adjustments, chrominance, etc.

When RawTherapee was based on integer math it was wise to not use working space larger than absolutely needed to get the best precision in the calculations. However, RawTherapee had switched to floating-point processing in 2011, and since version 4.0.12 the default working profile is ProPhoto, which has a very large gamut.

The choice of working profile has an influence on the effect of the curves in all modes except for perceptual - in that mode, changing the working profile will not alter the effect of the curve. If you have trouble fitting colors within the output gamut you can experiment with changing the working profile when using curves in any mode but perceptual.

Note that the working profile will only specify the red, green and blue primaries, gamma will not change as RawTherapee's processing pipeline is floating point with no gamma encoding (that is gamma = 1.0). Some tools (like curves and histograms) will still display with a gamma (usually sRGB gamma) which is hard-coded for the tool and stays the same regardless of working profile.

=== Adding Custom Working Profiles ===
RawTherapee 5.5 allows you to specify custom working profiles through a [https://en.wikipedia.org/wiki/JSON JSON] file. The file should be named <code>workingspaces.json</code> and it can reside either in the user's ICC profile folder as set in [[Preferences#Color_Management_Tab|Preferences]], or in RawTherapee's system-wide ICC profile folder:
* Windows: <code>%RT_DIR%\iccprofiles</code>
* Linux: <code>$RT_INSTALL_PREFIX/share/rawtherapee/iccprofiles</code>

The format is as follows:
<pre style="white-space: pre-wrap">
{"working_spaces": [
{
"name" : "ACES",
"file" : "/path/to/ACES.icc"
},
{
"name" : "ACEScg",
"matrix" : [0.7184354, 0.16578523, 0.09882643, 0.29728935, 0.66958117, 0.03571544, -0.00647622, 0.01469771, 0.66732561]
}
]}
</pre>

If "matrix" is present, "file" is ignored. If only "file" is present, the matrix is extracted from the ICC profile. For this, RawTherapee looks only at the R, G, and B matrix columns and the white point set in the profile. Bradford adaptation is used to convert the matrix to D50. Anything else in the profile (LUT, TRC, etc.) is ignored.

It is the user's responsibility to ensure that the profile is suitable to be used as a working space.

== Output Profile ==
Specify the output color profile; the saved image will be transformed into this color space and the profile will be embedded in the metadata. The effects the output profile has on the image cannot be seen in the preview.

RawTherapee lets you specify "input" (e.g. you're camera's profile), "display" and "output" (i.e. printer) device class profiles with an RGB color space, because RawTherapee saves only RGB images. Profiles listed in this combobox are those which come bundled with RawTherapee and those located in the folder set in Preferences > [[Preferences#Color_Management_Tab|Color Management]].

The soft-proofing feature is dedicated to simulating printer rendering. It lets you preview what your image will look like when printed, assuming you use a printer profile which correctly simulates your printer and paper combination. For best printout quality, after you have tweaked your photo using soft-proofing, you should select your printer profile as the output profile and save the image using it. This ensures that the image is encoded using your printer's color space directly from RawTherapee's internal high quality floating-point representation, instead of being saved to an 8-bit image in sRGB for example and then having to be subsequently converted to the printer profile, which would be quite lossy.

The main histogram, navigator and clipping indicators will use either the working or the output profile, depending on your setting in Preference > [[Preferences#General_Tab|General]].

RawTherapee comes bundled with a number of custom-made high quality output profiles:
; RT_sRGB
: Similar to sRGB
: Gamma close to sRGB: g=2.40, slope=12.92
; RT_sRGB_gBT709
: Similar to sRGB
: Gamma BT709: g=2.22, slope=4.5
; RT_sRGB_g10
: Similar to sRGB
: Linear gamma g=1.0, slope=0
; RT_Medium_gsRGB
: Similar to AdobeRGB1998
: Gamma close to sRGB: g=2.40, slope=12.92
; RT_Large_gsRGB
: Similar to ProPhoto
: Gamma close to sRGB g=2.40, slope=12.92 (close to "Melissa" used by Lightroom)
; RT_Large_gBT709
: Similar to ProPhoto
: Gamma BT709: g=2.22, slop=4.5
; RT_Large_g10
: Similar to ProPhoto
: Linear gamma g=1.0, slope=0
; Rec2020
: Wide gamut, larger than AdobeRGB but smaller than ProPhoto
: Gamma BT709: g=2.22, slope=4.5

The recommended output profile when you're saving to an 8-bit format and/or publishing to the web is RT_sRGB. If no profile is selected, none will be embedded, which means that "sRGB" is implied, though it is safer to embed RT_sRGB in terms of getting your image displayed properly in various applications.

RT_sRGB is a '''higher quality''' version of the standard sRGB profile, which surprisingly is inconsistent between implementations. RT_sRGB was custom-made for RawTherapee by Jacques Desmis and has 4096 LUT points, as opposed to the lower quality 1024 point sRGB profiles. Applications that aren't color managed and won't take advantage of RT_sRGB will fall back on sRGB.

Wide-gamut output profiles such as RT_Large_gsRGB are generally used if you export to a 16-bit or higher bit-depth format for further editing in another application. If you will be sending your image for printing, a wide-gamut output profile is also recommended, since some printers may have wide gamuts (at least in certain colors).

You should have a wide-gamut monitor if you want to work with wide-gamut profiles, otherwise you're flying in the dark.

Linux

2017-09-13T15:19:55Z

Agriggio:

This page details instructions for compiling RawTherapee on '''GNU/Linux''' systems. There are also instructions for compiling on [[Windows]] and [[OS X]].

When in doubt, [[IRC | join us on IRC]] and ask a human!

== Dependencies ==
To compile RawTherapee your system will need a set of tools. They are called dependencies, and here is a list of dependencies for both GTK2 and GTK3 versions of RawTherapee:

{| class="wikitable sortable"
|+ Build-time dependencies for RawTherapee 4 and 5.0.
! GTK+ !! Package !! Version !! Gentoo !! Debian/Ubuntu !! URL
|-
| GTK2, GTK3 || BZIP2 || bzip2>-1.0.4 || app-arch/bzip2 || libbz2-dev || http://www.bzip.org/
|-
| GTK2, GTK3 || EXIV2 || exiv2>=0.19 || media-gfx/exiv2 || libexiv2-dev || http://www.exiv2.org/
|-
| GTK2, GTK3 || EXPAT || expat>=2.1.0 || dev-libs/expat || libexpat-dev || http://expat.sourceforge.net/
|-
| GTK2, GTK3 || FFTW3 || fftw>=3.2.2 || sci-libs/fftw || fftw-dev || http://fftw.org/
|-
| GTK2, GTK3 || GCC || gcc>=4.9 || sys-devel/gcc || build-essential || http://gcc.gnu.org/
|-
| GTK2, GTK3 || GLIB2 || glib-2.0>=2.24 || dev-libs/glib || libglib2.0-dev || http://www.gtk.org/
|-
| GTK2, GTK3 || GLIBMM || glibmm-2.4>=2.24 || dev-cpp/glibmm || libglibmm-2.4-dev || http://www.gtkmm.org
|-
| GTK2 || GTK+ || gtk+-2.0>=2.24.18 || x11-libs/gtk+ || libgtk2.0-dev || http://www.gtk.org/
|-
| GTK3 || GTK+ || gtk+-3.16 || x11-libs/gtk+ || libgtk-3-dev || http://www.gtk.org/
|-
| GTK2 || GTK2-Engines || gtk-engines-2.20.2 || x11-themes/gtk-engines || gtk2-engines || http://www.gtk.org/
|-
| GTK2 || GTKMM || gtkmm-2.4>=2.22 || dev-cpp/gtkmm || libgtkmm-2.4-dev || http://www.gtkmm.org
|-
| GTK3 || GTKMM || gtkmm-3.16 || dev-cpp/gtkmm || libgtkmm-3.0-dev || http://www.gtkmm.org
|-
| GTK2, GTK3 || JPEG || libjpeg>=6b || media-libs/jpeg || libjpeg-dev || http://libjpeg-turbo.virtualgl.org/ http://jpegclub.org/ http://www.ijg.org/
|-
| GTK2, GTK3 || LCMS2 || lcms>=2.6 || media-libs/lcms || liblcms2-dev || http://www.littlecms.com/
|-
| GTK3 || LENSFUN || lensfun>=0.2 || ?? || liblensfun-dev || http://lensfun.sourceforge.net/
|-
| GTK2, GTK3 || LIBCANBERRA || libcanberra>=0.29 || media-libs/libcanberra || libcanberra-gtk3-dev || http://0pointer.de/lennart/projects/libcanberra/ (Linux only)
|-
| GTK2, GTK3 || LIBIPTCDATA || libiptcdata>=1.0.2 || media-libs/libiptcdata || libiptcdata-dev || http://libiptcdata.sourceforge.net
|-
| GTK2, GTK3 || PNG || libpng>=1.2.44 || media-libs/libpng || libpng-dev || http://www.libpng.org/
|-
| GTK2, GTK3 || SIGC || sigc++-2.0 || dev-libs/libsigc++ || libsigc++-2.0-dev || http://libsigc.sourceforge.net/
|-
| GTK2, GTK3 || TIFF || libtiff>=3.9.4 || media-libs/tiff || libtiff-dev || http://www.remotesensing.org/libtiff/
|-
| GTK2, GTK3 || ZLIB || zlib>=1.2.3 || sys-libs/zlib || zlib1g-dev || http://www.zlib.net/
|}

To compile the outdated RawTherapee 3 you will need these:

{| class="wikitable"
|+ Build-time dependencies for RawTherapee 3
! Package !! Version !! Gentoo !! Debian/Ubuntu !! URL
|-
| LCMS1 || lcms<=1.99 || media-libs/lcms || liblcms1-dev || http://www.littlecms.com/
|}

In order to install all these dependencies, you will need to open a console and paste the code from the appropriate section into the console. Note that these code snippets include the GTK3 dependencies if available, so if you want to compile the legacy "gtk2" branch which uses GTK2 then replace the GTK3 dependencies with GTK2 ones as described in the list above.

=== Arch ===
The latest Arch supports GTK3, use the <code>dev</code> branch (or checkout a "gtk3" release tag). The dependencies below are only for GTK3.
<pre style="white-space: pre-wrap">sudo pacman -S bzip2 exiv2 expat fftw glib2 glibmm gtk3 gtkmm3 lcms2 lensfun libcanberra libiptcdata libjpeg-turbo libpng libsigc++ libtiff zlib</pre>

=== CentOS 7.1 ===
CentOS 7.1 does not support a recent enough version of GTK3, so you can only compile the <code>gtk2</code> branch.
As CentOS 7.1 does not seem to have the Clearlooks GTK2 theme engine, you will either need to install some other GTK2 theme engine, or after installing RawTherapee go to "Preferences > General > Default Theme" and enable "Use system theme".
<pre style="white-space: pre-wrap">sudo yum install bzip2-devel cmake curl exiv2-devel expat-devel fftw-devel gcc-c++ git glibmm24-devel gtk2-devel gtkmm24-devel lcms2-devel libjpeg-turbo-devel libcanberra-devel libiptcdata-devel libpng-devel libtiff-devel sigc++20-devel zlib-devel</pre>

=== Fedora ===
Fedora supports GTK3 from version 22, use the <code>dev</code> branch (or checkout a "gtk3" release tag). The dependencies below are only for GTK3.
If you are using Fedora version 21 or older, use the legacy <code>gtk2</code> branch.
<pre style="white-space: pre-wrap">sudo dnf install bzip2-devel cmake exiv2-devel expat-devel fftw-devel gcc-c++ glib2-devel glibmm24-devel gtk3-devel gtkmm30-devel lcms2-devel lensfun-devel libcanberra-devel libiptcdata-devel libjpeg-turbo-devel libpng-devel libsigc++20-devel libtiff-devel zlib-devel</pre>

=== Gentoo ===
Gentoo supports GTK3, use the <code>dev</code> branch (or checkout a "gtk3" release tag). The dependencies below are only for GTK3.
<pre style="white-space: pre-wrap">sudo emerge -uva app-arch/bzip2 dev-cpp/gtkmm:3.0 dev-libs/expat media-gfx/exiv2 media-libs/lcms media-libs/libcanberra media-libs/libiptcdata media-libs/libjpeg-turbo media-libs/libpng media-libs/tiff net-misc/curl sci-libs/fftw sys-libs/zlib x11-libs/gtk+:3</pre>

=== openSUSE ===
openSUSE 42.2 and Tumbleweed support GTK3, use the <code>dev</code> branch (or checkout a "gtk3" release tag). The dependencies below are only for GTK3.
Note: openSUSE 42.1 supports GTK+ 3.16.7 but compilation fails as the sigc++-2.0>=2.4 requirement is not met.
If you are using openSUSE version 42.1 or older, use the legacy <code>gtk2</code> branch.
<pre style="white-space: pre-wrap">sudo zypper in cmake fftw3-devel gcc-c++ glib2-devel glibmm2-devel gtk3-devel gtkmm3-devel libbz2-devel libcanberra-devel libexpat-devel libiptcdata-devel libjpeg-devel liblcms2-devel libpng-devel libsigc++2-devel libtiff-devel zlib-devel</pre>

=== Sabayon ===
Sabayon supports GTK3, use the <code>dev</code> branch (or checkout a "gtk3" release tag). The dependencies below are only for GTK3.
<pre style="white-space: pre-wrap">sudo equo install app-arch/bzip2 dev-cpp/gtkmm:3.0 dev-libs/expat dev-util/cmake media-gfx/exiv2 media-libs/lcms media-libs/libcanberra media-libs/libiptcdata media-libs/libjpeg-turbo media-libs/libpng media-libs/tiff net-misc/curl sci-libs/fftw sys-libs/zlib x11-libs/gtk+:3</pre>

=== Ubuntu ===
Ubuntu as of version 15.10 (Wily Werewolf) supports GTK3, use the <code>dev</code> branch (or checkout a "gtk3" release tag). The dependencies below are only for GTK3.
Older versions of Ubuntu either do not support GTK3 at all, or the version of GTK3 they ship is not recent enough (RawTherapee GTK3 support requires GTK3 version 3.16 or newer), meaning you must use the legacy <code>gtk2</code> branch which uses GTK2.

==== Ubuntu 16.10 ====
Use the <code>dev</code> branch (or checkout a "gtk3" release tag). The dependencies below are only for GTK3.
<pre style="white-space: pre-wrap">sudo apt update
sudo apt install build-essential cmake curl git libcanberra-gtk3-dev libexiv2-dev libexpat-dev libfftw3-dev libglibmm-2.4-dev libgtk-3-dev libgtkmm-3.0-dev libiptcdata0-dev libjpeg-dev liblcms2-dev liblensfun-dev libpng-dev libsigc++-2.0-dev libtiff5-dev zlib1g-dev</pre>

==== Ubuntu 16.04 LTS and 15.10 ====
Use the <code>dev</code> branch (or checkout a "gtk3" release tag). The dependencies below are only for GTK3.
<pre style="white-space: pre-wrap">sudo apt-get update
sudo apt-get install build-essential cmake curl git libbz2-dev libcanberra-gtk3-dev libexiv2-dev libexpat-dev libfftw3-dev libglibmm-2.4-dev libgtk-3-dev libgtkmm-3.0-dev libiptcdata0-dev libjpeg8-dev liblcms2-dev liblensfun-dev libpng12-dev libsigc++-2.0-dev libtiff5-dev zlib1g-dev</pre>

==== Ubuntu 15.04, 14.10, 14.04 LTS ====
Use the legacy <code>gtk2</code> branch. The dependencies below are only for the <code>gtk2</code> branch.
<pre style="white-space: pre-wrap">sudo apt-get update
sudo apt-get install build-essential cmake curl git libbz2-dev libcanberra-gtk-dev libexiv2-dev libexpat-dev libfftw3-dev libglibmm-2.4-dev libgtk2.0-dev libgtkmm-2.4-dev libiptcdata0-dev libjpeg8-dev liblcms2-dev libpng12-dev libsigc++-2.0-dev libtiff5-dev zlib1g-dev</pre>

RawTherapee requires GCC version 4.9 or higher. Ubuntu 14.04 LTS ships with GCC version 4.8.2 which is too old - to get 4.9, follow these steps: http://askubuntu.com/questions/466651/how-do-i-use-the-latest-gcc-on-ubuntu-14-04

==== Ubuntu 13.10, 13.04, 12.10, 12.04 LTS, 11.10 ====
These versions of Ubuntu are badly outdated. The code below used to work but it may stop working at any moment. Upgrade your operating system.

As these versions of Ubuntu only support GCC-4.8.1 and older, the latest commit you will be able to compile is [https://github.com/Beep6581/RawTherapee/commit/b343b9a7 commit b343b9a7] from 2015-12-29 - newer versions will not compile.
<pre style="white-space: pre-wrap">sudo apt-get update
sudo apt-get install build-essential cmake curl git libbz2-dev libcanberra-gtk-dev libexiv2-dev libexpat-dev libfftw3-dev libglibmm-2.4-dev libgtk2.0-dev libgtkmm-2.4-dev libiptcdata0-dev libjpeg8-dev liblcms2-dev libpng12-dev libsigc++-2.0-dev libtiff5-dev zlib1g-dev</pre>

==== Ubuntu 10.10 and 11.04 ====
These versions of Ubuntu are badly outdated. The code below used to work but it may stop working at any moment. Upgrade your operating system.

<pre style="white-space: pre-wrap">sudo apt-add-repository ppa:dasprid/rawtherapee
sudo apt-get update
sudo apt-get install cmake curl git libbz2-dev libcanberra-gtk-dev libexiv2-dev libexpat-dev libglibmm-2.4-dev libgtk2.0-dev libgtkmm-2.4-dev libiptcdata0-dev libjpeg62 liblcms2-dev libnm-glib2 libpng12-dev libsigc++-2.0-dev libtiff4-dev zlib1g-dev</pre>


== Compiling: The Manual Way ==
This section describes compiling RawTherapee manually.

=== Clone the source ===
First, you need to clone RawTherapee's source code repository. Bring up your console and run this:

<pre style="white-space: pre-wrap">git clone https://github.com/Beep6581/RawTherapee ~/repo-rt
cd ~/repo-rt</pre>

=== Choose a branch ===
* Features are developed on their own feature branches.
* Development happens on the <code>dev</code> branch. Feature branches are merged into the <code>dev</code> branch when they're ready. The <code>dev</code> branch is unstable.
* Releases are tagged on the <code>releases</code> branch.

Checkout the latest tag if you want the most stable code. To see all available tags, type:
<pre style="white-space: pre-wrap">git tag</pre>

Checkout the <code>dev</code> branch or some other feature branch if you want to test the latest bleeding-edge code. To see all available branches, type:
<pre style="white-space: pre-wrap">git branch -a</pre>

Checking out is done via the "git checkout" command. To checkout a tag or a branch, type:
<pre style="white-space: pre-wrap">git checkout <tag or branch></pre>

RawTherapee uses GTK+ for the user interface and requires GTK+ version 3.16 or newer. If your system does not support version 3.16 or newer then you must checkout the <code>5.0-r1-gtk2</code> tag. Our GTK2 support has officially ended on 2 February 2017 - update your system.

Note: Compiling old versions of RawTherapee will fail on a modern system, as you will be missing the old dependencies.

=== Compile RawTherapee ===
Now you will make an out-of-source compilation of RawTherapee, it will be built into the ~/repo-rt/build/release folder, and then you will move this folder to your home directory and rename it to "rt", so make sure there is no ~/rt folder already!

There are a few compilation settings you need to be aware of, you will pass these to CMake using the -D option as described below:

; BUILD_TYPE
: You must specify the <code>BUILD_TYPE</code> when building RawTherapee. You can set the <code>BUILD_TYPE</code> value to "<code>debug</code>", "<code>relwithdebinfo</code>" or "<code>release</code>". The "debug" and "relwithdebinfo" builds will let you [[How_to_write_useful_bug_reports | get a useful stack-backtrace]] if RawTherapee crashes while running through GDB which you can then submit to us so we can find the problem and fix it. The "debug" build is the slowest but generates the most detailed information. The "relwithdebinfo" build is almost as fast as a "release" build and generates often sufficient information, though not as detiled as a "debug" build. The "release" build will not provide any useful information when it crashes, but does contain many speed optimizations resulting in a program that works many times faster than the "debug" version would. For normal use, make a "release" or "relwithdebinfo" build. If you find a reproducible bug, then make a "debug" build and send us a stack-backtrace (or fix it yourself and send us the patch!). Alternatively use a "relwithdebinfo" build, and hope that it's detailed enough.
:: To make a "release" type build, write: <code>-DCMAKE_BUILD_TYPE="release"</code>
:: Replace "release" by "debug" or "relwithdebinfo" as needed.

; USE_OLD_CXX_ABI
: When compiling a program, one must use the same conventions as those used by the libraries which that program relies upon, otherwise compilation (linking) will fail. Generally one does not need to concern oneself with this, but we are now at a time when GCC4 is being phased out by GCC5, each by default uses a convention incompatible with the other, and so this issue is relevant. If the libraries on your system have been compiled using GCC5, they probably use a standard called C++11. This means that your RawTherapee build must use the same standard, which is the case by default. However if despite using GCC5 your libraries were built using the older C++03 standard, then RawTherapee must be set to use the same, and this is when you would set "USE_OLD_CXX_ABI" to "ON":
:: To enable USE_OLD_CXX_ABI, write: <code>-DUSE_OLD_CXX_ABI="ON"</code>

; CACHE_NAME_SUFFIX
: The CACHE_NAME_SUFFIX options dictates the suffix of the cache and config folder names the compiled RawTherapee build will use.
: See the [[File Paths]] article for a full explanation, or just use "5-dev".

; PROC_TARGET_NUMBER
: The PROC_TARGET_NUMBER option sets which CPU type to optimize for. "2" is a safe choice because it means "native", so the optimizations will be automatically detected for your CPU.
: For more info, see the file "ProcessorTargets.cmake" in the cloned repository.
:: To make a build using "native" optimizations, write: <code>-DPROC_TARGET_NUMBER="2"</code>

Finally, you need to find out how many threads your CPU supports. This will make compilation faster but it will have no effect on the speed of running RawTherapee.
; Threads
: To find out how many threads your CPU supports, run:
: <code>grep -c processor /proc/cpuinfo</code>
: Then replace the number in "-j8" below with this number.

Now you are ready to compile:
<pre style="white-space: pre-wrap">cd ~/repo-rt
rm -rf build
mkdir build && cd build
cmake -DCMAKE_BUILD_TYPE="release" \
-DPROC_TARGET_NUMBER="2" \
-DBUILD_BUNDLE="ON" \
-DCACHE_NAME_SUFFIX="5-dev" \
-DWITH_LTO="OFF" \
..
make -j4 install
mv release ~/rt</pre>

=== Run RawTherapee ===
To run RawTherapee:
<pre style="white-space: pre-wrap">~/rt/rawtherapee</pre>

The source code repository is in <code>~/repo-rt</code> and the compiled program is in <code>~/rt</code>

You can safely delete <code>~/repo-rt</code> if you so wish. The compiled program will still work, but then you will have to redo all the above steps if you want to update. Rather, leave the repository intact so that you can do the next step in a week or a month's time.

=== Update RawTherapee ===
Every time you want to update your RawTherapee to the latest code available, just do the following:
<pre style="white-space: pre-wrap">cd ~/repo-rt
git pull</pre>

Then repeat the [[Linux#Compile RawTherapee | Compile RawTherapee]] step above.

Dynamic processing profiles

2017-03-10T08:48:59Z

Agriggio:

Sometimes a single, "static" default processing profile is not enough to cover
all use cases. For example, the amount of noise reduction to apply varies
according to the Camera and ISO setting used. Another example is the kind and
amount of lens corrections needed, which is obviously dependent on the lens
used.

In order to handle such cases, RawTherapee provides a feature that allows to
create a default processing profile "dynamically", based on the metadata of
the image being processed (such as camera and lens name, shutter speed, ISO
value, and so on).

This is done by defining a set of "Dynamic profile rules". Each rule has a
[[Creating_processing_profiles_for_general_use|(partial) processing profile]] attached to it, plus some conditions on the image
metadata that define whether the rule is applicable. When a picture is edited for the
first time, the list of rules is scanned, and all the profiles that match are
combined (in the order given, so later rules can override earlier ones) to
build the initial processing profile.

In order to activate the functionality, the [[Preferences#Default_Processing_Profile|default processing profile]] must be set to "(Dynamic)".
Rules are defined in the [[Preferences#Dynamic_Profile_Rules_Tab|Dynamic Profile Rules]] section of the preferences window.

Dynamic profile rules work on the following image metadata:

; Camera
: the camera name (including brand) as shown in the image info overlay of the [[The_Image_Editor_Tab|Image Editor]]. If active, by default this entry will cause the rule to apply only to pictures taken with the exact camera specified here (except that the capitalization of the string is ignored). However, if the entry starts with the <code>re:</code> prefix, then the rest of the string will be interpreted as a [https://en.wikipedia.org/wiki/Regular_expression regular expression] to use for the matching. For example, a rule with the Camera value set to <code>re:SONY ILCE-[56].00</code> will be applied to all Sony Alpha a5xxx and a6xxx cameras.

; Lens
: the full lens name. As above, a regular expression can be used by starting with the <code>re:</code> prefix

; ISO
: the range of ISO values

; Aperture
: the range of apertures of the lens (measured in f/ stops)

; Focal length
: the range of focal lengths used (in mm)

; Shutter
: the range of shutter speeds in seconds (for example, enter 0.03 for a speed of 1/30")

; Exposure compensation
: the range of exposure compensations.

A screenshot is shown below.

[[File:dynamic-profile-rules-screenshot.png]]

Preferences

2017-03-10T07:19:31Z

Agriggio:

You can access the Preferences window by clicking on the Preferences button [[image:Gtk-preferences.png]] which is either in the bottom-left corner of the RawTherapee window, or the top-right one, depending on your [[The_Image_Editor_Tab#Editor_Tab_Modes | Editor tab mode layout]].

Note: When you start RawTherapee not just by clicking its shortcut but by passing an image's filename as an argument so that the image is opened directly, RawTherapee will run in "[[The_Image_Editor_Tab#Editor_Tab_Modes | no-File-Browser mode]]". The Preferences button is missing when RawTherapee is in that mode. Getting rid of that mode is on the TODO list, see [https://github.com/Beep6581/RawTherapee/issues/2238 issue 2238]. To access Preferences, be sure to start RawTherapee normally without passing any filename arguments.

== About ==
Shows information about the original author of RawTherapee and the current version, details of the build, names of developers and other contributors and the licence under which RawTherapee is published: [https://en.wikipedia.org/wiki/GPLv3 GPLv3]

== General Tab ==
=== Layout ===
RawTherapee lets you use the following modes:
* Single Editor Tab Mode
* Single Editor Tab Mode, Vertical Tabs
* Multiple Editor Tabs Mode
* Multiple Editor Tabs Mode (if available on second monitor)

Remember that if you use multiple "Editor" tabs, each one takes a substantial amount of RAM. Only use multiple Editor tabs if you have quite a lot of RAM (exactly how much depends on what resolution your images are, which tools you use, how many other programs you run in the background, etc.).

A restart is required for these options to take effect.

=== Default Language ===
Select the language for the GUI out of a list of thirty languages. English (US) is the default ('mother') language, translations are based on that one. On Win Vista/7 64bit you can have the language automatically read from the operation system.

Again, a restart is required to change the language of the GUI.

=== Default Theme ===
Choose between several themes for the GUI, from light to dark. The effects are visible after a few seconds, so no need to restart here. Checking 'Use System Theme' might change the appearance of RawTherapee, although this depends on the platform and the window manager in use. Just see if it works for you.

"Crop mask color/transparency" is the color of the area outside of a crop. By clicking on the colored button, a new window appears where you can also set transparency. If set to 75, the cropped area is still somewhat visible. Useful to move the crop around and to find the best composition (hold the '''Shift''' key and move the crop with the mouse).

Choose the font of your liking here. With smaller fonts more tools can be displayed on the screen. You can also enable "Slim interface" to fit some more tools into your screen space.

=== Clipping Indication ===
When clipped highlight [[image:Warnhl.png]]/[[image:Warnsh.png]] shadow indication is enabled in the preview, areas which are clipped in at least one channel are painted a solid color. The shade of this color depends on how strong the clipping is. The threshold values determine when clipping is considered to begin. The clipping indicators are calculated on the final image in the output color space as selected for that image in the [[Color_Management#Output_Profile | Color Management]] panel.

=== Pan Rate Amplification ===
Imagine a high resolution image is opened, and you are zoomed to 100%. In order to move the image around (it's called "panning") you would have to make multiple mouse movements (or have a very large mouse pad!). RawTherapee saves you from this by using a "pan rate amplification" - when set to 5, RawTherapee multiplies by 5 every pixel you pan by. If in one comfortable mouse movement you'd normally move the cursor 500 pixels, with this option set to 5 you will have panned 2500 pixels.

The effect is most visible when you are zoomed in, and least visible when zoomed out.

=== External Editor ===
You can have RawTherapee send the processed image directly to an external program, e.g. an image viewer, an image editor or a script. You do this using the [[File:Image-editor.png]] "[[Edit Current Image in External Editor]]" button in the Editor tab under the main preview, see the [[Saving]] article. It is here in Preferences where you can customize which program is to be sent this processed image when you click the button.

* Windows
: If you use Windows, RawTherapee allows you to set up the path to GIMP, Photoshop, and to one other external program ("Custom command line").
: The recommended way of setting the GIMP option is by pointing RawTherapee to the folder which contains the <code>bin</code> folder which contains the GIMP executable, <code>gimp-2.*.exe</code>. If you use an unofficial version of GIMP where the executable does not have that name, you may need to use the command line option instead.
: For the Photoshop option, point RawTherapee to the folder which contains the Photoshop executable, <code>Photoshop.exe</code>
: For the command line option, simply write the full path including the executable. Don't worry about spaces or about escaping backslashes. Environment variables such as <code>%ProgramFiles%</code> are not supported.
: Examples:
:: <code>C:\Program Files\Gimp-2.9\gimp-2.9.exe</code>
:: <code>C:\Program Files\Digital Light & Color\Picture Window Pro 6.0\pw60.exe</code>

* Linux
: If you use Linux, the GIMP option is hard-coded to look for the GIMP executable <code>gimp</code> anywhere.
: For the command line option, simply write the full path including the executable. You may need to enclose the whole line in double quotation marks if you need to pass arguments, see the example. Environment variables such as <code>~</code> or <code>$HOME</code> are not supported.
: Examples:
:: <code>"/usr/bin/geeqie --remote"</code>
;: The above command opens the image in a single instance of Geeqie. Note that you need to enclose it in double quotation marks because you're passing the "--remote" option.
:: <code>/home/bob/programs/luminance hdr/luminance-hdr</code>
;: The above command opens the image in Luminance HDR. No arguments or options passed so no quotation marks needed.

* macOS
: If you use macOS, the GIMP option is hard-coded to <code>open -a GIMP</code> and the Photoshop option is hard-coded to <code>open -a Photoshop</code>
: For the command line option, write <code>open -a "External Program"</code> where <code>"External Program"</code> is the name of the program you want to be used to open the image. Surround the name of the program in quotation marks if it contains one or more space characters.
: Examples:
:: <code>open -a "Adobe Photoshop CS6"</code>
;: The above command opens the image in Adobe Photoshop CS6. Note that you need to enclose it in quotation marks because it contains space characters.
:: <code>open -a "Affinity Photo Trial"</code>
;: The command above opens the trial version of Affinity Photo. It too needed to be enclosed in quotation marks due to the spaces in the name.
:: <code>open -a "/My stuff/Programs/Pixel Mixer"</code>
;: The command above opens a program called "Pixel Mixer" in the "My stuff" folder. We have reports that it is not necessary to write the full path to the program even if it does not reside in the standard <code>/Applications/</code> folder.

== Image Processing Tab ==
=== Default Processing Profile ===
Specify which profile RawTherapee is to use when opening a raw photo and when opening a non-raw photo. When you have made your own default profile, you can tell RawTherapee to always use that one. To do that, to have it show up in the list, you must save it to RawTherapee's "''config''" folder. You can find out where it is on the [[File_paths#Processing_Profiles | file paths]] page.

The default processing profile for non-raw files like JPEG or TIFF is best set to "Neutral". The "Neutral" profile just loads the photo as it is, without applying anything like [[Exposure#Auto_Levels | Auto Levels]] or [[Sharpening]].

The special entry "(Dynamic)" activates the support for [[Dynamic_processing_profiles | Dynamic Processing Profiles]].

=== Custom Processing Profile Builder ===
Executable (or script) file called when a new initial processing profile should be generated for an image. The path of the communication file (*.ini style, a.k.a. "Keyfile") is added as a command line parameter. It contains various parameters required for the executable or script to allow a rules-based processing profile generation.

This feature is very powerful; for example it allows you to set lens correction parameters or noise reduction based on image properties. It is called just once on the first edit of the picture, or called manually from the context menu when right-clicking on a thumbnail in the [[The File Browser Tab|File Browser]] or [[The_Image_Editor_Tab#The_Filmstrip | Filmstrip]]

<b>Note:</b> You are responsible for using double quotes where necessary if you're using paths containing spaces.

=== Processing Profile Handling ===
"Save processing profiles next to the input file": When checked, RawTherapee writes a PP3 file with all the edits you made to your photo next to the input (raw) file. This represents your work (e.g. sharpening settings used) and can be reloaded later.

"Save processing profiles to the cache": Instead of creating a PP3 file next to the raw, this option - when checked - writes the PP3 to the cache. When you check the last option only, chances are that you lose your work (the edits) when installing RawTherapee on a new PC for instance.

It's usually a good idea to only save the processing parameters next to the input file, since you can e.g. back them up along with the your raws.

=== Dark-Frame ===
Specify the directory on your hard disk for searching for the dark frame shots for long exposure noise subtraction. File with coordinates listing of the bad pixels must be placed in the same directory for auto correction.

=== Flat-Field ===
Specify the directory on your hard disk for searching for the flat field reference images.

=== Metadata ===
The "Copy Exif/IPTC/XMP unchanged to output file" option changes RawTherapee's metadata handling behavior.
* Enabled, it will copy Exif (including Makernotes), XMP and IPTC information from the input image into the output image unchanged. You will want to keep it enabled if you tag, rate, describe or caption your images in other software so that the image saved by RawTherapee will contain this information unchanged. However if you add, delete or change Exif or IPTC metadata using RawTherapee's "Meta" tab, then with this option enabled these changes will be lost - they will not be present in the saved image!
* Disabled, RawTherapee will save only that metadata in the output file which is enabled in the "Meta" tab - by default all metadata is enabled. If you add, delete or change Exif (including Makernotes), IPTC or XMP metadata using RawTherapee's "Meta" tab, then disable this option.

== Dynamic Profile Rules Tab ==
Here you can define your custom rules for creating [[Dynamic_processing_profiles | Dynamic Processing Profiles]].

== File Browser Tab ==
=== Image Directory at Startup ===
At the top you can define the image directory to use at startup. It could be the RawTherapee installation directory, the last-visited directory, the home directory, or a custom directory.

=== File Browser / Thumbnail Options ===
These options determine which information is visible in the thumbnails and how it should be displayed.

=== Context Menu Options ===
Adjust the grouping of the right-click context menu in the [[The File Browser Tab|File Browser]] (and [[The_Image_Editor_Tab#The_Filmstrip | Filmstrip]]).

=== Parsed Extensions ===
Choose which files are recognized as images and displayes in the [[The File Browser Tab|File Browser]]. All supported extensions are set by default. They can be deactivated by unchecking the relevant box. If a desired extension is missing you can easily add it by using the plus button.

=== Cache Options ===
These options influence the speed of thumbnail loading and generation. These options are quite self-explanatory.

== Color Management Tab ==
The "Color Management" tab lets you define the directory where ICC profiles can be found.

=== Monitor ===

You should define here the ICC profile of your monitor when you've done a calibration. If you don't do it, the image will be displayed with wrong colors.

The option "Use operating system's main monitor color profile" is currently only supported on Windows, and it support only one monitor. If you have multiple monitors connected, it will always take the main monitor's profile (the one with the task bar).

On macOS all displayed colors will be in [https://en.wikipedia.org/wiki/SRGB sRGB space], and then, if necessary, converted by the native macOS color pipeline to match the screen calibration, if any. This means that you cannot choose a monitor color profile on macOS. Colors will be displayed correctly, even over multiple screens, but if you have a wide-gamut screen RawTherapee's displayed colors will still be limited to sRGB. This will however not affect output, i.e. you can still produce images with colors outside the sRGB space.

The Linux version does not support monitor profile auto-detection, but as long as you load the same ICC profile as used in calibration the colors will be managed and you will get full use of your wide gamut monitor, if you have one. If you have more than one monitor with different profiles you will have to choose a primary one for correct color and have the RawTherapee window there.

See below for Rendering Intent an Black Point Compensation.

=== Printer (Soft-Proofing)===

You can select here the color profile of your own printer or your print service in order to simulate the rendering of the printed image.

See below for Black Point Compensation.

=== Rendering Intent ===

The "[https://en.wikipedia.org/wiki/Rendering_intent#Rendering_intent Rendering intent]" drop-down lets you choose how the ICC profiles are used for translation between gamuts or color spaces.
; Perceptual
: If the color gamut of your image is higher than that of your destination device (monitor or printer) then it is compressed a bit to fit the gamut of your device as far as possible. This might result in an image with reduced saturation, but the hue is still kept. It might look a bit dull. But this is not really that much visible as the color relations stay the same. This method is activated by default (recommended).

; Relative Colorimetric
: The colors existing in the color gamuts of both your image and your device are kept and displayed 100% perfect. If the color does not exist within the color gamut of your device the nearest possible value is taken. This might lead to some banding effects, especially visible in blue sky. The white point will be corrected.

; Saturation
:Very similar to Perceptual, but here it is tried to keep the saturation and change the hue instead. This is very useful for e.g. screenshots or similar. It could also be used when you do not care about a possible color shift as long the image does not look dull.

; Absolute Colorimetric
: Similar to relative colorimetric. It tries to reproduce the exact colors recorded in the original scene. The white point will not be corrected. It is normally used, when the gamuts of your image and your device are nearly the same. Used when exact reproduction of specific colors is needed, e.g. fabric or logo colors.

===Black Point Compensation===

When enabled, the Black Point level of the input image is moved to the Black Point level of the output image in a color transformation (e.g. from working profile to display profile). It means that the luminance channel alone is compressed or expanded to match the output capabilities. This feature will keep details in the shadows (avoid flat dark areas) at the expense of less color correctness.

== Batch Processing Tab ==
Batch processing is the capability of editing several images at the same time in the [[The File Browser Tab|File Browser]] tab. That is why there is a tool panel in the "File Browser". It looks the same as the tool panel in the [[The_Image_Editor_Tab|Image Editor]] tab, but since it lets you tweak many files at once we refer to it as the "batch tool panel". The checkboxes here have three states:<br>
<code>[ ]</code> Disabled<br>
<code>[✓]</code> Enabled<br>
<code>[-]</code> Values differ across selected images.<br>

Batch editing is done by selecting more than one image by using the '''Shift''' or '''Control''' key in the [[The_File_Browser_Tab|File Browser]], then you can edit those images with the tools in the batch tool panel on the right. The way the sliders' values are used to modify the image depends on the options set in this "Batch Processing" tab.

When you select a single image, the sliders get the values of the processing parameters of that specific image. These can be the values of the default profile or the values from your last edit session of this photo. If your image is currently being edited in an [[The_Image_Editor_Tab | Image Editor]] tab, the editor's values will be reflected in real time in the batch tool panel, and vice versa, so take care what you're doing.

When selecting more than one image in the "File Browser", the action of the tool sliders depends on that tool's batch processing mode. Tools which are not listed function as if they were in the "Set" mode.

; The "Add" Mode
: This mode may also be understood as "relative". Modifying sliders which are set to the "Add" mode will result in the value of the modification being added to the existing value. For example, if you select two images by holding the '''Ctrl''' modifier key, one image which has an [[Exposure#Exposure_Compensation Exposure Compensation]] of -0.5 EV and the other which has +1.0 EV, moving the "Exposure Compensation" slider up to +0.3 will result in setting a value of -0.2 EV for the first image and +1.3 EV for the second one.

: Using the "Reset" button will move the slider to its default (zero) position and will then bring back the initial value of that slider for each selected image.

; The "Set" Mode
: This mode may also be understood as "absolute". Modifying sliders which are set to the "Set" mode will result in the value of the modification being set, irrelevant of what the existing value was. If we use the same example as before, moving the slider up to +0.3 EV will result in setting a value of +0.3 EV for both images (one value for all images).

: Using the 'Reset' button will move the slider to its default position (different for each slider), and will then reset this parameter for each image.

; Overwrite Existing Output Files
: The option "Overwrite existing output files" sets RawTherapee to overwrite existing images. When disabled, existing images will not be overwritten; instead, an index number is appended to the image being saved.
: e.g. If "output.jpg" exists and the option is not checked, the new image will be saved as "output-1.jpg".

== Performance Tab ==
The "Performance" tab is only for people who know what they're doing. It lets you poke under the hood and tweak the parameters of some tools. These parameters take part in the balance between speed and stability.

=== Maximum Number of Threads for Noise Reduction ===
The [[Noise Reduction]] algorithm in RawTherapee is very powerful. It is also quite CPU and memory intensive. People with weak hardware who experience crashes caused by running out of RAM may find that tweaking this parameter prevents those crashes, at the cost of longer processing time.

[[Noise Reduction]] has a baseline requirement of 128MB of RAM for a 10 megapixel raw photo, or 512MB of RAM for a 40 megapixel one, and additionally 128MB of RAM per thread. The more threads run in parallel, the quicker the computation, but higher the memory requirement.

Most modern CPUs run two threads per physical core. Find out what CPU you have and how many cores it has, multiply that by two, and you get the maximum number of threads it would make sense to run simultaneously. Let's call this number ''T<sub>max</sub>''. You would not benefit from running more threads than this - in fact you would likely suffer a small speed penalty.

Setting this parameter to "0" will let your CPU figure out what ''T<sub>max</sub>'' is, and use that. If you experience crashes due to insufficient RAM, then you can calculate ''T<sub>max</sub>'' yourself and use a number lower than that.

== Sounds Tab ==
The "Sounds" tab lets you set an audible notification when a lengthy operation ends. It is currently only supported on Windows and Linux.

The "Queue processing done" sound is played after the last [[The_Batch_Queue | Queue]] image finishes processing.
The "Editor processing done" sound is played after a lengthy in-[[The_Image_Editor_Tab | editor]] operation that took longer than the specified number of seconds is complete.

Sounds can be muted either by disabling the "Enabled" checkbox or by setting fields with sound file references to blank values.

The "Queue" and "Editor processing done" text boxes can either point to wave (.wav) files, or can specify one of the following values:
; Windows:
* SystemAsterisk
* SystemDefault
* SystemExclamation
* SystemExit
* SystemHand
* SystemQuestion
* SystemStart
* SystemWelcome

; Linux
* bell
* camera-shutter
* complete
* dialog-warning
* dialog-information
* message
* service-login
* service-logout
* suspend-error
* trash-empty
* possibly the name of any file in <code>/usr/share/sounds/freedesktop/stereo/</code>

=== Sounds issues under Linux ===

RawTherapee relies on libcanberra to produce sounds. <BR/>
If your sound installation works but that rawtherapee is unable to produce sound,<BR/>
you can check directly that libcanberra is working correctly by compiling this sample:
<pre>
hello_world.sh
--
#!/bin/bash
canberra-gtk-play -i phone-incoming-call -d "hello world"
--

chmod +x hello_word.sh
./hello_word.sh

</pre>

If the hello_world produces sound, you can check rawtherapee by setting "phone-incoming-call" in one of the boxes and try decoding an image.

Problems can arise if you installed pulseaudio, desactivated it (eg: relying on alsa), the hello_world will mostly produce an error message if this happends.

Dynamic processing profiles

2017-03-10T07:16:16Z

Agriggio:

Sometimes a single, "static" default processing profile is not enough to cover
all use cases. For example, the amount of noise reduction to apply varies
according to the Camera and ISO setting used. Another example is the kind and
amount of lens corrections needed, which is obviously dependent on the lens
used.

In order to handle such cases, RawTherapee provides a feature that allows to
create a default processing profile "dynamically", based on the metadata of
the image being processed (such as camera and lens name, shutter speed, ISO
value, and so on).

This is done by defining a set of "Dynamic profile rules". Each rule has a
[[Creating_processing_profiles_for_general_use|(partial) processing profile]] attached to it, plus some conditions on the image
metadata that define whether the rule is applicable. When a picture is edited for the
first time, the list of rules is scanned, and all the profiles that match are
combined (in the order given, so later rules can override earlier ones) to
build the initial processing profile.

In order to activate the functionality, the [[Preferences#Default_Processing_Profile|default processing profile]] must be set to "(Dynamic)".
Rules are defined in the [[Preferences#Dynamic_Profile_Rules|Dynamic Profile Rules]] section of the preferences window.

Dynamic profile rules work on the following image metadata:

; Camera
: the camera name (including brand) as shown in the image info overlay of the [[The_Image_Editor_Tab|Image Editor]]. If active, by default this entry will cause the rule to apply only to pictures taken with the exact camera specified here (except that the capitalization of the string is ignored). However, if the entry starts with the <code>re:</code> prefix, then the rest of the string will be interpreted as a [https://en.wikipedia.org/wiki/Regular_expression regular expression] to use for the matching. For example, a rule with the Camera value set to <code>re:SONY ILCE-[56].00</code> will be applied to all Sony Alpha a5xxx and a6xxx cameras.

; Lens
: the full lens name. As above, a regular expression can be used by starting with the <code>re:</code> prefix

; ISO
: the range of ISO values

; Aperture
: the range of apertures of the lens (measured in f/ stops)

; Focal length
: the range of focal lengths used (in mm)

; Shutter
: the range of shutter speeds in seconds (for example, enter 0.03 for a speed of 1/30")

; Exposure compensation
: the range of exposure compensations.

A screenshot is shown below.

[[File:dynamic-profile-rules-screenshot.png]]

Main Page

2017-03-08T22:16:42Z

Agriggio: /* Processing Profiles */

<div style="text-align: center; padding-bottom: 1em; margin-bottom: 1em; background-color: #363636; color: #DDDDDD;">
<span style="font-family: serif; font-size: 4em; font-weight: bold; text-shadow: 2px 2px 2px #161616;">Raw</span>
<span style="font-family: serif; font-size: 4em; font-weight: bold; text-shadow: 2px 2px 2px #161616; color: #BBBBBB">Pedia</span><br>
<span style="font-variant: small-caps;">The encyclopedia of RawTherapee, raw shooting and everything raw</span>
</div>

<div style="float: left; clear: right">
{| class="wikitable" style="float: left; margin-right: 2em; text-align:center; font-variant: small-caps"
|-
! style="padding: 0 1em;" colspan="2" | In other languages
|-
| [[File:Flag_of_France.svg|90x60px|frameless|link=Main_Page/fr|Française]]<br>[[Main_Page/fr|Français]]
| [[File:Flag_of_Japan.svg|90x60px|frameless|link=Main_Page/jp|日本]]<br>[[Main_Page/jp|日本語]]
|}

{| class="wikitable" style="float: left; text-align:center; font-variant: small-caps"
|-
! style="padding: 0 1em;" colspan="3" | Download book
|-
| [[File:P_literature.gif|60x60px|frameless|link=RawPedia:Books/RawPedia_Book]]<br>[[RawPedia:Books/RawPedia_Book | English]]
| [[File:P_literature.gif|60x60px|frameless|link=RawPedia:Books/RawPedia_Book/fr]]<br>[[RawPedia:Books/RawPedia_Book/fr | French]]
| [[File:P_literature.gif|60x60px|frameless|link=RawPedia:Books/RawPedia_Book/jp]]<br>[[RawPedia:Books/RawPedia_Book/jp | Japanese]]
|}
</div>
<br style="clear: both;">

<div style="background-color: #f6f6f6; border: 1px solid #aaa; padding: 1em; margin-bottom: 1em;">
[[image:Rawtherapee_rawpedia_header1_h300.jpg|right]]
== RawTherapee ==
=== General Information ===
<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3;">
* [[Getting Started]]
* [[Features]]
* [[The Floating Point Engine]]
* [[8-bit and 16-bit]]
* [[RGB and Lab]]
* [[Making a Portable Installation]]
* [[The File Browser Tab]]
* [[The Image Editor Tab]]
* [[Batch Adjustments - Sync]]
* [[Saving]]
* [[The Batch Queue]]
* [[Edit Current Image in External Editor]]
* [[Command-Line Options]]
* [[Keyboard Shortcuts]]
* [[Adding Support for New Raw Formats]]
* [[File Paths]]
* [[Preferences]]
* [[Negative]]

</div>

<hr />

<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3;">
<div style="display: inline-block; width: 100%;">
=== Processing Profiles ===
* [[Sidecar Files - Processing Profiles]]
* [[Creating processing profiles for general use]]
* [[Dynamic processing profiles]]
</div>
<div style="display: inline-block; width: 100%;">
==== Processing Profile Scripts ====
* [[RTProfileSelector]]
* [[RTbatch]]
</div>
<div style="display: inline-block; width: 100%;">
==== Bundled Processing Profiles ====
* [[Default]]
* [[Faded]]
</div>
</div>

<hr />

=== Tool Description ===
* [[General Comments About Some Toolbox Widgets]]
<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3;">
<div style="break-inside: avoid-column; -webkit-column-break-inside: avoid;">
==== Exposure Tab ====
* [[Exposure]]
* [[Gamma - Differential]] (WIP, not available yet)
* [[Shadows/Highlights]]
* [[Tone Mapping]]
* [[Vignetting Filter]]
* [[Graduated Filter]]
* [[Lab Adjustments]]
* [[CIECAM02|CIE Color Appearance Model 2002]]
</div>

<div style="break-inside: avoid-column; -webkit-column-break-inside: avoid;">

==== Detail Tab ====
* [[Sharpening]]
* [[Edges and Microcontrast]]
* [[Impulse Noise Reduction]]
* [[Noise Reduction]]
* [[Defringe]]
* [[Contrast by Detail Levels]]
</div>
<br>
<div style="break-inside: avoid-column; -webkit-column-break-inside: avoid;">
==== Color Tab ====
* [[White Balance]]
* [[Vibrance]]
* [[Channel Mixer]]
* [[Black-and-White]]
* [[Black-and-White addon]]
* [[HSV Equalizer]]
* [[Film Simulation]]
* [[RGB Curves]]
* [[Color Toning]]
* [[Color Management]]
* [[Color Management addon]]
</div>

<div style="break-inside: avoid-column; -webkit-column-break-inside: avoid;">
==== Wavelets Tab ====
* [[Wavelets]]
</div>

<div style="break-inside: avoid-column; -webkit-column-break-inside: avoid;">
==== Transform Tab ====
* [[Crop]]
* [[Resize]]
* [[Lens/Geometry]]
</div>

<div style="break-inside: avoid-column; -webkit-column-break-inside: avoid;">
==== Raw Tab ====
* [[Demosaicing]]
* [[Preprocessing]]
* [[Chromatic Aberration]]
* [[Raw Black Points]]
* [[Raw White Points]]
* [[Dark Frame]]
* [[Flat Field]]

</div>

<div style="break-inside: avoid-column; -webkit-column-break-inside: avoid;">

==== Metadata Tab ====
* [[Exif Tab]]
* [[IPTC Tab]]
</div>
</div>

<hr />

=== Interact ===
* [[Forum]]
* [[IRC]]
* [[Google+]]

=== Compiling ===
* In [[Linux]]
* In [[Windows]]
* In [[macOS]]

=== Troubleshooting ===
* [[How to write useful bug reports]]
* [[How to fix crashes on startup]]
</div>

<div style="background-color: #f6f6f6; border: 1px solid #aaa; padding: 1em; margin-bottom: 1em;">

== General Photography ==
* [[How to convert raw formats to DNG]]
* [[How to create DCP color profiles]]
* [[How to extract and examine ICC profiles]]
* [[How to get LCP and DCP profiles]]
* [[How to get Nikon ICM profiles]]
* [[Watermarking]]
* [[Image file formats and compression]]
</div>

Dynamic processing profiles

2017-03-08T22:16:33Z

Agriggio: Created page with "Sometimes a single, "static" default processing profile is not enough to cover all use cases. For example, the amount of noise reduction to apply varies according to the Came..."

File:Dynamic-profile-rules-screenshot.png

2017-03-08T22:15:01Z

Agriggio: Screenshot of the "Dynamic profile rules" editor

Screenshot of the "Dynamic profile rules" editor