http://rawpedia.rawtherapee.com/api.php?action=feedcontributions&user=DrSlony&feedformat=atomRawPedia - User contributions [en]2024-03-29T07:45:49ZUser contributionsMediaWiki 1.38.4http://rawpedia.rawtherapee.com/index.php?title=Template:AdobeDngConverterLinux&diff=10247Template:AdobeDngConverterLinux2023-12-06T00:45:19Z<p>DrSlony: Updated for AdobeDNGConverter 16.0.1</p>
<hr />
<div># Install [http://www.winehq.org/ Wine], preferably using your package manager. At the time of writing, wine-8.21 is confirmed to work well with Adobe DNG Converter 16.0.1.<br />
# Download Adobe DNG Converter for Windows. Try the newest version first. If that doesn't work, try an older version. You can download the newest version from [https://helpx.adobe.com/camera-raw/using/adobe-dng-converter.html Adobe], or you can download older versions from [https://www.filehorse.com/download-adobe-dng-converter/old-versions/ FileHorse].<br />
# Set Wine to Windows 10 mode:<br />
#: <pre style="white-space:pre-wrap;">WINEPREFIX="$HOME/wine-dng" winecfg</pre><br />
#: Wine might ask you to install Mono. At the time of writing, it was not needed to run Adobe DNG Converter, so installing it is not required but not needed either.<br />
#: In the "Applications" tab set "Windows Version" to "Windows 10". Hit "Ok" to close Wine configuration.<br />
# Install Adobe DNG Converter:<br />
#: <pre style="white-space:pre-wrap;">WINEPREFIX="$HOME/wine-dng" wine ~/Downloads/AdobeDNGConverter_x64_16_0_1.exe</pre><br />
#: It will install to <code>$HOME/wine-dng/drive_c/Program Files/Adobe/Adobe DNG Converter/Adobe DNG Converter.exe</code><br />
# This step is optional. There is an issue affecting all versions of Wine older than 5.0-rc5 when using Adobe DNG Converter version 11.2 or newer. The issue results in Wine crashing on startup. The issue was fixed in Wine 5.0-rc5, see Wine bug [https://bugs.winehq.org/show_bug.cgi?id=46972 #46972]. If you use any version of Wine lower than 5.0-rc5, you can easily circumvent the issue.<br />
#: Run Wine configuration:<br />
#: <pre style="white-space:pre-wrap;">WINEPREFIX="$HOME/wine-dng" winecfg</pre><br />
#: Go to the "Libraries" tab, add a new override for <code>api-ms-win-core-winrt-error-l1-1-0</code>, then edit it and select "Disable". Done.<br />
# Run Adobe DNG Converter:<br />
#: <pre style="white-space:pre-wrap;">WINEPREFIX="$HOME/wine-dng" wine "$HOME/wine-dng/drive_c/Program Files/Adobe/Adobe DNG Converter/Adobe DNG Converter.exe"</pre><br />
# Add an alias so that you can run Adobe DNG Converter from a console with ease:<br />
#: <pre style="white-space:pre-wrap;">echo "alias dng='WINEPREFIX=\"\$HOME/wine-dng\" wine \"\$HOME/wine-dng/drive_c/Program Files/Adobe/Adobe DNG Converter/Adobe DNG Converter.exe\"'" >> ~/.bashrc && exec bash</pre><br />
# To run Adobe DNG Converter, just type <code>dng</code> in a console.</div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=Wavelet_Levels&diff=10135Wavelet Levels2023-04-06T14:22:05Z<p>DrSlony: Updated dead link to Guided Image Filtering</p>
<hr />
<div><div class="pagetitle">Wavelet Levels</div><br />
<br />
[[File:Daffodil_split.jpg|none|thumb|700px|class=heroed|A ''before'' (bottom) and ''after'' (top) view of an image processed with Wavelet levels.]]<br />
<br />
__TOC__<br />
<br />
== How is this tool organized? ==<br />
<br />
The Wavelet Levels tool is extensive and its underlying algorithms are complex. It has most of the functions necessary for processing photographs from start to finish with the exception of certain tasks such as interpolation or color management. However, it is most useful when it is used to complete or refine processing operations carried out in other parts of RawTherapee. It allows you to work on different levels of detail to produce subtle contrast and color effects, remove noise or defects in the image without sacrificing overall detail, or work on the color and luminance of the image without introducing artifacts.<br />
<br />
It can be used for any sort of image but its unique capabilities make it particularly suitable for portraits, macro photography, astro-photography etc., where selective control over fine detail is important. It can also be used to great effect in landscape photography to remove noise in skies, compress the dynamic range while at the same time preserving the details, reduce the noise, remove color casts in shadows, and create interesting luminosity effects.<br />
The capabilities are almost limitless, but you will only be able to use them properly if you have a good understanding of the underlying principles and operation of the various tools, '''so please read on!'''<br />
<br />
The tool is organized around a general '''Wavelet Settings''' module followed by a series of modules which can activated or deactivated to perform specific tasks.<br />
<br />
== What are Wavelets? ==<br />
<br />
A [https://en.wikipedia.org/wiki/Wavelet Wavelet], or more precisely a [https://en.wikipedia.org/wiki/Wavelet_transform Wavelet Transform], is a complex mathematical function which is very useful in image processing. It allows you to split images into different levels of detail so that you can work on the level that interests you.<br />
<br />
The wavelets term was introduced in the early 1980s by French physicists Jean Morlet and Alex Grossman: they used the French word ''ondelette'', which means ''small wave''. Later, this word was adapted to English changing ''onde'' by ''wave'', leading to ''wavelet''.<br />
<br />
The ''Wavelet Transform'', which is similar to a ''Fourier Transform'', represents data as combinations of known and predefined waves (the frequencies), so that the result is as close as possible to the original data. Broadly speaking, the main difference for two-dimensional images is that in the Wavelet Transform the data being analyzed is represented as the frequencies present at the pixel level of the image, whereas in the standard Fourier Transform the data represents the frequencies present in the full image. Therefore, using wavelets offers more precision when analyzing the data. &nbsp; <span style="font-size: 0.7em; font-style: italic;">[Obviously this is a very simplistic explanation: mathematicians would surely have a lot to say here...]</span><br />
<br />
[[File:Wavelet_daubechies20.jpg|thumb|400px|Graphic rendering of a Daubechies wavelet|link=https://en.wikipedia.org/wiki/Daubechies_wavelet]]RawTherapee uses wavelets in various tools, and in this one in particular it uses the [https://en.wikipedia.org/wiki/Daubechies_wavelet Daubechies] wavelet, to decompose the elements of the image into the components of the [https://en.wikipedia.org/wiki/CIELAB_color_space L*a*b* color space] (''L*'', ''a*'' and ''b*'').<br />
<br />
Image decomposition is carried out using an [https://en.wikipedia.org/wiki/Algorithm algorithm] to analyze the «internal» contrast of groups of pixels (2x2=4 pixels on the first level, 4x4=16 pixels on the second level, ...) in three directions: vertical, horizontal and diagonal. This analysis converts these contrast values into sets of wavelets with different amplitudes and intensities and stores their characteristics in coefficient matrices, which indicate how the wavelets should be combined to regenerate an image as close as possible to the original. <br />
<br />
Each time you make modifications (contrast, tone, noise, ...) this regeneration is done automatically, so that you can immediately see the result of your adjustments.<br />
<br />
In fact the moment the image is decomposed, it ceases to exist, leaving only sets of coefficients (one set for each level) which will be used subsequently by the tool. These coefficient sets can be used to characterize the image in the following two ways:<br />
* Several levels of detail: the first level corresponds to details with an area of 2x2 pixels; the tenth level corresponds to «details» with an area of 1024x1024 pixels. The choice of how many you use depends on your needs, however keep in mind that processing time and memory requirements will increase with the number of levels.<br />
: Because only ''variations'' (gradients, or differences) in [https://en.wikipedia.org/wiki/Hue hue] or [https://en.wikipedia.org/wiki/Luminance luminance] are analyzed at each level, the levels will not contain any information if an image is absolutely uniform in luminance and color. In this case any differences extracted from individual levels will come from digital noise and changes in contrast (or chromaticity) due to edge effects, fog or other scene-related optical phenomena.<br />
* A residual image: the result of removing the details from all of the decomposed levels of the original image. Consequently, any modifications (contrast, chromaticity etc.) that are carried out within a particular level will have no effect on the residual image and vice versa.<br />
<br />
Moreover, each level the tool takes into account the set of coefficient values and calculates their arithmetic mean (for each level the mean will be different) and the [https://en.wikipedia.org/wiki/Standard_deviation standard deviation]. By adding the maximum and minimum coefficients to this data, a characteristic distribution curve is generated for each level (it should be noted that this curve is not [https://en.wikipedia.org/wiki/Normal_distribution Gaussian]). This information is used in different ways in the various algorithms used by the wavelet levels tool.<br />
<br />
== In practice ==<br />
<br />
After decomposition, the resulting levels can be used for different purposes: image compression, noise reduction, [http://www.intechopen.com/books/discrete-wavelet-transforms-algorithms-and-applications/application-of-discrete-wavelet-transform-in-watermarking secret watermarking], specific residual image treatment for astronomy, etc.<br />
<br />
Depending on your needs, you can work either with an individual level of detail, with several levels of detail (one after another), with the residual image, or with all of them combined.<br />
<br />
The size of the details included in each level is:<br />
<br />
[[File:Wavelet_detail_size.jpg|thumb|350px|Comparison of actual detail size at each level]]<br />
:: '''1 (Finest)''' : 2x2 pixels<br />
:: '''2''' : 4x4 pixels<br />
:: '''3''' : 8x8 pixels<br />
:: '''4''' : 16x16 pixels<br />
:: '''5''' : 32x32 pixels<br />
:: '''6''' : 64x64 pixels<br />
:: '''7''' : 128x128 pixels<br />
:: '''8''' : 256x256 pixels<br />
:: '''9 (Coarsest)''' : 512x512 pixels<br />
:: '''Extra''' : 1024x1024 pixels<br />
<br />
If you were to select 5 detail levels, the changes in the various levels would be limited to details with 32 pixels size or smaller. In this case the residual image would have all the details of the image, except those included in levels ''1'' to ''5''. And since the details that have been removed are relatively small, the residual image would be similar to the original image.<br />
<br />
On the other hand, if you chose ''level 9'' you could change the details with a size of 512 pixels and 1024 pixels (''level Extra''). In this case the residual image would be quite different from the original image, as the levels from ''1'' to ''Extra'' would contain all the details, leaving little more than a blurred background.<br />
<br />
Wavelet decomposition separates the ''[https://en.wikipedia.org/wiki/Lightness lightness]'' and the ''[http://www.huevaluechroma.com/015.php chroma]'' channels ([https://en.wikipedia.org/wiki/CIELAB_color_space#CIELAB ''a*'' and ''b*'']) in the residual image and in each of the levels. This allows you to apply different adjustments to the brightness and tones of each level and carry out completely different processing operations on the residual image. This means that the levels and the residual image are independent and the tool will only modify those levels where changes have been made. The rest will remain untouched and the residual image will continue to be what is left after the details in each of the levels have been removed (regardless of whether they have been modified).<br />
<br />
Note that if you want to use the Wavelet Levels tool at the same time as [[CIECAM02 | the CIECAM tool]], you may get artifacts due to the fact that the CIECAM color model uses specific values that are close to, but different from the values of the Lab color space. Because of the way the tool is coded these artifacts are unavoidable, but their appearance will depend on which processing operations have been carried out.<br />
<br />
==== The preview ====<br />
<br />
The size of the image on the screen has a direct impact on the perceived sharpness and on one’s ability to see any small changes introduced by the various modules: '''the effects of this tool are only visible at full size''' (or larger).<br />
<br />
In practice, this means that, [[General_Comments_About_Some_Toolbox_Widgets#The_Preview_Area | for processing speed reasons]], you must have the final size of the image in mind. If it is planned to reduce the image size (scale it down, not crop it), then it is advised to first export it with its final size and process it afterwards with wavelets. Keep this in mind because otherwise what you see in the preview will not be the same as the final exported result.<br />
<br />
There is also another limitation: RawTherapee uses all the levels it can in the preview and ignores levels that have details larger than the portion of the image you see on the screen. However, if the changes in the ignored levels are not shown on screen, they will be applied when the image is saved to disk.<br />
<br />
'''Examples'''<br />
<br />
* '''''Example 1''''': the image is '''4096x2160''' pixels, you have enlarged it (to 100% or more) and in the preview you see a '''1500x1200''' pixel-area similar in size to the final image. This is the ideal case because on the screen you can see all the modifications in all of the levels (up to the ''level Extra''). In addition, any changes made in any of the levels will be included in the final image.<br />
* '''''Example 2''''': the image is '''4096x2160''' pixels, but you have enlarged it and can only see '''300x200''' pixels in the preview. On the screen you won't be able to see any change in details bigger than ''level 7'' (details of 128 pixels), but when you save it the changes you made in levels ''8'', ''9'' and ''Extra'' will be included (because the image is bigger than 1024x1024 pixels).<br />
* '''''Example 3''''': the image is '''720x480''' pixels and you have enlarged it until you can only see '''300x200''' pixels in the preview. On the screen you will not be able to see any modification in details bigger than those of the ''level 7'' (details of 128 pixels). When saving, the changes you made in ''level 8'' will be included (details of 256 pixels), but levels ''9'' and ''Extra'' '''will NOT''' be included.<br />
<br />
To help keep this important information in mind, the tool indicates how many levels are being used for the preview (under the last slider of the ''Contrast'' module). In the examples 2 and 3 it would indicate: «'''Preview maximum possible levels = 7'''».<br />
<br />
==== Contrast by Detail Levels vs Wavelet Levels ====<br />
<br />
It's worth mentioning that RawTherapee has a tool called ''[[Contrast_by_Detail_Levels|Contrast by Detail Levels]]'' and although it looks like the Wavelet Levels tool, there are several important differences between them:<br />
* ''Contrast by Detail Levels'' has fewer levels (6, instead of up to 10),<br />
* ''Contrast by Detail Levels'' only allows you to adjust the luminance of each level, while Wavelet Levels also allows you to adjust the chroma of each level,<br />
* ''Contrast by Detail Levels'' adjusts equally all luminance (or chroma) values present in the level, while Wavelet Levels performs a progressive adjustment ([[#The_attenuation_curve|this is explained further in the contrast attenuation section]]),<br />
* ''Contrast by Detail Levels'' doesn't have a residual image.<br />
<br />
That said, it is possible to use both tools at the same time. It should be noted however that ''Contrast by Detail Levels'' is applied earlier in the [[Toolchain_Pipeline|Processing Pipeline]], so depending on the intensity of the adjustments made there, the details presented in levels from ''1'' to ''6'' may be affected. In other words, since the contrast will have changed with the ''Contrast by Levels of Detail'' settings, the analysis by Wavelet Levels could decompose the image in a different way, so the results would be different. In any case, if you have to use both tools, it is recommended that you adjust first the Contrast by Detail Levels and then adjust the Wavelet Levels.<br />
<br />
== General tool configuration ==<br />
<br />
When this tool is turned on, any adjustments will affect all the subsequent modules.<br />
<br />
=== Strength ===<br />
<br />
With this slider you can adjust the overall intensity of the tool. It works on a similar principle to the opacity slider used for blending layers in the GIMP: any adjustments made in the Wavelet Levels tool can be blended back into the original image using the Strength slider. This allows you to make fairly aggressive adjustments and then adjust the overall intensity to achieve the desired result. <br />
<br />
=== Wavelet levels ===<br />
<br />
This slider lets you decide how many detail levels the image will be decomposed into. You can choose any level between ''4'' and ''9'' (the 10th level, called ''Extra'', appears automatically when you select ''level 9''). The higher the number, the more processing time and memory will be required.<br />
<br />
=== Tiling method ===<br />
<br />
A drop-down list allows you to choose from:<br />
* Full image,<br />
* [https://en.wikipedia.org/wiki/Euclidean_tilings_by_convex_regular_polygons Tiles].<br />
<br />
It is always preferable to use ''Full image'', because it avoids problems in the transition area between tiles.<br />
<br />
However, if you do not have enough RAM, or if you are processing very large images (e.g., 50 Megapixels or more), you may have to use the tiles:<br />
<br />
{| class="RP3c-grid"<br />
! class="tablegrid-caption" | Required memory, in bytes, with 9 detail levels<br />
|-<br />
! role="columnheader" |<br />
! role="columnheader" data-colh1="Pentax K10D" | Pentax K10D<br />
! role="columnheader" data-colh2="Nikon D810" | Nikon D810<br />
|-<br />
! role="rowheader"| Megapixels (Mpx)<br />
| data-colh1="Pentax K10D" | 10.2Mpx (3888 x 2608)<br />
| data-colh2="Nikon D810" | 36.3Mpx (7360 × 4912)<br />
|-<br />
! role="rowheader"| To open the image (all tools turned off)<br />
| data-colh1="Pentax K10D" | 116MiB ([[https://en.wikipedia.org/wiki/Mebibyte Mebibytes]])<br />
| data-colh2="Nikon D810" | 414MiB<br />
|-<br />
! role="rowheader"| Contrast, Chromaticity or Hue Protection turned on<br />
| data-colh1="Pentax K10D" | 329MiB<br />
| data-colh2="Nikon D810" | 1172MiB<br />
|-<br />
! role="rowheader"| + Avoid color shift<br />
| data-colh1="Pentax K10D" | 39MiB<br />
| data-colh2="Nikon D810" | 138MiB<br />
|-<br />
! role="rowheader"| Total<br />
| data-colh1="Pentax K10D" | 483MiB<br />
| data-colh2="Nikon D810" | 1724MiB<br />
|}<br />
<br />
=== Edge performance ===<br />
<br />
An image that has been decomposed into its component parts using the Daubechies method may have up to 10 coefficient scales ranging from D2 (which corresponds to the Haar decomposition) to D20. In RawTherapee the coefficients ''D2 (low), D4 (standard), D6 (standard plus), D10 (medium)'' and ''D14 (high)'' are used. The more coefficients there are, the more detail the wavelet will distinguish albeit with a slight increase in processing time (often negligible).<br />
<br />
Although there is no direct relationship between the resulting quality and the number of coefficients (depending on the original image), choosing the right number of coefficients will allow you to refine the quality of the lower levels, or that of the residual image:<br />
* in some cases the best results for edge detection are obtained with D2<br />
* in other cases with D6 or D14<br />
<br />
This parameter has a fairly strong impact on ''[[#Edge_detection | Edge detection]]'' and also on global decomposition (the relationship between the residual image and each level).<br />
<br />
=== Preview ===<br />
<br />
This group of controls will help you understand how to work with the wavelets tool and assist when fine-tuning the parameters of the various modules (e.g. noise reduction).<br />
<br />
You have a total of four drop-down lists, allowing you to tailor what you see in the preview.<br />
<br />
The group is divided into two main drop-down lists (and several others that will be activated when you make certain selections in the main lists):<br />
* the first lets you choose the preview background<br />
* the second lets you choose which levels will be displayed in the preview<br />
<br />
==== Background ====<br />
<br />
In the '''''Background''''' list you can choose between 3 possible backgrounds: ''Black'', ''Gray'' or ''Residual Image'', which will be used when viewing any of the levels.<br />
<br />
The histogram will take into account these options and will allow you, for example, to see the effects of the settings on the residual image. Note however, that if you choose the black or gray background, you will not see the residual image (the real background) and you may find that the image has a strange look. You should be especially aware of this if you make changes to the detail levels, as the actual effect will not be seen until you put the residual image back into the background. In spite of this, it is sometimes interesting to see the changes against a neutral background to better judge what is happening (for example in noise reduction).<br />
<br />
==== The process levels ====<br />
<br />
<br />
<br />
In the '''''Process''''' list you can select:<br />
# ''One level''<br />
# ''Finer details levels, with selected level'': all levels '''from''' the selected level down to ''level 1'',<br />
# ''Coarser details levels, without selected level'': all levels up to the ''level Extra'' (plus the residual image), '''with the exception''' of the selected level<br />
# ''All levels, in all directions''<br />
<br />
In previous versions of the program, the list was shown with different labels, but the behaviour of the sliders remains unchanged:<br />
* One level<br />
* Below or equal the level: now ''Finer details levels, with selected level''<br />
* Above the level: now '''Coarser details levels, without selected level'''<br />
* All levels, in all directions<br />
<br />
If you select any of the first three options, two drop-down lists will be activated just below ''Process:''.<br />
* in the list on the left you can decide which level the previous options refer to (from ''level 1'' to ''9'', the ''level Extra'', or the ''Residual Image'').<br />
* in the list on the right you can choose the wavelet decomposition direction (''Vertical, Horizontal, Diagonal, All directions'').<br />
<br />
If you select the option ''All levels, in all directions'', you can edit the levels directly on the residual image (the two lower lists would remain disabled). This option is useful if you already have experience with the tool and you prefer to view the entire image while editing it. It is also the option you should select before exporting. Keep in mind that what you see in the preview will be what is exported in the final image and is shown in the histogram: if you have selected ''One level'', you will see only one level on the screen and the histogram will reflect the RGB values of that particular level. When you export the image only the chosen level will be included in the final image so '''before exporting, make sure you select ''All levels, in all directions'''.<br />
<br />
==== Suggestions for use ====<br />
<br />
* you can select ''One level'' with a gray background to see how the selected Daubechies' coefficient (from D2 to D14) has decomposed the details, and then try out different coefficients to see which one offers the most accurate detail separation<br />
* you can select ''One level'' to find the level that has the details you want to work on (such as the level that has extracted the blemishes from the skin, but not its texture)<br />
* you can select ''One level'' and see the effect of contrast changes on that particular level, or fine tune the noise reduction<br />
* you can select ''Coarser details levels, without selected level'' and ''8'', to see the residual image along with the largest details and better appreciate the action of the various parameters of the module ''Residual Image''<br />
* you can select ''Finer details levels, with selected level 4'' and as a background ''Residual Image'', to see the modifications in the finest details in their context, without the larger details masking what you are doing<br />
<br />
=== Example (the preview) ===<br />
<br />
Below is a sample image with minimal processing that will be used in all the subsequent examples. Next to it, from left to right you will see the ''level 2'' details, the ''level 4'' details and the ''residual image''.<br />
<br />
In the two examples showing the details, the decomposition has been done with '''''Edge performance''''' set to ''D6 - standard plus'', the color ''gray'' has been selected as '''''Background'''''. In addition, to isolate the detail, ''One level'' has been selected in '''''Process'''''.<br />
<br />
The ''Residual Image'' is the result of removing all of the details after choosing ''5 Wavelet Levels''.<br />
<br />
<span style="font-size: 0.7em; font-style: italic;">&nbsp;&nbsp;'''''To enlarge the images click on them and when the new page loads, click on the image a second time'''''. </span><br />
<br />
<div><ul class="leftalign"> <br />
<li class="RPgallery"> [[File:wavelet_pic.jpg|thumb|none|400px|Original image: a Prunus pisardii flower (cherry plum) at 50% of original size.]] </li><br />
<li class="RPgallery"> [[File:wavelet_config_L2.jpg|thumb|none|400px|''Level 2'' details over a gray background: see how the texture of the petals has been captured in this level (you must enlarge the image to see it properly).]] </li><br />
<li class="RPgallery"> [[File:wavelet_config_L4.jpg|thumb|none|400px|''Level 4'' details over a gray background: in this level you can see what we would probably draw if we wanted to make a sketch of the flower.]] </li><br />
<li class="RPgallery"> [[File:wavelet_config_RI.jpg|thumb|none|400px|''Residual Image'' details: we can see perfectly the fundamental hue of each zone of the photo.]] </li><br />
</ul></div><br />
<br />
== Contrast module ==<br />
<br />
In this module you can modify the lightness contrast (''L*'' component of decomposition) of the details in each level independently. This allows you to increase the contrast of smaller details to give an impression of greater sharpness, while reducing the contrast of larger details. A practical benefit of this approach is that by reducing the overall contrast (the large details), you do not have to increase the fine details as much to achieve an impression of sharpness. This makes it easier to avoid introducing artifacts.<br />
<br />
=== The attenuation curve ===<br />
<br />
<br />
As discussed in an earlier chapter, the wavelets tool calculates the mean and standard deviation for each decomposition level and will use these values in all of the modules.<br />
<br />
In the case of the Contrast module, the first step is to set the contrast slider values for each decomposed level depending on the effect required. However, if you only perform this action, the contrast variations would be proportional to the original contrast ([https://en.wikipedia.org/wiki/Homothetic_transformation homothetical modifications], as in the ''Contrast by Detail Levels'' tool) and it would be quite easy to generate artifacts.<br />
<br />
To overcome this problem, the contrast values for the details in each of the levels are analyzed and sorted before being modified and progressively attenuated similar to the following curve :<br />
<br />
[[File:wavelet_beta.png|frame|none|Graphical representation of the proportional changes made to each contrast value.]]<br />
<br />
Broadly speaking and for each level, the graph shows that:<br />
* the lowest contrast values are to the left and the highest contrast values to the right<br />
* the contrast value set for each level (''contrast'' in the graph) defines the maximum modification that will be applied to the contrast values present in the level<br />
* the modification will be maximum around the average contrast value of each level (the ''mean'' value on the graph)<br />
* the more the contrast values vary from the average contrast value, the less they will be changed <br />
* high or strong contrast values are more attenuated than low ones<br />
<br />
This means that for each level, the biggest contrast changes will be made to the mid-contrast values while avoiding the extreme values to avoid excessive effects or artifacts. However, keep in mind two fundamental points:<br />
# the mean contrast value is the arithmetic mean '''of the contrast values present in the level''': if all the contrast values are high (strong contrasts), the mean value will also be high and the extreme contrasts in that particular level will be modified less<br />
# each level has its own average value, which depends on the contrast values present in the details of that particular level<br />
<br />
=== Contrast Levels ===<br />
<br />
[[File:wavelet_contrast_buttons.jpg|frame|The values of each level after clicking several times on '''''Contrast +''''']] The number of levels shown is defined by the '''''Wavelet levels''''' and you can reduce or increase this number in the wavelet configuration settings.<br />
<br />
The '''''Contrast -''''' and '''''Contrast +''''' buttons make it easier to progressively change the values of each level: stronger in the first levels and more discreet in the last. As you can see in the example, the progression is homogeneous: starting from the ''Extra level'', which has not been modified, each level has been increased by 31 units with respect to the previous level (the actual amount will depend on the number of times you click on the Contrast+ or the Contrast- buttons).<br />
<br />
In general these buttons allow you to define a logical progression of [[Edges_and_Microcontrast#Microcontrast|microcontrast]] values: higher for the first levels and lower for the last levels.<br />
<br />
Don't forget that if a level has uniform contrast, the slider action for that level will not have any effect (if there are no details, nothing is changed).<br />
<br />
Note that the residual image is not included in this group of controls because it is not a level: it is what is left of the original image after removing all the details distributed across all of the levels.<br />
<br />
=== Attenuation and selectivity in contrast changes ===<br />
<br />
<br />
There are 3 sliders that allow you to adjust the curve for each level, as explained in [[#Analysis_of_the_contrasts_in_each_level | Analysis of the contrasts in each level]]:<br />
<ol><br />
<li> '''''Attenuation Response''''': by selecting positive values the upper part of the curve becomes wider around the medium contrast area, and is weighted towards the higher contrasts. Conversely, selecting negative values narrows the curve, thus reducing the range of contrasts that undergo any noticeable modification. Graphically:<br />
<div><ul class="leftalign"> <br />
<li class="RPside2side"> [[File:wavelet_beta+damper.png|thumb|left|590px| The curve can be widened by selecting a positive''Attenuation Response'' value. The green background curve is the original curve, with the slider at ''0''. The horizontal line (''contrast'') is the maximum value that can be set by the contrast slider at that level.]] </li><br />
<li class="RPside2side"> [[File:wavelet_beta-damper.png|thumb|left|590px|The curve can be made narrower by selecting a negative ''Attenuation Response'' value. The green background curve is the original curve, with the slider at ''0''. As indicated previously, the changes in the curve are more pronounced in the area with high contrast values.]]</li><br />
</ul></div></li><br />
<li> '''''Offset''''': shifts the top of the curve, so that the strongest contrast modifications are no longer made to the medium contrasts. By shifting the curve to the right, the higher contrast values will vary more, whereas with negative slider values, the lower contrast values will be modified more. Graphically:<br />
[[File:wavelet_beta+offset.png|none|frame|class=heroed|Selecting a positive ''Offset'' will affect the higher-contrast values (but not the extreme contrasts) for that particular level.]]</li><br />
<li> '''''Low contrast threshold''''': this is the minimum contrast value that the details in the decomposition level must have for them to be taken into account. Lower contrast values, which have a value lower than the minimum value, will not be taken into account when calculating the mean of that level, nor will they undergo any variation, whatever the slider settings. In this way we can avoid highlighting noise or finer and more delicate textures.</li><br />
</ol><br />
<br />
=== Apply To ===<br />
<br />
<br />
This control block allows you to decide whether changes in contrast in individual levels apply to all the details or only to those details with pixels that are within a given range of [https://en.wikipedia.org/wiki/Luminance luminance]. This allows you, for example, to increase the contrast of fine details with high luminance and reduce the contrast of larger details with low luminance.<br />
<br />
In the drop-down list, you decide where to apply the contrast changes: over the whole range of luminance values (i.e. to all the details in each level) or only to details that have a certain luminance value.<br />
<br />
==== Luminance ranges ====<br />
<br />
If you have selected the ''Whole luminance range'', the modification will apply to all of the details in each of the levels. However, if you choose ''Selective luminance range'', you can decide which details will be modified in which levels.<br />
<br />
In addition, after selecting the ''Selective luminance range'' two threshold curves and two sliders will appear allowing you to customize the result. i.e.:<br />
<br />
* '''Finer levels luminance range''':<br />
** this is a small area with a black and white gradient and four points that define the range of luminance values that will be affected by the change in contrast <div style="overflow: hidden">[[File:wavelet_contrast_highlight.jpg|left]]</div><br />
** If you move your mouse over it, you will see where the default limits are: ''Bottom-Left: 50, Top-Left: 75, Top-Right: 98, Bottom-Right: 100''. This range covers the highlights<br />
** these are the luminance values that must be in the image for the contrast change to be applied to the details (see following slider explanation)<br />
** the default values are as follows:<br />
*** details with luminance of 50 or less will not be changed<br />
*** details with a luminance of 50 to 75 will be subject to an increasing amount of modification<br />
*** between 75 and 98, 100% of the modification will be applied<br />
*** between 98 and 100, progressively less change will be applied<br />
** to change the values of the points on the curve, we have two options:<br />
*** click and move one of the two points on one side (left or right) and slide the two points together<br />
*** press the ''shift'' key, click on a point and slide it to move only that point<br />
** the default values are set for the highlights but you can modify the points to cover any part of the range from the shadows to the highlights as required.<br />
<br />
* '''Finer levels''': only levels from the selected value and below will be affected by the ''Finer levels luminance range'' threshold curve.<br />
<br />
* '''Coarser levels luminance range''':<br />
** another small area with a black and white gradient and four points that define the range of luminance values that will be affected by the change of contrast <div style="overflow: hidden">[[File:wavelet_contrast_shadow.jpg|left]]</div><br />
** again, by hovering your mouse over it, you will see where the default boundaries are around the shadows: ''Bottom-Left: 0, Top-Left: 2, Top-Right: 25, Bottom-Right: 50''<br />
** the default levels are:<br />
*** details with luminance between 0 and 2 will be subject to an increasing amount of contrast change<br />
*** between 2 and 25, 100% contrast modification will be applied<br />
*** between 25 and 50, progressively less change will be applied<br />
*** from 50 onwards no change will be applied<br />
** the default values are set for the shadows but you can modify the points to cover any part of the range from the shadows to the highlights as required.<br />
<br />
* '''Coarser levels''': only those levels from the value set with this slider up to the selected number of ''wavelet levels'' will be affected by the ''Coarser levels luminance range'' threshold curve.<br />
<br />
No modifications will be made to any level that is not included in either a ''Finer levels'' or a ''Coarser levels'' selection, no matter what values have been set with the Contrast sliders. For these levels the final result will be the same as setting a contrast-slider value of ''0''.<br />
</br><br />
<br />
==== Case Studies ====<br />
<br />
* you are using 7 levels and only want to change ''level 7'' within the range set by the ''Coarser levels luminance range'' threshold curve: adjust the slider for ''Coarser levels'' to ''7''<br />
* you are using 7 levels and only want to selectively modify the finest details: set the ''Finer levels'' to the highest level you want to modify, and set the Contrast sliders for the rest of the levels to ''0''<br />
* you are using 7 levels and you want to selectively adjust levels ''1'' and ''2'' in accordance with the luminance values set in the threshold curve for ''Finer levels luminance range'' and adjust levels ''6'' and ''7'' in accordance with the luminance values set in the threshold curve for the ''Coarser levels luminance range'': set the ''Finer levels'' slider to ''2'' and the ''Coarser levels'' slider to ''6''. This will selectively modify levels ''1'', ''2'' and ''6'', ''7'' in accordance with the relevant threshold curve settings and the details in levels ''3'', ''4'' and ''5'' will remain unchanged<br />
<br />
=== Example (changing contrast) ===<br />
<br />
The sample image is shown below and next to it, from left to right, are several different possibilities when a contrast increase is applied to all levels (after pressing ''15 times'' on the button '''''Contrast +''''').<br />
<br />
First the effect on the '''''Whole luminance range''''' is shown and to the right the effect if you set the '''''Selective luminance range'''''. Finally, an example of how the changes can be nuanced by the '''''Strength''''' slider.<br />
<br />
The sliders not mentioned have been left at their default values (the control points on the curves, ...).<br />
<br />
<div><ul class="leftalign"> <br />
<li class="RPgallery"> [[File:wavelet_pic.jpg|thumb|none|400px|Original image.]] </li><br />
<li class="RPgallery"> [[File:wavelet_contrast_15C+_WL.jpg|thumb|none|400px|After applying the effect on the '''''Whole luminance range''''': the increased visibility of the background noise is particularly noticeable.]] </li><br />
<li class="RPgallery"> [[File:wavelet_contrast_15C+_H3S6.jpg|thumb|none|400px|After applying the effect over the '''''Selective luminance range''''': '''''Finer levels''''' at ''3'', '''''Coarser levels''''' at ''6'': the effect is better, but it looks a little exaggerated.]] </li><br />
<li class="RPgallery"> [[File:wavelet_contrast_15C+_H3S6_Str50.jpg|thumb|none|400px|The same treatment as above, but lowering the overall '''''Strength''''' of the tool to ''50''.]] </li><br />
</ul></div><br />
<br />
And now both the original image and the final image, side by side to better appreciate the differences: you can see an increase in the sharpness of the texture of the petals, without ruining the overall effect.<br />
<br />
<div><ul class="leftalign"> <br />
<li class="RPside2side"> [[File:wavelet_pic.jpg|thumb|none|600px|Original image.]] </li><br />
<li class="RPside2side"> [[File:wavelet_contrast_15C+_H3S6_Str50.jpg|thumb|none|600px|Contrast modified and effect reduced to 50%.]] </li><br />
</ul></div><br />
<br />
== Chroma module ==<br />
<br />
This module works in a similar way to the contrast module, except that in this case, the tool analyzes the color contrast (components ''a*'' and ''b*'').<br />
<br />
In the drop-down list '''''Chrominance method''''' you have the following options:<br />
* ''Whole chroma range'': with this option, any change in any level will affect the full range of chroma, regardless of the values that have been set in the ''Contrast module'' levels.<br />
* ''Saturated/pastel'': here you can modify two threshold curves that act simultaneously and limit the pastel and saturated tones, regardless of the values in the ''Contrast module'' levels.<br />
* ''Link contrast levels'': the changes in chroma will be directly related to those made at each level of the ''Contrast module''.<br />
<br />
When you select ''Whole chroma range'' or ''Saturated/pastel'' you can use the ''Neutral'' button to reset all the level sliders to their default value (0).<br />
<br />
In addition, there is a ''Attenuation Response'' slider for all 3 options, which will act in the same way as described in the [[#Attenuation_and_selectivity_in_contrast_changes|section on the attenuation of the Contrast module]].<br />
<br />
=== Whole chroma range ===<br />
<br />
If you choose this option, the entire chroma range in the image is changed, regardless of how saturated each color is already.<br />
<br />
The same observation as for contrast applies here: for there to be changes in color, there must be a pre-existing color variation in the level. If a level has a uniform color, the slider will have no effect.<br />
<br />
The modifications at each level are limited to the range ''[-100,+100]'' : the value ''-100'' is the equivalent of completely desaturating the level, while the value ''+100'' increases the chroma of each detail. This method almost always introduces artifacts because the formula that is applied to the color value for each detail does not take into account whether there are any deviations from the initial value.<br />
<br />
<div><ul class="leftalign"> <br />
<li class="RPgallery"> [[File:wavelet_contrast_15C+_H3S6.jpg|thumb|none|400px|Image with the contrast modifications applied and the overall intensity of the wavelets at ''100%''.]] </li><br />
<li class="RPgallery"> [[File:wavelet_chrom_WC_full.jpg|thumb|none|400px|Effect on the ''Whole chroma range'' with the sliders of the 5 levels at ''+100'': even on downsized images you can see the color artifacts (this behaviour is expected because the effect has been applied to the maximum).]] </li><br />
<li class="RPgallery"> [[File:wavelet_chrom_WC_L1L2full.jpg|thumb|none|400px|After applying the maximum effect on levels ''1'' and ''2'': at this size there is hardly any change (remember that we are only modifying the finest details).]] </li><br />
<li class="RPgallery"> [[File:wavelet_chrom_WC_detail.jpg|thumb|none|400px|Detail with 400% zoom (8 times larger than the preceeding images): at the top, with the color modification applied, artifacts can be seen especially on the edges of the stamens, but hardly any change in the texture of the petal.]] </li><br />
</ul></div><br />
<br />
The above examples mean that you should only make subtle changes with this option because depending on the level and the strength of the change, it is very easy to introduce highly visible artifacts. However, if the changes are too subtle, they will hardly be noticeable. In all cases the chroma noise will be affected and will increase significantly.<br />
<br />
=== Saturated/pastel ===<br />
<br />
With this option, the color changes in each level are focused on the saturated tones of levels with finer details and on the pastel tones of the other levels (with coarser details).<br />
<br />
After selecting this option, a threhold slider and two threshold curves will appear, which operate in the same way as the contrast threshold curves above.<br />
* '''Saturation/pastel threshold'''<br />
** with this control you decide from which level to switch from saturated to pastel tones<br />
** the default value is ''5'', i.e. in the first 5 levels the saturated tones will be changed, and in the higher levels the pastel tones will be changed<br />
** please note that if this value is higher than the number of levels of the wavelet decomposition, only the saturated tones will be changed<br />
** on the other hand, if you choose ''1'' (the level with only the finest details), it is as if you only modify the pastel tones<br />
* '''Pastel chroma range''':<br />
** the threshold curve is the same as for the contrast. The points define the saturation level for which a change in color will be effective <div style="overflow: hidden">[[File:wavelet_chrom_pastel.jpg|left]]</div><br />
** ''it should be noted that the dark area of the gradient corresponds to the pastel tones and the lighter area corresponds to the saturated tones (following [https://en.wikipedia.org/wiki/Colorfulness this explanation of saturation])''<br />
** hovering the mouse over it, you can see the limits: by default the values presented are ''Bottom-Left: 0, Top-Left: 2, Top-Right: 20, Bottom-Right: 30''.<br />
** changes to the curve are made in a similar way to those made to the contrast curves<br />
* '''Saturated chroma range'''<br />
** hovering the mouse over it, you will see where the limits are: by default the values shown are ''Bottom-Left: 30, Top-Left: 45, Top-Right: 100, Bottom-Right: 130'' <div style="overflow: hidden">[[File:wavelet_chrom_chrom.jpg|left]]</div><br />
** although the values of both curves do not overlap, you can see an overlap on the graphical interface. And in practice it seems that changes around the threshold level affect both the saturated and pastel tones. To be able to see clearly whether there is an effect or not (depending on whether the tone is pastel or saturated), it is necessary to use very saturated or very ''desaturated'' (pastel) values.<br />
<br />
Nonetheless, as with the ''Whole chroma range'' option, the changes are not noticeable unless you are willing to introduce fairly visible artifacts.<br />
<br />
<div><ul class="leftalign"><br />
<li class="RPgallery">[[File:wavelet_contrast_15C+_H3S6.jpg|thumb|none|400px|Image with contrast modifications applied and overall wavelet strength at 100%.]]</li><br />
<li class="RPgallery">[[File:wavelet_chrom_WC_L1L2full.jpg|thumb|none|400px|After applying maximum effect on levels ''1'' and ''2''.]]</li><br />
<li class="RPgallery">[[File:wavelet_chrom_SP_L1L2full_L3_60.jpg|thumb|none|400px|Applying modifications in saturated and pastel tones independently. '''''Saturation/pastel threshold''''' in level ''3''. Maximum effect on levels ''1'' and ''2'', while it stays at ''60'' on level ''3''. The rest in ''0''.]]</li><br />
<li class="RPgallery">[[File:wavelet_contrast_15C+_H3S6.jpg|thumb|none|400px|Once more the image with the contrast modifications applied and the overall strength of the wavelets at 100% (to be compared with the modified pastel and saturated tones.]]</li><br />
</ul></div><br />
<br />
As you can see, despite applying 100% changes in some levels, the differences are subtle and may appear to be negligible if you don't look closely. The most visible changes are the more intensely colored «veins» in the petals.<br />
<br />
=== Link contrast levels ===<br />
<br />
This option is an interesting one because the changes in chroma are directly related to those made to each of the contrast levels.<br />
<br />
The ratio between the changes in contrast and color is adjusted with the '''''Chroma-contrast link strength''''' slider: thus ''0'' will have no effect on chroma, while ''100'' will provide the maximum effect, and is more intense than for the ''Whole chroma range'' option (particularly noticeable in ''chroma noise'').<br />
<br />
Keep in mind that if you apply strong changes to the contrast levels, they will also appear in the chroma and will most likely generate undesirable artifacts: your best ally will always be the '''''Chroma-contrast link strength''''' control, to achieve clearly visible effects without producing artifacts that will ruin the photo.<br />
<br />
=== Example (changing chroma) ===<br />
<br />
<div><ul class="leftalign"> <br />
<li class="RPgallery"> [[File:wavelet_chrom_Link_100.jpg|thumb|none|400px|Color linked to changes in contrast. ''Chroma-contrast link strength'' in ''100''. Image absolutely degraded by artifacts (as expected): halos and color noise in the background.]] </li><br />
<li class="RPgallery"> [[File:wavelet_chrom_Link_50.jpg|thumb|none|400px|In this case the ''Chroma-contrast link strength'' is ''50''. It's not subtle, but it's controllable.]] </li><br />
<li class="RPgallery"> [[File:wavelet_chrom_Link_50_Str50.jpg|thumb|none|400px|The same strength as the previous picture, but with the overall strength of the wavelet at 50%.]] </li><br />
<li class="RPgallery"> [[File:wavelet_contrast_15C+_H3S6_Str50.jpg|thumb|none|400px|Reference image with contrast modifications applied and overall wavelet strength at 50%.]] </li><br />
</ul></div><br />
<br />
The modifications to the original image have been exaggerated so that the results are clearly visible. Consequently, the contrast and color modifications made to the last photo have introduced blue edges on the petals, halos around the anthers of the stamens and a noisy background. Despite this, the image is not a complete disaster given how aggressive the modifications are. At this point it is worth noting the intensity of the color in the «veins» of the petals.<br />
<br />
== Gamut module ==<br />
<br />
This module is linked to the [[#Contrast_module|Contrast]] and [[#Chroma_module|Chroma]] modules, so that adjustments can be targeted as a function of the chroma in the details. In other words, for the details in each of the wavelet levels, you can not only take into account the contrast of the luminance (contrast module) or the contrast of the tones (chroma module), you can also choose the color range that these modifications will be applied to.<br />
<br />
=== Reduce artifacts in blue sky ===<br />
<br />
Digital images often have speckled noise in the blue colors of the sky. Wavelet processing can accentuate this noise or generate small artifacts because it increases local contrast.<br />
<br />
This checkbox introduces a [https://en.wikipedia.org/wiki/Median_filter median filter] to reduce these artifacts, at the expense of loss of detail and generation of artifacts in areas where there are changes in tone or which have high contrast. Although useful for fast and undemanding processing, you will actually achieve better results with a judicious combination of the ''[[Noise Reduction]]'' tool in the Detail tab and the ''[[#Denoise_and_Refine_module|Denoise and Refine module]]'' in this tool.<br />
<br />
<div><ul class="leftalign"> <br />
<li class="RPside2side"> [[File:wavelets_gamut_nosky.jpg|thumb|none|600px|Original image with speckles in the blue sky.]] </li><br />
<li class="RPside2side"> [[File:wavelets_gamut_sky.jpg|thumb|none|600px|Artifacts generated by applying ''Reduce artifacts in blue sky'': you can see extra ''detail'' at the intersections of the lines and loss of contrast in the thinnest lines.]] </li><br />
</ul></div><br />
<br />
=== Skin hue ===<br />
<br />
Although the title refers to ''skin hues'', the adjustment is not restricted to these and you can specify the range of tones you want to modify. The selected range will govern the changes made by the other controls in the module. However, the default range is for the usual skin tones.<br />
<br />
For the examples that follow, the following (rather restrictive) range of red tones has been chosen:<br />
<br />
[[File:wavelets_gamut_skin_hue.jpg|frame|none|class=heroed|Color range selected for the following examples. A narrow range of reds has been selected to clearly differentiate the changes.]]<br />
<br />
=== Skin targetting/protection ===<br />
<br />
This allows you to modify the contrast and/or color of details that have colors included in the above range:<br />
* with the slider at ''0'' all the colors of the image are modified equally<br />
* selecting ''-100'' (sliding left) centers the contrast and color changes '''in the selected color range'''<br />
* on the contrary, if you select ''100'' (by sliding right) the colors that '''do not''' coincide with the selected range will be modified<br />
<br />
In the intermediate positions between ''0'' and ''±100'' the changes increase progressively towards either the chosen range, or towards the rest of the colors.<br />
<br />
<div><ul class="leftalign"> <br />
<li class="RPgallery"> [[File:wavelets_gamut_skin.jpg|thumb|none|400px|Original image. <span style="font-size: 0.8em; font-style: italic;">Courtesy of [https://www.photographyblog.com/reviews/nikon_d850_review/sample_images Photographyblog.com]]] </li><br />
<li class="RPgallery"> [[File:wavelets_gamut_skin_target0.jpg|thumb|none|400px|By applying some fairly radical changes in Contrast and Color, with the slider at ''0''.]] </li><br />
<li class="RPgallery"> [[File:wavelets_gamut_skin_target-100.jpg|thumb|none|400px|In this case the position is ''-100'': the contrast and color changes are centered on the range of reds.]] </li><br />
<li class="RPgallery"> [[File:wavelets_gamut_skin_target+100.jpg|thumb|none|400px|When the position is at ''100'', changes apply to colors that '''are not red'''.]] </li><br />
</ul></div><br />
<br />
=== Curve ===<br />
<br />
Once you've set the desired ''Skin targetting/protection'', you can use this graph to fine tune the contrast/chromaticity variation for each color: moving a control point up will increase the variation for that color, while moving it down will mitigate the changes for that particular color (although it won't eliminate the effect entirely).<br />
<br />
However, only those colors within the range selected above will be taken into account regardless of the colors modified with the curve.<br />
<br />
<div><ul class="leftalign"> <br />
<li class="RPside2side"> [[File:wavelets_gamut_curve_target100.jpg|thumb|none|400px|According to the attached curve, the intention is to highlight the green colors as much as possible, while leaving all the others in the background. The consequence is that the green ticket is the most highlighted of all the objects.]] </li><br />
<li class="RPside2side"> [[File:wavelets_gamut_curve.jpg|thumb|none|250px|The curve in which changes have been mitigated for all colors except green, which has been maximized.]] </li><br />
</ul></div><br />
<br />
=== Avoid color shift ===<br />
<br />
Processing by Wavelet Levels can introduce significant hue changes, especially near the limits of the color range of the [[Color_Management#Working_Profile|working color space]]. Activating this option makes a series of corrections to ensure that the resulting hue is related to the initial color.<br />
<br />
== Toning module ==<br />
<br />
This module can be used for color toning specific detail levels as required.<br />
<br />
However, it is not possible to act directly and accurately on the hue in each individual level because the components ''a*'' and ''b*'' have been decomposed and it is very difficult to create a precise mathematical relationship between the selected hue and the decomposed components.<br />
<br />
Still, you can control to some extent which hues will be modified and decide which color dominants they will take.<br />
<br />
As with the other modules, there is an ''Attenuation Response'' slider, which will act in the same way as described in the [[#Attenuation_and_selectivity_in_contrast_changes|chapter on the attenuation in the Contrast module]].<br />
<br />
=== Excluded Colors ===<br />
<br />
<br />
The '''''Excluded Colors''''' graph is based on the color distribution of the chromatic coordinates used for the L*a*b* color space: the horizontal axis represents the a* component (going from green to red) and the vertical axis represents the b* component (going from blue to yellow).<br />
<br />
However, because it is complicated to represent the actual L*a*b* space color distribution in two dimensions, the pastel shades as shown in the interface, while being mathematically accurate, are not visually intuitive, especially when selecting yellow tones. Perceptually they are equivalent to a graph such as the one below:<br />
<br />
[[File:Cielab 8x8.jpg|thumb|450px|center|'''Approximate''' representation of the color tone distribution in the CIEL*a*b* space.]]<br />
<br />
In the center of the graph there is a white dot which, when dragged, will produce a second black dot. These two dots define the centers of the color ranges that will be protected to a greater or lesser extent by any toning adjustments subsequently carried out in this module. Putting the white dot on a particular color on the graph defines the center of the first color range. Similarly, the position of the black dot defines the center of the second color range. If the black dot is not moved from the initial position at the center, then the second range is ignored.<br />
<br />
With the slider '''''Range a and b %''''' a zone of influence is created around the center as defined by the position of the dot on the graph and the slider % determines how large the zone will be. <br />
<br />
With the '''''Protection''''' slider, the effect of any adjustments on the selected colors is reduced in the zone of influence (center plus range). The protection slider value corresponds to the % of the protection effect and will decrease as you move away from the center, until at the end of the range (at the periphery of the zone of influence) the reduction is equivalent to half the established value.<br />
<br />
For example: ''Protection=80'' means that the protection is 80% and therefore the center of each range will only receive 20% of the toning values set in the equalizer modules (explained below). As we move away from the center and until we reach the limit set by ''Range a and b %'', the toning will become progressively more intense until it reaches a maximum of half of the ''Protection'' value. In this case it would be 40 meaning that the colors on the periphery would undergo 60% of the set value.<br />
<br />
=== Toning controls ===<br />
<br />
In this group of controls, two curves are presented:<br />
* the '''''Opacity Red-Green''''' (the ''a*-curve'') which acts on the red-green tones<br />
* the '''''Opacity Blue-Yellow''''' (the ''b*-curve'') which acts on the blue-yellow tones<br />
<br />
But don't forget that the final colors of the photo will be a combination of the tones of these two curves. For example: if you modify the ''a*'' curve ('''''Red-Green Opacity''''') to red, all the tones of the level you are modifying will take on a red/reddish tone, but will not necessarily become red (if they also had a strong blue component, they would turn towards magenta/violet).<br />
<br />
From a practical point of view: a tone can become more or less saturated up ''to a certain limit'' and at the same time undergo a change in hue. To better visualize these effects, take a look at this [https://upload.wikimedia.org/wikipedia/commons/0/06/CIELAB_color_space_top_view.png view from above the ''L*a*b* color space''], with ''b*'' as the vertical axis and ''a*'' as the horizontal axis. And don't miss this [https://upload.wikimedia.org/wikipedia/commons/7/7d/CIELAB_color_space_front_view.png front view of the ''L*a*b* color space'']. The bottom of the top view matches the front of the front view.<br />
<br />
In the interface you will find two ''curve types:'' ''Linear'' ([[File:wavelet_toning_linear.jpg|frameless|text-bottom]]) and ''Equalizer'' ([[File:wavelet_toning_curve.jpg|frameless|text-bottom]]). To choose between one or the other, click on the small triangle on the right.<br />
<br />
The ''linear'' curve cancels the effect of the axis to which it refers: if you select it in the '''''Red-Green Opacity''''', you will not perform any action on those tones. Similarly with the '''''Blue-Yellow Opacity'''''.<br />
<br />
In each ''equalizer''curve there is a horizontal axis (or ''x'' axis) and a vertical axis (or ''y'' axis):<br />
* the ''x'' axis represents the 10 possible levels, in ascending order from left to right and evenly distributed<br />
* the ''y'' axis represents the intensity of the modification: when the curve rises above or falls below the mid-line the color is modified towards one end or the other of the axis of the component being modified (''a*'' or ''b*'')<br />
* in the '''''Red-Green Opacity''''' (the ''a*-curve''), moving the curve upward introduces a reddish tint, while moving it downward introduces a greenish tint<br />
* in the '''''Blue-Yellow Opacity''''' (the ''b*-curve''), moving the curve upward introduces a yellow tint, while moving it downward introduces a bluish tint<br />
<br />
By default, the curve is flat and lies on the mid-line. To get an idea of how you can interact with the curve, see the explanations of the ''[[Exposure#Tone_Curves|Tone Curves]]''. And remember that if you don't like the changes you have made to the curve, you can always start over by clicking the reset arrow [[File:ResetButton.png]].<br />
<br />
As long as there are variations in contrast in the original image color, these curves will allow you to selectively vary the tone of the desired details. The resulting changes depend on where you place the points in the curve and the amplitude of the modification (i.e. the number of levels it affects). Everything has to be done «by eye», as there is no reference to the levels on the ''x'' axis, however you can see the effect of the modification by looking at the preview.<br />
<br />
If you use less than 10 levels, the points affecting the rightmost levels will simply be ignored: if you are modifying an image with 4 levels, the rightmost 6 (the ones with the largest details) will be ignored.<br />
<br />
=== Example (applying toning) ===<br />
<br />
You will recall that we had some ugly blue halos around parts of the flower, so let's try to eliminate them (or at least hide them) with the toning controls. We take advantage of the fact that most of the image has a red dominant so we can modify the blue component, without it being too noticeable in the overall result. For this example, none of the colors have been excluded:<br />
<br />
<div><ul class="leftalign"> <br />
<li class="RP3inarow"> [[File:wavelet_chrom_Link_50_Str50.jpg|thumb|none|380px|The image as it was after the changes in the Chroma module, with the overall strength at 50%.]] </li><br />
<li class="RP3inarow"> [[File:wavelet_toning_opBYfull.jpg|thumb|none|380px|By applying a maximum tonal change on the ''Blue-Yellow'' curve: see how yellow halos have been generated where they were previously blue.]] </li><br />
<li class="RP3inarow"> [[File:wavelet_toning_opBYfull_curve.jpg|thumb|none|280px|The applied curve, which mainly affects levels ''3'' and ''4'' and to a lesser extent level ''5''.]] </li><br />
</ul></div><br />
<br />
<div><ul class="leftalign"> <br />
<li class="RP3inarow"> [[File:wavelet_toning_opBY.jpg|thumb|none|380px|A moderate change of tone in the ''Blue-Yellow'' curve to eliminate blue halos as much as possible.]] </li><br />
<li class="RP3inarow"> [[File:wavelet_toning_opBY_Str50.jpg|thumb|none|380px|The same change as in the previous image, but with the overall wavelet strength at 50%.]] </li><br />
<li class="RP3inarow"> [[File:wavelet_toning_opBY_curve.jpg|thumb|none|280px|The applied curve, which affects more or less the same levels as before, but with lower intensity.]] </li><br />
</ul></div><br />
<br />
There are still some traces of blue halos in the final result although they are not as visible, and the overall appearance of the photo seems to be the same.<br />
<br />
== Denoise and Refine module ==<br />
<br />
This module complements the general '''[[Noise_Reduction|Noise Reduction]]''' tool (in the ''Detail tab'') and '''Edge Sharpness''' (explained in the next section).<br />
<br />
Noise management is a complex issue because decisions have to be made as to where should it be done in the processing pipeline (e.g. at the beginning or at the end), what should be done and how.<br />
<br />
In RawTherapee the general noise reduction tool is placed at the beginning of the processing pipeline to prevent subsequent tools from enhancing the noise to unacceptable levels. In the ''Noise Reduction'' tool in the Detail tab you have the following possibilities:<br />
* process the luminance (also based on wavelets) as a block, i.e. with no distinction between the wavelet levels<br />
* process the color noise using a different method: this generally requires a higher number of wavelet levels (4 to 7) and more complex processing<br />
* add ''Fourier Transform'' processing to refine the luminosity<br />
* add a median filter<br />
<br />
Although this may be sufficient, use of the Wavelet Levels tool can provide some additional benefits (even though it uses the same algorithm as the general tool):<br />
* it is at the end of the processing pipeline, thus reducing the impact of noise added by other general tools (''Exposure'', ''Curves'', ''Dynamic Range'', etc.)<br />
* it acts separately and independently on each of the first 4 levels, whereas the ''standard'' noise reduction has an effect on the entire image. This is especially useful for low noise images and for images where the general tool has been used sparingly to preserve detail (i.e. to reduce rather than to eliminate the noise)<br />
* it reduces the incidence of noise in the other wavelet processing modules, e.g. allowing you to process skies without exaggerating the noise<br />
* it adjusts both noise processing and the degree of contrast amplification/reduction at each level, which is useful for example for astronomical images<br />
<br />
=== The controls ===<br />
<br />
You can adjust the noise reduction by levels as required with the following set of controls, which not only decide what noise to act on, but also link its effect to the ''Edge Sharpness'' module and the chroma denoise.<br />
<br />
==== Link with Edge Sharpness' Strength ====<br />
<br />
This option will modify the behavior of the lower slider of each level (explained below).<br />
* if you choose '''not to activate it''', then the lower slider of each level (the '''Strength''' slider) will have a similar effect to the Contrast module when it is used over the ''Whole luminance range''<br />
* if you activate it, you can change the distribution of the sharpness improvement in the first levels with the lower slider (this is explained in more detail in the next module, ''Edge Sharpness'')<br />
<br />
==== Denoise equalizer White-Black ====<br />
<br />
Human vision is able to distinguish noise more easily in light areas than in dark areas, even when there is more noise in the dark areas (the shadows).<br />
<br />
With this slider, noise reduction can be increased either in the shadows (with values to the right) or in the highlights (with values to the left).<br />
<br />
It is easier to adjust if you choose an area with both light and dark areas, so that you can see the difference between the noise levels in the shadows and in the highlights.<br />
<br />
==== Denoise and Strength ====<br />
<br />
These sliders are used to control noise in the 4 finer-detail levels of the image:<br />
* the upper slider of each level performs the '''Denoise'''.<br />
* the lower one, called '''Strength''', modifies the contrast of the details for that particular level. It should be noted that this adjustment isn't as sophisticated as the adjustments made in the Contrast module<br />
<br />
Although the ''Strength'' slider may seem redundant, it is quite useful for recovering lost contrast in the details when higher values of ''Denoise'' have been applied. That way you don't have to jump from one module to another to quickly adjust the image. It also serves to modulate the distribution of the effect on the first 4 levels of the ''Edge Sharpness''.<br />
<br />
==== Denoise chrominance ====<br />
<br />
The chroma denoise is complementary to the ''Noise Reduction'' tool in the Detail tab. <br />
<br />
Because the wavelet chrominance denoise is at the end of the processing pipeline, it is useful for removing any chrominance noise that wasn't removed when using the noise reduction in the Detail tab, or noise that has been generated by other tools.<br />
<br />
In this group of sliders you will find:<br />
* the '''Denoise Equalizer Blue-Red''': chrominance noise usually comes in the form of red or blue dots and with this slider you can increase the reduction of the blue dots (to the left), or the red dots (to the right)<br />
* the '''Chrominance Fine''' slider: reduces the chrominance noise in the finest details, i.e. at the lowest levels<br />
* the '''Chrominance Coarse''' slider: reduces the chrominance noise in the coarser details, i.e. at the higher levels. This noise can be seen as patches of color that appear to be «dirty» or «do not belong» to the image and that cannot be removed with the ''Chrominance Fine'' slider because of their size<br />
<br />
=== Example (applying denoise) ===<br />
<br />
To get a better understanding of the extent to which the noise levels can be improved, it is useful to proceed on a level-by-level basis, taking advantage of the fact that you can view the detail in each individual level on a neutral background (as explained when dealing with the ''[[#The_preview|Preview]]''). Turn off ''Link with Edge Sharpness' Strength'' and then increase the ''Strength'' slider of the level you are working on to the maximum: the noise will become obvious and you will be able to assess how much denoise is needed. Once you have adjusted the ''Denoise'' slider, move the ''Strength'' slider to the value that suits you best (negative values can also be used) and move to the next level.<br />
<br />
<div><ul class="leftalign"> <br />
<li class="RPgallery"> [[File:wavelet_denoise_orig.jpg|thumb|none|400px|The original image, enlarged to 300%.]] </li><br />
<li class="RPgallery"> [[File:wavelet_denoise_L2d00s100.jpg|thumb|none|400px|The details of ''level 2'', with ''strength: 100'', without denoise. The noise is clearly visible.]] </li><br />
<li class="RPgallery"> [[File:wavelet_denoise_L2d30s100.jpg|thumb|none|400px|The same ''level 2'' with denoise applied (''30''). Don't forget that the ''Strength'' is still at ''100''.]] </li><br />
<li class="RPgallery"> [[File:wavelet_denoise_L2d30s27.jpg|thumb|none|400px|The level with denoise applied and ''Strength'' reduced to ''27''.]] </li><br />
</ul></div><br />
<br />
<div><ul class="leftalign"> <br />
<li class="RPgallery"> [[File:wavelet_denoise_L1d00s00.jpg|thumb|none|400px|''Level 1'' details.]] </li><br />
<li class="RPgallery"> [[File:wavelet_denoise_L1d00s100.jpg|thumb|none|400px|The details of ''level 1'' with ''Strength: 100''.]] </li><br />
<li class="RPgallery"> [[File:wavelet_denoise_L1d12s100.jpg|thumb|none|400px|After applying a slight noise reduction (''Denoise: 12'') and with the ''Strength'' still at ''100''.]] </li><br />
<li class="RPgallery"> [[File:wavelet_denoise_L1d12s-17.jpg|thumb|none|400px|The final effect of noise reduction, after having lowered the ''Strength'' to ''-17'' (a negative value to lower the initial contrast of the details).]] </li><br />
</ul></div><br />
<br />
<div><ul class="leftalign"> <br />
<li class="RPgallery"> [[File:wavelet_denoise_orig.jpg|thumb|none|400px|The original image, enlarged to 300%.]] </li><br />
<li class="RPgallery"> [[File:wavelet_denoise_final.jpg|thumb|none|400px|The final image, enlarged to 300%.]] </li><br />
<li class="RPgallery"> [[File:wavelet_denoise_orig100.jpg|thumb|none|400px|A more general view of the image, without denoise. Size at 100%.]] </li><br />
<li class="RPgallery"> [[File:wavelet_denoise_final100.jpg|thumb|none|400px|The same view as above, with denoise applied: you can see the reduction of noise in the stone and a slight increase in sharpness in the window.]] </li><br />
</ul></div><br />
<br />
As a general rule, it is best not to eliminate the noise completely, but simply reduce it so that it is only just visible and at the same time, increase the contrast of the details in that particular level. By amplifying the presence of the details, the noise will be ignored when the image is viewed and the photo will have a light textured look. The procedure is as follows:<br />
# reduce the luminance noise slightly using the ''Noise Reduction'' tool in the detail tab, taking special care not to lose any detail<br />
# select ''one level'', ''gray background'' and ''level 1''<br />
# zoom in to 300-400% on an area with poor background detail (there must be enough detail with good contrast, but not so much that it masks the noise)<br />
# move the ''level 1 strength'' slider in ''Denoise'' to the maximum (or almost), making sure that the details can still be distinguished from the noise<br />
# move the top slider to a point where the noise reduction is medium-low (do not remove noise completely) and then return the lower strength slider back to its original position.<br />
# the noise reduction adjustment will result in a loss of contrast in the details. To remedy this, increase the lower slider to a strength level that allows you to recover the initial contrast of the details<br />
# switch to ''level 2'' and continue with points 4, 5 and 6, this time adjusting the ''strength'' of ''level 2''<br />
# continue in the same way with levels ''3'' and ''4''<br />
# finish the process by selecting ''All levels in all directions''<br />
<br />
If the image is not very noisy, you can go straight to step 2. However, if the image is very noisy, it is important to adjust the luminance noise reduction at step 1: you need to play with the ''Luminance'' denoise slider and the ''Gamma'' slider (in the Noise Reduction tool), to direct the noise reduction to the shadows or the highlights. The more care you take with this step, the better the final result.<br />
<br />
To increase the presence of detail you can use the lower sliders and increase the strength of each level as much as you like, but it is preferable to use the sliders in the Contrast module, as they offer more control and give better results with fewer artifacts. Also, don't forget that in this example only the ''Denoise'' and ''Strength'' sliders have been used, but the result can be further refined if necessary with the other sliders in this module.<br />
<br />
Do not confuse the denoise in this module with the '''Threshold low (noise)''' function used for '''Edge detection''' in the ''Edge Sharpness'' module, which takes noise into account (without reducing it) to avoid highlighting it when analyzing the edges<br />
<br />
== Edge Sharpness module ==<br />
<br />
This module applies a form of contour detection on the details in each of the wavelet levels.<br />
<br />
At first glance it looks like an '''[[Sharpening#Unsharp_Mask|Unsharp Mask]]''', because decomposition by wavelet levels generates a ''residual image'' that looks a bit like a mask, but that's where the similarities end.<br />
<br />
If you want results that are similar to the ''Unsharp Mask'' or ''[https://en.wikipedia.org/wiki/Deconvolution#Optics_and_other_imaging Deconvolution]'', then you will need to select the ''Edge detection'' box and choose a high value of ''Gradient sensitivity'' (70 or more; by default it will be 90). It is better not to modify the first contrast levels in ''Contrast by Detail Levels'', because they can impair the way the algorithm works (all of these options are explained in detail below).<br />
<br />
Before explaining how to use the module, keep in mind the following to avoid generating excessively strong artifacts or effects: both the configuration of the ''[[#Edge_performance|Edge performance (D2, D4 ... D14)]]'' and the [[#Denoise_and_Refine_module|strength of each level in ''Denoise and Refine'']] (when you have ''Link with Edge Sharpness' Strength'' activated) have a noticeable effect on ''Edge detection''. Each time you make an adjustment, you need to evaluate the result and readjust everything to obtain good sharpness with the minimum of artifacts.<br />
<br />
In the interface you have several control blocks:<br />
* '''''settings''''': this first block allows you to adjust the way the tool detects the edges<br />
* '''''local contrast''''': in this block you can decide how contrast changes are applied to the details based on their initial contrast values. <br />
* '''''edge detection''''': to increase sharpness where it is needed most (i.e. at the edges)<br />
<br />
=== Configuration ===<br />
<br />
'''''For the time being do not enable ''Edge detection'', as the results will be different if this option is activated.'''''<br />
<br />
There are 4 sliders:<br />
# '''Strength''': is the amount of contrast enhancement applied to the details. The higher the ''Strength'' value, the greater the change in contrast. Its effect is stronger at finer levels and resetting this slider cancels out any changes in the rest of the module.<br />
# '''Attenuation Response''': this operates in the same way as the attenuation control described in the [[#Attenuation_and_selectivity_in_contrast_changes|chapter covering the attenuation of the Contrast module]]. It controls the extent to which the contrast values will be modified.<br />
# '''Radius''': generates a three-dimensional image effect and may give the impression of more ''volume'' in the details, or more pronounced ''texture'' and has an influence even if the slider is set to zero. It should also be noted that the effect of the ''Radius'' is modified by the value of the ''Detail''. <br />
# '''Detail''' : changes the way the contrast is distributed between the levels. The effect will be stronger in the first 3 levels if the cursor is moved to the right, whereas if you move it to the left (towards negative values), the contrast changes in the first 3 levels will be practically canceled out.<br />
<br />
The following example allows you to see how closely the changes in contrast in each of the levels are related to the values of the ''Radius'' and the ''Detail'' sliders, and how the effects of the ''Radius'' slider are modified according to the value of the ''Detail'' slider. To illustrate this we set ''First level: Unchanged'' (which will be explained later) and ''Link with Edge Sharpness' Strength'' disabled (in the ''Denoise and Refine'' module).<br />
* '''the Radius-Contrast ratio''': changing the value of the ''Radius'' modifies the contrast of the details. In general, the strongest contrast changes are observed between radii 40 and 75. Below 40, level 1 is enhanced and above 75, level 3 and to a lesser extent the higher levels (the effect becomes increasingly softer the higher the level and at levels ''9'' and ''Extra'' the effect is negligible).<br />
* '''Radius-Detail relationship''': depending on the value of ''Detail'', modifying the ''Radius'' increases, more or less, the contrast of details in one level or another.<br />
<br />
The following is a summary of the main points. The graphical representation makes it easier to understand:<br />
<br />
<div><ul class="leftalign"> <br />
<li class="RP3inarow"> [[File:Wavelet_edge_sharpening_D-50.png|thumb|none|450px|Variation of the contrast of the first three levels as the value of the ''Radius'' increases, but with '''''Detail: -50'''''. In this case, except for the ''Radius: 60'', the contrast is practically unchanged. However, levels 4 and above have stronger contrast values.]] </li><br />
<li class="RP3inarow"> [[File:Wavelet_edge_sharpening_unchanged.png|thumb|none|450px|With '''''Detail: 10''''' (the default value) and with radii below 40, ''level 1'' has the strongest increase, while above 75 the increase is much less significant. As the ''Radius'' increases, levels 4 and above undergo only a moderate increase in contrast]] </li><br />
<li class="RP3inarow"> [[File:Wavelet_edge_sharpening_D100.png|thumb|none|450px|When you choose '''''Detail: 100''''', ''level 2'' has the most visible effect for almost all radii. With this value of ''Detail'', contrast is increased, albeit subtly, for levels 4 and above as the ''Radius'' increases.]] </li><br />
</ul></div><br />
<br />
Just under the ''Detail'' control, you have a drop-down list with 3 options for the '''First (wavelet) level''':<br />
* ''Reinforced'': the effect is increased at ''level 1''.<br />
* ''Unchanged'': the distribution of the algorithm is unchanged.<br />
* ''Reduced'': the modification is reduced for ''level 1''.<br />
<br />
Being able to see the differences between these three options will depend on the amount of fine detail in the image, how much contrast there is in the details and the choice of coefficients used for the decomposition (''D2'', ''D4'', ..., ''D14''): in night photos with overexposed points of light (e.g. streetlamps etc.) the ''Reduced'' option will soften any high-contrast noise in the first level. Often however, there are hardly any relevant details in ''level 1'' so the option you choose will probably not be important.<br />
<br />
In addition, if you use the option ''Reduced'', you may see a somewhat strange or at least «different» behavior for ''level 1'': the contrast decreases progressively from a maximum at ''Radius: 0'' to an almost total blurring of the details at ''Radius: 19'' and then jumps to another maximum at ''Radius: 20''. It then slowly reduces back to ''Radius:100''. Graphically:<br />
<br />
[[File:Wavelet_edge_sharpening_reduced.png|thumb|450px|center|Variation of the contrasts in the levels from ''1'' to ''3'', as the ''Radius'' increases. Look at the changes in ''level 1'', especially around ''Radius: 20''. The '''''First level: Reduced'''''.]]<br />
<br />
The best thing to do is to choose ''Unchanged'', because with the option ''Link to Edge Sharpness' Strength'' the changes will be more progressive and controllable.<br />
<br />
=== Link to Edge Sharpness' Strength ===<br />
<br />
All of the above is valid as long as you do NOT activate the option ''Link to Edge Sharpness' Strength'' (in ''Denoise and Refine''). Not activating it means that contrast changes will be made depending on the values of ''Radius'' and ''Detail''.<br />
<br />
However, if you have activated the option ''Link to Edge Sharpness' Strength'', the strength settings for each ''Denoise'' level will regulate the strength of the effect in each of the first four levels of ''Edge Sharpness''. This allows you to adjust the sharpness for certain levels only and use significantly higher increases in contrast than can be obtained with the 10 ''Contrast'' sliders.<br />
<br />
For example, you can:<br />
* leave ''level 1'' contrast unchanged<br />
* increase the maximum strength in ''level 2''<br />
* reduce contrast in ''level 4'' (negative ''Strength'')<br />
<br />
=== Local contrast ===<br />
<br />
For each level of decomposition, the tool calculates the [https://en.wikipedia.org/wiki/Mean mean] and [https://en.wikipedia.org/wiki/Standard_deviation standard deviation] of the internal contrast of the details (also called ''local contrast'') and then uses the results for subsequent modifications.<br />
<br />
Remember that a «detail» is actually a group of pixels in the original image. The higher the wavelet level, the larger the group (at ''level 1'' a group consists of 2x2=4 pixels, at ''level 2'' 4x4=16 pixels, etc). Because each pixel has a different initial luminance from the rest of the pixels in the detail, the tool can derive and analyze the internal contrast between pixels.<br />
<br />
Any modification to these internal or local contrast values is based on a pattern (or curve) derived from the mean of the local contrast values in the level and on their standard deviation. It is applied to the local contrast values in the same way in each of the levels. i.e. centered around the mean contrast values.<br />
<br />
So, for example, you can:<br />
* for low initial contrast values (usually located in the shadows): reduce local contrast to soften the detail<br />
* for average values: enhance them by increasing the local contrast<br />
* for high values (usually located in very bright areas): reduce or even remove the local contrast, to avoid ''clipping'' the highlights<br />
<br />
You can choose between two graphical controls for setting the parameters:<br />
# a threshold curve with four movable points that represent (from left to right) the minimum contrast, the mean, the average + standard deviation and the maximum contrast<br />
# a curve, which by default is an asymmetrical Gaussian type curve, with the following characteristics<br />
#* the center of the [https://en.wikipedia.org/wiki/Cartesian_coordinate_system abscissa] corresponds to the mean value of the contrast values<br />
#* the area from the center covering one-third of the width of the graph on each side are the details with contrast values that are either higher or lower than the average value and lie within the range of values set by the standard deviation<br />
<br />
'''''THE CURVE WITH SLIDERS'''''<br />
<div class="parrpad">[[File:wavelet_local_contrast_thresholds.jpg|left]]</div><br />
<br />
If you choose the threshold curve, moving a point to the right will increase its contrast, while moving it to the left will decrease it (the whiter the background color, the higher the contrast, whereas a dark background indicates low contrast).<br />
<br />
As indicated above, the points correspond, from left to right, to the minimum contrast, the mean, the mean + the standard deviation and the maximum contrast. For example, moving the point that represents the mean of the contrast values to the right will increase the contrast values close to the mean. Similarly for the other points i.e. the tool modifies each group of contrast values (mean, standard deviation, minimum and maximum) in accordance with the position of the adjustable points.<br />
<br />
In practice:<br />
* Using the default values, the position of the points on the threshold curve usually gives a more ''natural'' look at the expense of exaggerated brightness, and in particular, specular brightness. Details however are enhanced more naturally and with more definition than with the Gaussian curve, without excessively highlighting noise or grain<br />
* in daylight photos, which have a predominance of mid-tones (as in cityscapes), the default settings will highlight details without exaggerating their contrast (however reflections will be more pronounced)<br />
* however, in high contrast photos (night photos with artificial lighting, astronomical photography) the default settings tend to exaggerate the contrast values of bright points of light<br />
* in photos with high contrast (with a lot of contrasting noise): if you have selected ''first level reduced'' the effect on ''level 1'' decreases and the noise is quite smooth. However, in photos with moderate contrasts there is practically no difference<br />
<br />
'''''THE GAUSSIAN CURVE'''''<br />
<div class="parrpad">[[File:wavelet_local_contrast_gauss.jpg|left]]</div><br />
<br />
In this case the shape of the curve serves as a visual guide when modifying the contrast values of the details. Remember that the standard deviation of the contrast values are one third to the right and one third to the left of the center of the graph.<br />
<br />
Compared to the threshold curve, this graph allows you to not only modify the range of local contrast values that will be affected but also the strength of the modification: if you move a point on the curve to the right or left, you will change the range of contrast values that will be affected (as with the slider points), whereas moving it up or down will increase or decrease the strength of the changes in detail.<br />
<br />
With the default curve shape (which you can reset with the [[File:ResetButton.png]] button) the effect achieved is similar to a [https://www.ledet.com/margulis/Makeready/MA69-Life_on_the_Edge.pdf HIRALOAM]: it enhances the contrast values by controlling the shadows, while making strong contrasts less prominent. It is like highlighting the volume of each detail, keeping both noise in the shadows and overexposure in the highlights under control (especially with specular highlights). However, the grain and noise of the medium contrast values are excessively enhanced.<br />
<br />
The threshold curve and the Gaussian curves will give different results with their respective default values, so the choice depends on what you are trying to achieve. However, when using the Gaussian curve the ''Strength'' of the tool should be kept low to avoid overly exaggerated results. With the threshold curve you can use higher strength values and still achieve ''natural'' results. However, you can achieve the same effect by adjusting the Gaussian curve, with the added advantage of being able to vary the contrast values to either increase or reduce them, or even flatten them completely by moving the curve below the horizontal line).<br />
<br />
<div><ul class="leftalign"> <br />
<li class="RP3inarow"> [[File:wavelet_local_contrast_curves_o.jpg|thumb|none|450px|Original image.]] </li><br />
<li class="RP3inarow"> [[File:wavelet_local_contrast_curves_t.jpg|thumb|none|450px|Variation of the local contrast with the sliders: the edges are highlighted in a more natural way.]] </li><br />
<li class="RP3inarow"> [[File:wavelet_local_contrast_curves_g.jpg|thumb|none|450px|Variation of the local contrast with the Gaussian curve: there is a relief effect on the edges]] </li><br />
</ul></div><br />
<br />
=== Edge detection ===<br />
<br />
Before you start using this part of the module you need to adjust the above parameters carefully, especially the local contrast. You should only make subtle changes, as it is easy to generate exaggerated effects and artifacts in the image.<br />
<br />
By activating the edge detection, the result obtained will be different from those of the traditional algorithms (unsharp mask, deconvolution...), as the tool performs a series of operations on the details of each level to highlight the edges without enhancing the noise: it intensifies the details of the decomposition, blurs them to remove the noise and selects those details that are considered to be part of an edge.<br />
<br />
The process is based on the Sobel-Canny algorithm, customized to fit the components of the decomposition and reduce the necessary variables to 3 sliders:<br />
* '''Gradient sensitivity''': the more you move the cursor to the right, the more the detection algorithm will focus on sharp edges and the less it will take into account the local contrast values of small areas (such as noise or small details). Conversely, moving the cursor to the left will detect more edges, even the smallest ones, but it will also highlight noise.<br />
* '''Threshold low (noise)''': this slider configures a [https://en.wikipedia.org/wiki/Gaussian_blur Gaussian filter] that does not directly modify the image, but rather the decomposition coefficients. On the left it acts on a 3x3 matrix, while on the right it acts on a larger 5x5 matrix. By blurring the image, noise and finer or lower contrast details are lost or obscured. This is good for mitigating noise, but it also results in less accurate edge detection. The farther to the right the cursor is, the better the noise will be mitigated, but fewer edges will be detected. A value around 3x3 is better for detecting fine edges, but is more prone to interference from noise. A value of 5x5 is better for wider or more prominent edges, at the cost of losing the finer edges and making detection less accurate.<br />
In addition, in a later step of the algorithm, this threshold will remove those edges that, although detected, are unlikely to be true edges. The lower this threshold is, the more it will detect low-contrast edges. However, it will also be more likely to interpret noise as a probable edge.<br />
* '''Threshold high (detection)''': once the edges of the image have been detected, this slider allows the tool to analyze the reliability of the edge detection (i.e. whether it is a sharp or blurred edge) and then either attenuate or enhance the local contrast changes depending on how sharp the edge is. Moving the cursor to the right will enhance the contrast of the sharp edges and moving it to the left will attenuate it.<br />
<br />
===Enhanced algorithm===<br />
<br />
Activating this part of the module allows you to configure certain aspects of the edge detection algorithm:<br />
* Edge sensitivity: this value allows you to discard details that do not have a higher contrast than the value set by the slider. The more the slider is moved to the right, the higher the contrast in the details must be for them to be considered as a possible edge (lower-contrast edges will be ignored).<br />
* Base amplification: this slider intensifies the initial values before starting the calculations to improve edge detection. The further to the right, the better the distinction between ''edge'' and ''non-edge'', but the greater the risk of artifacts.<br />
* Neighboring pixels: here you decide what influence the pixels surrounding the detail will have on edge detection. You have 3 options: ''None'', ''Low'', ''High''.<br />
<br />
=== Example (modifying noise reduction and edge sharpness) ===<br />
<br />
<div><ul class="leftlalign"> <br />
<li class="RPside2side> [[File:wavelet_pic.jpg|thumb|none|600px|Original image.]] </li><br />
<li class="RPside2side> [[File:wavelet_edge_sharpness.jpg|thumb|none|600px|The image after applying the modules described above, including noise reduction and edge sharpness improvement.]] </li><br />
</ul></div><br />
<br />
== Blur levels module ==<br />
<br />
<br />
This module allows you to selectively blur («defocus») the details of selected levels. The result is stronger in the higher levels (from ''level 7'' upwards) and is especially useful in astrophotography.<br />
<br />
The '''''Attenuation Response''''' slider acts as described in the [[#Attenuation and selectivity in contrast changes|chapter on the attenuation of the Contrast module]].<br />
<br />
The '''''Blur by levels''''' curve modifies the luminance of each level: it is divided into 10 zones, with ''level 1'' on the left and ''Extra'' on the right. Raising the curve in the area of a level will increase the blur for that particular level.<br />
<br />
The '''''Blur Chroma''''' slider blends the colors with their surroundings, creating a subtle smudge effect. It acts on the same levels defined by the previous curve.<br />
<br />
== Sharp-mask and Clarity module ==<br />
<br />
<br />
<br />
The ''Sharp mask'' feature is a new way of enhancing sharpness alongside the other methods available in RawTherapee (i.e. ''Unsharp Mask'', ''Deconvolution'' and ''Wavelet Levels Edge Sharpness''). It can be used in conjunction with them or on its own.<br />
<br />
The ''Unsharp mask'' is the method that has been traditionally used to accentuate edges and increase the impression of sharpness in an image: it is based on the creation of a blurred Gaussian type mask generated by taking each pixel and recursively blurring the neighboring pixels. This mask is then subtracted from the original image to emphasise the edges. The radii used with this method are usually small (in the order of less than 1 to a few pixels).<br />
<br />
The mask in this module is based on part of the wavelet decomposition and can be used in two ways:<br />
* enhancing the finer levels using the '''Sharp mask''' option.<br />
* enhancing the coarser levels using the '''Clarity''' option, which increases the impression of local contrast and local saturation in the image.<br />
<br />
When you activate the module, the general configuration of the tool will automatically change to:<br />
<br />
{| class="RP3c-grid"<br />
|-<br />
! role="columnheader" | <br />
! role="columnheader" data-colh1="Sharp mask" | Sharp mask<br />
! role="columnheader" data-colh2="Clarity" | Clarity<br />
|-<br />
! role="rowheader" | Background:<br />
| data-colh1="Sharp Mask" | Residual Image<br />
| data-colh2="Clarity" | Residual Image<br />
|-<br />
! role="rowheader" | Levels:<br />
| data-colh1="Sharp mask" | Levels with fine details<br />
| data-colh2="Clarity" | Levels with coarse details<br />
|-<br />
! role="rowheader" | Level:<br />
| data-colh1="Sharp mask" | 3<br />
| data-colh2="Clarity" | 7<br />
|}<br />
<br />
In either case you can change the reference ''level''. In the case of the ''Sharp Mask'' the change of level is similar to changing the radius in the ''Unsharp Mask'' and you can choose any level between ''1'' and ''4''. For ''Clarity'' a level change results in a greater or lesser ''three-dimensional volume'' effect on the image. In this case you can select the levels from ''5'' to ''Extra''.<br />
<br />
When you deactivate the module the ''merge'' values are not lost and you will only have to re-select the desired ''level'' when you re-activate the module.<br />
<br />
The ''merging'' in the ''Sharp Mask'' consists of enhancing the details below the selected level and merging (blending) the result with the remaining levels: if you have selected ''level 3'', the details of levels ''1'', ''2'' and ''3'' will be enhanced and then merged with levels 4 and above (including the residual image). The ''merge'' slider allows you to adjust the mix, giving more or less relevance to the enhanced details with respect to the rest of the image.<br />
<br />
Similarly, in the case of ''Clarity'' the coarser levels are enhanced and merged with the rest of the photo.<br />
<br />
In both cases you have 3 sliders to adjust the changes:<br />
# ''Merge Luma'': by moving it to the right (positive values) the contrast of the details is enhanced, while with negative values the image becomes ''blurry, like a dream''.<br />
# ''Merge Chroma'': by moving it to the right (positive values) saturated tones are enhanced more than the less saturated (pastel) tones. With negative values, the image becomes less vivid and the pastel tones remain virtually unchanged.<br />
# ''Soft Radius'': high merge values can generate halos around the contrasting areas. With this control you can smooth them without affecting the image too much. However, it does have side effects: the dark areas become darker and more and more areas will be considered as not having sufficient contrast to be enhanced, so they remain unchanged.<br />
<br />
<div><ul class="leftalign"> <br />
<li class="RP3inarow"> [[File:wavelet_smc_original.jpg|thumb|none|450px|Original image. <span style="font-size: 0.8em; font-style: italic;">Courtesy of [https://www.photographyblog.com/reviews/nikon_d850_review/sample_images Photographyblog.com]]] </li><br />
<li class="RP3inarow"> [[File:wavelet_sharpm_ML60MC30.jpg|thumb|none|450px|Applying the Sharp Mask, setting Merge Luma: 60 and Merge Chroma:30. The effect is rather subtle, but you can see an increase in the sharpness of the small details.]] </li><br />
<li class="RP3inarow"> [[File:wavelet_clarity_ML60MC30.jpg|thumb|none|450px|Applying Clarity, setting Merge Luma: 60 and Merge Chroma:30. In this case the effect is more pronounced because the contrast values are higher.]] </li><br />
</ul></div><br />
<br />
Finally, under the ''Soft Radius'' you have the option to ''Show wavelet 'mask''', which allows you to see which details will be enhanced:<br />
* in the case of the ''Sharp Mask'', an image will be displayed with a black background and the details will be highlighted in white (if you have ever seen an ''Unsharp Mask'', you will find it similar).<br />
* however, with the ''Clarity'' option, the mask is different and is based on [https://kaiminghe.github.io/eccv10/index.html Guided Image Filtering] and is less intuitive. In general, the white areas (although blurred) are the ones that will be highlighted.<br />
<br />
== Residual Image module ==<br />
<br />
You will recall that the residual image corresponds to the original image minus the details that were extracted in the levels. Any changes made in the levels will therefore have no effect on the residual image and the more levels you select in the general settings of the tool, the greater the difference between the original and the residual image. Furthermore, when you select more than 6 levels, the residual image will contain almost no noise, so changing the global contrast or chromaticity in the residual image will have almost no effect on the noise.<br />
<br />
<div><ul class="leftalign"> <br />
<li class="RPgallery"> [[File:wavelets_residual_original.jpg|thumb|none|400px|Original image. <span style="font-size: 0.8em; font-style: italic;">Courtesy of [https://www.photographyblog.com/reviews/nikon_z7_review/sample_images Photographyblog.com]]] </li><br />
<li class="RPgallery"> [[File:wavelets_residual_L5.jpg|thumb|none|400px|Residual image when decomposing to 5 levels of detail.]] </li><br />
<li class="RPgallery"> [[File:wavelets_residual_L7.jpg|thumb|none|400px|Residual image when decomposing to 7 levels of detail.]] </li><br />
<li class="RPgallery"> [[File:wavelets_residual_L8.jpg|thumb|none|400px|Residual image when decomposing to 8 levels of detail.]] </li><br />
</ul></div><br />
<br />
It is important to note that to avoid artifacts and out of [https://en.wikipedia.org/wiki/Gamut gamut] tones, you will need to closely observe the adjustments you make on each of the levels and on the residual image: if the original image already has tones close to the boundaries of the color space, significantly increasing the contrast or chromaticity of the detail will almost inevitably result in artifacts or tones outside the color range. In this case, increasing or decreasing the residual image contrast and chromaticity will allow you to keep the colors within the range defined by the color space.<br />
<br />
As you can see, residual image adjustments are a fundamental aspect of wavelet level processing. They allow you to:<br />
* work with shadows and highlights regardless of the details they contain,<br />
* reduce overall contrast and chromaticity, to better perceive micro-contrast,<br />
* change the chromaticity to reduce artifacts resulting from excessive modifications in the levels (e.g. in the skies)<br />
* etc<br />
<br />
=== Shadows/highlights of the residual image ===<br />
<br />
<br />
<br />
<br />
Moving the sliders for Shadows and Highlights to the right increases the luminance of those areas; to the left (negative values), it reduces it. This can be used to further darken the shadows and increase the brightness of the highlights:<br />
<br />
<div><ul class="leftalign"> <br />
<li class="RP3inarow"> [[File:wavelets_residual_original.jpg|thumb|none|400px|Original image.]] </li><br />
<li class="RP3inarow"> [[File:wavelets_residual_SH.jpg|thumb|none|400px|Residual image with ''Shadows: -20'' and ''High lights: 50''.]] </li><br />
<li class="RP3inarow"> [[File:wavelets_residual_SH-out.jpg|thumb|none|400px|The resulting photograph with the changes in the residual image.]] </li><br />
</ul></div><br />
<br />
The effect of these changes is influenced by the threshold sliders, which have a luminance scale ranging from ''0'' to ''100'': for the shadows, moving the threshold slider to the left will progressively limit the action of the slider to the darker luminance values. Similarly for the highlights, moving the threshold slider to the right will progressively limit the action of the highlights slider to the higher luminance values.<br />
To help decide which threshold values to use you can check the luminance values by hovering the mouse over the relevant area in the image and reading off the L* luminance value in the Navigator panel. These values correspond directly to the scale used for the threshold sliders.<br />
<br />
If sliders for shadows and highlights have positive values, you can only ''recover'' the shadows (lightening them) or highlights (darkening them). The result is similar to the [[Shadows/Highlights]] tool in the Exposure tab. However, note that this tool does not have the ability to [[Exposure#Highlight_Reconstruction|Reconstruct Highlights]].<br />
<br />
* negative values have a strong impact on the residual image<br />
* highlights are darkened if negative values are used<br />
* highlights are lightened if positive values are used<br />
* shadows are darkened if negative values are used<br />
* shadows become lighter if positive values are used<br />
<br />
<div><ul class="leftalign"> <br />
<li class="RP3inarow"> [[File:wavelets_residual_SHneg_original.jpg|thumb|none|400px|Original image.]] </li><br />
<li class="RP3inarow"> [[File:wavelets_residual_SHneg_old.jpg|thumb|none|400px|Residual image using negative values in shadows and positive values in highlights]] </li><br />
<li class="RP3inarow"> [[File:wavelets_residual_SHneg_new.jpg|thumb|none|400px|Residual image using the same values as before, but without negative values.]] </li><br />
</ul></div><br />
<br />
<br />
The last option in this group is the ''Radius Shadows/Highlights''. Note: this slider will be hidden when the ''Algorithm using negative values'' option is activated.<br />
<br />
This slider applies [https://kaiminghe.github.io/eccv10/index.html Guided Image Filtering] that attenuates the transitions in the shadows and the highlights caused by the previous adjustments. It controls the area of influence of adjustments made in the shadows and highlights to improve the way they are integrated into the rest of the image.<br />
<br />
You can adjust the shadows and highlights to:<br />
* add impact to shiny objects,<br />
* prevent the highlights from becoming saturated,<br />
* lift the shadows,<br />
* etc<br />
<br />
=== Residual Image Contrast Compression ===<br />
<br />
This is one of the key aspects of wavelet level processing: the '''''Contrast''''' slider allows you to make changes to the contrast of the residual image separately from contrast changes to the details in the levels. <br />
<br />
Moderate reductions in the residual image contrast will make the contrast in the details stand out more clearly and give a greater impression of depth and relief. This allows you to limit increases in contrast for the details to avoid generating artifacts and at the same time, produce an effect that is visually equivalent to a greater increase.<br />
<br />
However for certain images, drastic changes in the contrast of the residual image will allow you to achieve some interesting effects:<br />
<br />
<div><ul class="leftalign"> <br />
<li class="RPside2side"> [[File:wavelets_residual_contrast-.jpg|thumb|none|500px|Dreamlike effect, by drastically reducing the residual image contrast (''-80'').]] </li><br />
<li class="RPside2side"> [[File:wavelets_residual_contrast+.jpg|thumb|none|500px|Result of increasing the residual image contrast to ''90''.]] </li><br />
</ul></div><br />
<br />
To help you control the effect of this module, there is a set of options that allow you to adjust the dynamic range of the residual image. These options are grouped into ''Contrast Compression'' and ''Tone Mapping Compression''.<br />
<br />
==== Compression Method: Contrast ====<br />
<br />
The effects of the contrast slider are immediately visible and vary almost linearly depending on the position of the cursor: to the right the contrast will increase and to the left it will decrease. The action of the slider is limited internally to avoid artifacts.<br />
<br />
The '''Compression strength''' modifies the dynamic range of the residual image: moving the slider to the right reduces it (shadows are lightened and highlights are reduced) and to the left, increases it (shadows are darkened and highlights are slightly intensified).<br />
<br />
The '''Compression gamma''' modifies the distribution of light and shadow, effectively moving the histogram to the left or right.<br />
<br />
With these controls you can, for example, reduce the effects of fog or compress the dynamic range of high dynamic range images.<br />
<br />
==== Compression Method: Tone Mapping ====<br />
<br />
<br />
In this case the compression method used is the same as the [[Tone_Mapping|Tone Mapping]] tool and its sliders act in the same way. It acts only in the residual image and will make in-depth modifications to the contrast (in the same way as Tone Mapping). Because of this, you will most likely have to readjust any changes in the levels as well to ensure that the overall image remains balanced.<br />
<br />
Although you are applying tone mapping to the residual image, this doesn't prevent you from activating the global ''Tone Mapping'' tool as well. In this case, care is needed because using both tools at the same time can generate artifacts.<br />
<br />
=== Blur ===<br />
<br />
<br />
<br />
This group of two sliders may seem trivial, but it can be an interesting aid to improve the [https://en.wikipedia.org/wiki/Bokeh bokeh] of the image, by blurring the luminance of the residual image ('''''Blur Luminance''''') and its color component ('''''Blur Chroma''''').<br />
<br />
The result is closely linked to the values and to the number of [[#Wavelet_levels|Wavelet levels]]: to obtain a good bokeh you need to be able to adjust the amount of detail in the image depending on whether you want the background to be partially recognizable or completely blurred. <br />
<br />
Normally the best results will be obtained with 7 or more wavelet levels and with modest blur values (around ''50''), as it is easy to generate halos and artifacts with lower levels or extreme values.<br />
<br />
=== Chroma of the residual image ===<br />
<br />
The Chroma slider works on the same principle as described for the contrast slider above, except that in this case it will change the saturation of the residual image tones.<br />
<br />
The ''Intensity'' control is linked to the values set in the sky hue protection range as explained below.<br />
<br />
==== Sky hue ====<br />
<br />
The title refers to ''sky hue'', but you are not restricted to sky colors and can adjust the color tones without limitation. As mentioned previously, the colours are linked to the ''Intensity'' control.<br />
<br />
The default range covers the usual shades of blue in the sky.<br />
<br />
==== Sky targetting/protection ====<br />
<br />
With this control you can decide whether you want to modify, the chroma of areas containing colors defined in the previous range:<br />
* with the slider at ''0'' the changes made to the chroma control will be applied equally to all tones in the image<br />
* selecting ''-100'' (sliding left) centers chroma changes in the selected tonal range<br />
* on the contrary, selecting ''100'' (sliding right) will modify the tones that ''don't'' match the selected range.<br />
<br />
In the intermediate positions between ''0'' and ''±100'' the changes are made progressively towards the chosen range, or towards the rest of the tones.<br />
<br />
This control is very useful to prevent over-saturation of human skin tones, which results in an immediately noticeable «carrot look».<br />
<br />
=== Residual image curve ===<br />
<br />
This is a Flat Curve with colored vertical lines and sliding dots and is independent of the ''sky hue range'' and the Chroma Intensity control: you can use it to modify the tones so that they take on a dominant color, independently of the rest of the controls of the module.<br />
<br />
It works as follows: if you move a dot upwards, the areas of the image with the color of that particular line will take on the hue of the line immediately to the right. If you move it down, the dominant will be the color of the line immediately to the left. For example: by moving the point of the yellow line up, the yellow areas of the residual image will take on a greenish hue (the line to the right of the yellow), whereas if you move the point down, the dominant will be orange (the line to the left of the yellow).<br />
<br />
=== Toning and Color Balance ===<br />
<br />
Activating this option presents 3 pairs of tone controls for ''Highlights'', ''Midtones'' and ''Shadows'', respectively, which can be used to color tone the residual image.<br />
<br />
The controls modify the ''a*'' and ''b*'' components of the Lab color space, so the changes will be:<br />
* for component ''a*'' = from green to magenta <br />
* for component ''b*'' = from blue to yellow<br />
<br />
The results will depend on the intensity of the changes:<br />
* with high values you can create special effects, similar to those achieved with the ''Chroma Module'', but focused on the residual image. You can use it in combination with that module if you wish<br />
* with moderate values you can manually correct the white balance: for example, imagine a scene where the main details are in a shaded area which has a blue color cast and the background is in full daylight and has a different color temperature. In this case you can adjust the white balance for the details (and remove the blue cast) and then readjust the background (the residual image) and customise the white balance for each area (highlights, mid-tones and shadows)<br />
<br />
Note that the residual image contrast compression controls, which modify the luminance values of each area, will have a direct influence on the results achieved with this part of the module.<br />
<br />
== Final Touchup module ==<br />
<br />
In this module you can apply small touch-up adjustments to the image. However because it is located at the end of the Wavelet levels tool, any significant modifications carried out here may mean that you have to readjust the rest of the modules.<br />
<br />
=== Directional Contrast ===<br />
<br />
In general, the initial balance between the 3 directional components of image decomposition is respected throughout the tool: vertical, horizontal and diagonal. However, with this module you can increase the weight of one over the other, to achieve a different result.<br />
<br />
==== Contrast Balance Method ====<br />
<br />
This ''balance'' control changes the balance between diagonal decomposition on the one hand and vertical and horizontal decomposition on the other. Its principle is similar to that of the [http://www.cs.huji.ac.il/~danix/epd edge-preserving decomposition] which is based on the [https://en.wikipedia.org/wiki/Cholesky_decomposition Cholesky factorization] and linearly modifies the luminance values of the image.<br />
<br />
This module allows you to modify the effects of the following modules: Contrast, Chroma and Residual Image Tone Mapping.<br />
<br />
You have two choices:<br />
* Slider: with this option, the '''''Contrast balance d/v-h''''' control appears allowing you to modify the contrast values in the image. Moving it to the right intensifies the overall image contrast, whereas moving it to the left reduces the contrast. Bear in mind though that you are acting on the balance between the different directions of decomposition, so with extreme values you'll introduce important artifacts.<br />
* Curve: In this case the curve '''''Contrast balance d/v-h balance curve''''' appears, which acts on the balance of the luminance values of the image.<br />
<br />
In both cases, there is an additional control: '''Delta balance levels'''. When it is set to zero (default), all levels of the decomposition are processed in the same way. If it is placed on the left, the lower levels are emphasized (the fine details) and the upper levels are reduced (those that give volume to the image). On the other hand, if it is placed to the right, the lower levels are reduced and the upper levels are increased.<br />
<br />
You also have at your disposal an '''''Attenuation Response''''' slider, which will act as described in the [[#Attenuation_and_selectivity_in_contrast_changes|chapter on attenuation of the Contrast module]].<br />
<br />
Finally the option '''''Chrominance balance''''' allows you to modify the d/v-h balance of the chromatic components of the decomposition using the same controls as above (slider or curve).<br />
<br />
=== Final Local Contrast ===<br />
<br />
This curve is located at the end of the processing pipeline, just before recomposition and acts non-linearly on the contrast of the decomposition levels.<br />
<br />
Please note that this curve, which acts on the initial local contrast and not on the luminance, does not duplicate the previous one (''Contrast balance'').<br />
<br />
On the graph, the center of the abscissa corresponds to the mean value of the local contrast and a third of the way on each side there is a point corresponding to the mean plus one standard deviation of the local contrast values. By changing the shape of the curve you will reduce or increase the effects of the modulus of ''Contrast'', the ''Edge sharpness'', the ''Balance method'' and even the very principle of decomposition - recomposition.<br />
<br />
By default the curve is ''flat'' (i.e. it has no effect), although you can modify it to your liking to e.g. further reduce the value of low local contrast and thus soften the visibility of the noise, or reduce the values of high local contrasts and avoid artifacts.<br />
<br />
In addition, there is also a '''''Attenuation Response''''' slider, which will act in the same way explained in the [[#Attenuation_and_selectivity_in_contrast_changes|chapter on the attenuation of the Contrast module]].<br />
<br />
=== ''After'' Contrast Curve ===<br />
<br />
This curve is not related to the previous curves. It is at the end of the wavelet levels processing pipeline, after the recomposition of the levels plus the residual image, and allows you to modify the global contrast of the image.<br />
<br />
It acts on luminance and its use is similar to the other tonal curves found in RawTherapee, although in this case you will not see a background histogram.<br />
<br />
Finally, you also have a '''''Soft Radius''''' slider that allows you to apply a blur to selected areas so that they blend in better with the image.<br />
<br />
== Final comparison ==<br />
<br />
&nbsp;<br />
<br />
<div><ul class="leftalign"> <br />
<li class="RPside2side"> [[File:wavelets_original_big.png|thumb|left|1000px|Original image]] </li><br />
<li class="RPside2side"> [[File:wavelets_final_big.jpg|thumb|left|1000px|Final image]] </li><br />
</ul></div></div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=Main_Page&diff=10106Main Page2023-03-09T14:01:31Z<p>DrSlony: Fixed language selection header colspan</p>
<hr />
<div>[[File:08_rt57_mushroom_blades_rawpedia.png|600px|right|link=]]<br />
<br />
Welcome to '''RawTherapee's''' documentation!<br />
<br />
If you're a new user, don't miss the [[Getting Started]] page to quickly learn your way around this awesome raw image processing program.<br />
<br />
If you're an experienced user, here you have an index of all the topics covered.<br />
<br />
{| class="wikitable" style="float: left; margin-right: 2em; text-align:center; font-variant: small-caps"<br />
|-<br />
! style="padding: 0 1em;" colspan="7" | In other languages<br />
|-<br />
| [[File:Flag_of_Brazil.svg|90x60px|frameless|link=Main_Page/pt|Brasileiro]]<br>[[Main_Page/pt|Brasileiro]]<br />
| [[File:Flag_of_Catalonia.svg|90x60px|frameless|link=Main_Page/ca|Català]]<br>[[Main_Page/ca|Català]]<br />
| [[File:Flag_of_Germany.svg|90x60px|frameless|link=Main_Page/de|Deutsch]]<br>[[Main_Page/de|Deutsch]]<br />
| [[File:Flag_of_Spain.svg|90x60px|frameless|link=Main_Page/es|Español]]<br>[[Main_Page/es|Español]]<br />
| [[File:Flag_of_France.svg|90x60px|frameless|link=Main_Page/fr|Française]]<br>[[Main_Page/fr|Français]]<br />
| [[File:Flag_of_Italy.svg|90x60px|frameless|link=Main_Page/it|Italiano]]<br>[[Main_Page/it|Italiano]]<br />
| [[File:Flag_of_Japan.svg|90x60px|frameless|link=Main_Page/jp|日本]]<br>[[Main_Page/jp|日本語]]<br />
|}<br />
<br />
<br style="clear: left;"><br />
<br />
== RawTherapee ==<br />
<br />
<div class="container"><br />
=== General Information ===<br />
<br />
<div class="RP3columns"><br />
* [[Getting Started]]<br />
* [[Features]]<br />
* [[Download]]<br />
* [[The Floating Point Engine]]<br />
* [[Bit Depth]]<br />
* [[RGB and Lab]]<br />
* [[About Noise Reduction]]<br />
* [[File Browser|The File Browser]]<br />
* [[Queue|The Queue]]<br />
* [[Editor|The Editor]]<br />
* [[Batch Adjustments - Sync]]<br />
* [[Saving Images]]<br />
* [[Edit Current Image in External Editor]]<br />
* [[Adding Support for New Raw Formats]]<br />
* [[File Paths]]<br />
* [[Preferences]]<br />
* [[GIMP Plugin]]<br />
* [[ICC Profile Creator]]<br />
* [[Making a Portable Installation]]<br />
* [[Command-Line Options]]<br />
* [[Keyboard Shortcuts]]<br />
* [[Toolchain Pipeline|Toolchain pipeline - Colorimetry]]<br />
</div><br />
<hr/><br />
<br />
=== Processing Profiles ===<br />
<br />
<div class="RP3columns"><br />
<br />
<div class="keeptogether"><br />
* [[Sidecar Files - Processing Profiles]]<br />
* [[Creating processing profiles for general use]]<br />
* [[Dynamic processing profiles]]<br />
</div><br />
<br />
<div class="keeptogether"><br />
==== Processing Profile Scripts ====<br />
* [[RTProfileSelector]]<br />
* [[RTbatch]]<br />
</div><br />
<br />
<div class="keeptogether"><br />
==== Bundled Processing Profiles ====<br />
* [[Neutral]]<br />
* [[Auto-Matched Curve]]<br />
* [[Standard Film Curve]]<br />
* [[Pop]]<br />
* [[Unclipped]]<br />
</div><br />
</div><br />
<hr/><br />
<br />
=== Tool Description ===<br />
<br />
<div class="RP1columns"><br />
* [[General Comments About Some Toolbox Widgets]]<br />
* [[Favorites Tab]]<br />
</div><br />
<br />
<div class="RP3columns"><br />
<br />
<div class="keeptogether"><br />
==== Exposure Tab ====<br />
<br />
* [[Exposure]]<br />
* [[Shadows/Highlights]]<br />
* [[Tone Mapping]]<br />
* [[Dynamic Range Compression]]<br />
* [[Vignetting Filter]]<br />
* [[Graduated Filter]]<br />
* [[Lab Adjustments|L*a*b* Adjustments]]<br />
</div><br />
<br />
<div class="keeptogether"><br />
==== Detail Tab ====<br />
<br />
* [[Spot Removal]]<br />
* [[Sharpening]]<br />
* [[Local Contrast]]<br />
* [[Edges and Microcontrast]]<br />
* [[Impulse Noise Reduction]]<br />
* [[Noise Reduction]]<br />
* [[Defringe]]<br />
* [[Contrast by Detail Levels]]<br />
* [[Haze Removal]]<br />
</div><br />
<br />
<div class="keeptogether"><br />
<br />
==== Color Tab ====<br />
<br />
* [[White Balance]]<br />
* [[Vibrance]]<br />
* [[Channel Mixer]]<br />
* [[Black-and-White]]<br />
* [[Black-and-White addon]]<br />
* [[HSV Equalizer]]<br />
* [[Film Simulation]]<br />
* [[Film Negative]]<br />
* [[Soft Light]]<br />
* [[RGB Curves]]<br />
* [[Color Toning]]<br />
* [[Color Management]]<br />
* [[Color Management addon | Color Management Supplement]]<br />
</div><br />
<br />
<div class="keeptogether"><br />
<br />
==== Advanced Tab ====<br />
<br />
* [[Retinex]]<br />
* [[CIECAM02|Color Appearance Model Cam02/16 & Jzazbz]]<br />
* [[Wavelet Levels]]<br />
</div><br />
<br />
<div class="keeptogether"><br />
<br />
==== Local Tab====<br />
* [[Local Adjustments]]<br />
</div><br />
<div class="keeptogether"><br />
<br />
==== Transform Tab ====<br />
<br />
* [[Crop]]<br />
* [[Resize]]<br />
* [[Lens/Geometry]]<br />
</div><br />
<br />
<div class="keeptogether"><br />
==== Raw Tab ====<br />
<br />
* [[Sensor with Bayer/X-Trans Matrix]]<br />
* [[Demosaicing]]<br />
* [[Raw Black Points]]<br />
* [[Preprocessing]]<br />
* [[Chromatic Aberration Correction]]<br />
* [[Raw White Points]]<br />
* [[Preprocessing White Balance]]<br />
* [[Dark-Frame]]<br />
* [[Flat-Field]]<br />
* [[Capture Sharpening]]<br />
</div><br />
<br />
<div class="keeptogether"><br />
<br />
==== Metadata Tab ====<br />
<br />
* [[Metadata Copy Mode]]<br />
* [[Exif Tab]]<br />
* [[IPTC Tab]]<br />
</div><br />
</div><br />
<hr/><br />
<br />
=== Interact ===<br />
<br />
<div class="RP1columns"><br />
* [[Forum]]<br />
<!--* [[IRC]]--><br />
</div><br />
<br />
=== Compiling ===<br />
<br />
<div class="RP1columns"><br />
* In [[Linux]]<br />
* In [[Windows]]<br />
* In [[macOS]]<br />
</div><br />
<br />
=== Troubleshooting ===<br />
<br />
<div class="RP1columns"><br />
* [[How to write useful bug reports]]<br />
* [[How to fix crashes on startup]]<br />
* [[Wayland]]<br />
</div><br />
<br />
=== Localization ===<br />
<br />
<div class="RP1columns"><br />
* [[Translating RawTherapee]]<br />
* [[Translating RawPedia]]<br />
</div><br />
</div><br />
<br />
== RawPedia ==<br />
<br />
<div class="container"><br />
<div class="RP1columns"><br />
* [[Contributing]]<br />
</div><br />
</div><br />
<br />
== General Photography ==<br />
<br />
<div class="container"><br />
<br />
<div class="RP1columns"><br />
* [[How to convert raw formats to DNG]]<br />
* [[How to create DCP color profiles]]<br />
* [[How to create LCP profiles]]<br />
* [[How to get LCP and DCP profiles]]<br />
* [[How to extract and examine ICC profiles]]<br />
* [[How to get Nikon ICM profiles]]<br />
* [[Watermarking]]<br />
* [[Image file formats and compression]]<br />
</div><br />
<br />
</div></div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=Main_Page&diff=10105Main Page2023-03-09T14:00:37Z<p>DrSlony: Fixed language selection by reverting to use wikitable, and revert to using SVG flag images</p>
<hr />
<div>[[File:08_rt57_mushroom_blades_rawpedia.png|600px|right|link=]]<br />
<br />
Welcome to '''RawTherapee's''' documentation!<br />
<br />
If you're a new user, don't miss the [[Getting Started]] page to quickly learn your way around this awesome raw image processing program.<br />
<br />
If you're an experienced user, here you have an index of all the topics covered.<br />
<br />
{| class="wikitable" style="float: left; margin-right: 2em; text-align:center; font-variant: small-caps"<br />
|-<br />
! style="padding: 0 1em;" colspan="6" | In other languages<br />
|-<br />
| [[File:Flag_of_Brazil.svg|90x60px|frameless|link=Main_Page/pt|Brasileiro]]<br>[[Main_Page/pt|Brasileiro]]<br />
| [[File:Flag_of_Catalonia.svg|90x60px|frameless|link=Main_Page/ca|Català]]<br>[[Main_Page/ca|Català]]<br />
| [[File:Flag_of_Germany.svg|90x60px|frameless|link=Main_Page/de|Deutsch]]<br>[[Main_Page/de|Deutsch]]<br />
| [[File:Flag_of_Spain.svg|90x60px|frameless|link=Main_Page/es|Español]]<br>[[Main_Page/es|Español]]<br />
| [[File:Flag_of_France.svg|90x60px|frameless|link=Main_Page/fr|Française]]<br>[[Main_Page/fr|Français]]<br />
| [[File:Flag_of_Italy.svg|90x60px|frameless|link=Main_Page/it|Italiano]]<br>[[Main_Page/it|Italiano]]<br />
| [[File:Flag_of_Japan.svg|90x60px|frameless|link=Main_Page/jp|日本]]<br>[[Main_Page/jp|日本語]]<br />
|}<br />
<br />
<br style="clear: left;"><br />
<br />
== RawTherapee ==<br />
<br />
<div class="container"><br />
=== General Information ===<br />
<br />
<div class="RP3columns"><br />
* [[Getting Started]]<br />
* [[Features]]<br />
* [[Download]]<br />
* [[The Floating Point Engine]]<br />
* [[Bit Depth]]<br />
* [[RGB and Lab]]<br />
* [[About Noise Reduction]]<br />
* [[File Browser|The File Browser]]<br />
* [[Queue|The Queue]]<br />
* [[Editor|The Editor]]<br />
* [[Batch Adjustments - Sync]]<br />
* [[Saving Images]]<br />
* [[Edit Current Image in External Editor]]<br />
* [[Adding Support for New Raw Formats]]<br />
* [[File Paths]]<br />
* [[Preferences]]<br />
* [[GIMP Plugin]]<br />
* [[ICC Profile Creator]]<br />
* [[Making a Portable Installation]]<br />
* [[Command-Line Options]]<br />
* [[Keyboard Shortcuts]]<br />
* [[Toolchain Pipeline|Toolchain pipeline - Colorimetry]]<br />
</div><br />
<hr/><br />
<br />
=== Processing Profiles ===<br />
<br />
<div class="RP3columns"><br />
<br />
<div class="keeptogether"><br />
* [[Sidecar Files - Processing Profiles]]<br />
* [[Creating processing profiles for general use]]<br />
* [[Dynamic processing profiles]]<br />
</div><br />
<br />
<div class="keeptogether"><br />
==== Processing Profile Scripts ====<br />
* [[RTProfileSelector]]<br />
* [[RTbatch]]<br />
</div><br />
<br />
<div class="keeptogether"><br />
==== Bundled Processing Profiles ====<br />
* [[Neutral]]<br />
* [[Auto-Matched Curve]]<br />
* [[Standard Film Curve]]<br />
* [[Pop]]<br />
* [[Unclipped]]<br />
</div><br />
</div><br />
<hr/><br />
<br />
=== Tool Description ===<br />
<br />
<div class="RP1columns"><br />
* [[General Comments About Some Toolbox Widgets]]<br />
* [[Favorites Tab]]<br />
</div><br />
<br />
<div class="RP3columns"><br />
<br />
<div class="keeptogether"><br />
==== Exposure Tab ====<br />
<br />
* [[Exposure]]<br />
* [[Shadows/Highlights]]<br />
* [[Tone Mapping]]<br />
* [[Dynamic Range Compression]]<br />
* [[Vignetting Filter]]<br />
* [[Graduated Filter]]<br />
* [[Lab Adjustments|L*a*b* Adjustments]]<br />
</div><br />
<br />
<div class="keeptogether"><br />
==== Detail Tab ====<br />
<br />
* [[Spot Removal]]<br />
* [[Sharpening]]<br />
* [[Local Contrast]]<br />
* [[Edges and Microcontrast]]<br />
* [[Impulse Noise Reduction]]<br />
* [[Noise Reduction]]<br />
* [[Defringe]]<br />
* [[Contrast by Detail Levels]]<br />
* [[Haze Removal]]<br />
</div><br />
<br />
<div class="keeptogether"><br />
<br />
==== Color Tab ====<br />
<br />
* [[White Balance]]<br />
* [[Vibrance]]<br />
* [[Channel Mixer]]<br />
* [[Black-and-White]]<br />
* [[Black-and-White addon]]<br />
* [[HSV Equalizer]]<br />
* [[Film Simulation]]<br />
* [[Film Negative]]<br />
* [[Soft Light]]<br />
* [[RGB Curves]]<br />
* [[Color Toning]]<br />
* [[Color Management]]<br />
* [[Color Management addon | Color Management Supplement]]<br />
</div><br />
<br />
<div class="keeptogether"><br />
<br />
==== Advanced Tab ====<br />
<br />
* [[Retinex]]<br />
* [[CIECAM02|Color Appearance Model Cam02/16 & Jzazbz]]<br />
* [[Wavelet Levels]]<br />
</div><br />
<br />
<div class="keeptogether"><br />
<br />
==== Local Tab====<br />
* [[Local Adjustments]]<br />
</div><br />
<div class="keeptogether"><br />
<br />
==== Transform Tab ====<br />
<br />
* [[Crop]]<br />
* [[Resize]]<br />
* [[Lens/Geometry]]<br />
</div><br />
<br />
<div class="keeptogether"><br />
==== Raw Tab ====<br />
<br />
* [[Sensor with Bayer/X-Trans Matrix]]<br />
* [[Demosaicing]]<br />
* [[Raw Black Points]]<br />
* [[Preprocessing]]<br />
* [[Chromatic Aberration Correction]]<br />
* [[Raw White Points]]<br />
* [[Preprocessing White Balance]]<br />
* [[Dark-Frame]]<br />
* [[Flat-Field]]<br />
* [[Capture Sharpening]]<br />
</div><br />
<br />
<div class="keeptogether"><br />
<br />
==== Metadata Tab ====<br />
<br />
* [[Metadata Copy Mode]]<br />
* [[Exif Tab]]<br />
* [[IPTC Tab]]<br />
</div><br />
</div><br />
<hr/><br />
<br />
=== Interact ===<br />
<br />
<div class="RP1columns"><br />
* [[Forum]]<br />
<!--* [[IRC]]--><br />
</div><br />
<br />
=== Compiling ===<br />
<br />
<div class="RP1columns"><br />
* In [[Linux]]<br />
* In [[Windows]]<br />
* In [[macOS]]<br />
</div><br />
<br />
=== Troubleshooting ===<br />
<br />
<div class="RP1columns"><br />
* [[How to write useful bug reports]]<br />
* [[How to fix crashes on startup]]<br />
* [[Wayland]]<br />
</div><br />
<br />
=== Localization ===<br />
<br />
<div class="RP1columns"><br />
* [[Translating RawTherapee]]<br />
* [[Translating RawPedia]]<br />
</div><br />
</div><br />
<br />
== RawPedia ==<br />
<br />
<div class="container"><br />
<div class="RP1columns"><br />
* [[Contributing]]<br />
</div><br />
</div><br />
<br />
== General Photography ==<br />
<br />
<div class="container"><br />
<br />
<div class="RP1columns"><br />
* [[How to convert raw formats to DNG]]<br />
* [[How to create DCP color profiles]]<br />
* [[How to create LCP profiles]]<br />
* [[How to get LCP and DCP profiles]]<br />
* [[How to extract and examine ICC profiles]]<br />
* [[How to get Nikon ICM profiles]]<br />
* [[Watermarking]]<br />
* [[Image file formats and compression]]<br />
</div><br />
<br />
</div></div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=Main_Page&diff=10104Main Page2023-03-09T13:46:06Z<p>DrSlony: </p>
<hr />
<div>[[File:08_rt57_mushroom_blades_rawpedia.png|600px|right|link=]]<br />
<br />
<div class="greetings"><br />
Welcome to '''RawTherapee's''' documentation!<br />
<br />
If you're a new user, don't miss the [[Getting Started]] page to quickly learn your way around this awesome raw image processing program.<br />
<br />
If you're an experienced user, here you have an index of all the topics covered.<br />
</div><br />
<br />
<div class=langsbox-wrapper><br />
<div class="row small-uncollapse large-collapse langsbox"><br />
<span class="langsavail">In other languages</span><br />
<ul class="small-block-grid-2 medium-block-grid-4 large-block-grid-7 columns flagsbox"><br />
<li>[[File:braz.png|90x60px|frameless|link=Main_Page/pt|Brasileiro]]<br>[[Main_Page/pt|Brasileiro]]</li><br />
<li>[[File:ct.png|90x60px|frameless|link=Main_Page/ca|Català]]<br>[[Main_Page/ca|Català]]</li><br />
<li>[[File:deu.png|90x60px|frameless|link=Main_Page/de|Deutsch]]<br>[[Main_Page/de|Deutsch]]</li><br />
<li>[[File:esp.png|90x60px|frameless|link=Main_Page/es|Español]]<br>[[Main_Page/es|Español]]</li><br />
<li>[[File:frc.png|90x60px|frameless|link=Main_Page/fr|Française]]<br>[[Main_Page/fr|Français]]</li><br />
<li>[[File:ita.png|90x60px|frameless|link=Main_Page/it|Italiano]]<br>[[Main_Page/it|Italiano]]</li><br />
<li>[[File:jap.png|90x60px|frameless|link=Main_Page/jp|日本]]<br>[[Main_Page/jp|日本語]]</li><br />
</ul><br />
</div><br />
</div><br />
<br />
<br style="clear: both;"><br />
<br />
== RawTherapee ==<br />
<br />
<div class="container"><br />
=== General Information ===<br />
<br />
<div class="RP3columns"><br />
* [[Getting Started]]<br />
* [[Features]]<br />
* [[Download]]<br />
* [[The Floating Point Engine]]<br />
* [[Bit Depth]]<br />
* [[RGB and Lab]]<br />
* [[About Noise Reduction]]<br />
* [[File Browser|The File Browser]]<br />
* [[Queue|The Queue]]<br />
* [[Editor|The Editor]]<br />
* [[Batch Adjustments - Sync]]<br />
* [[Saving Images]]<br />
* [[Edit Current Image in External Editor]]<br />
* [[Adding Support for New Raw Formats]]<br />
* [[File Paths]]<br />
* [[Preferences]]<br />
* [[GIMP Plugin]]<br />
* [[ICC Profile Creator]]<br />
* [[Making a Portable Installation]]<br />
* [[Command-Line Options]]<br />
* [[Keyboard Shortcuts]]<br />
* [[Toolchain Pipeline|Toolchain pipeline - Colorimetry]]<br />
</div><br />
<hr/><br />
<br />
=== Processing Profiles ===<br />
<br />
<div class="RP3columns"><br />
<br />
<div class="keeptogether"><br />
* [[Sidecar Files - Processing Profiles]]<br />
* [[Creating processing profiles for general use]]<br />
* [[Dynamic processing profiles]]<br />
</div><br />
<br />
<div class="keeptogether"><br />
==== Processing Profile Scripts ====<br />
* [[RTProfileSelector]]<br />
* [[RTbatch]]<br />
</div><br />
<br />
<div class="keeptogether"><br />
==== Bundled Processing Profiles ====<br />
* [[Neutral]]<br />
* [[Auto-Matched Curve]]<br />
* [[Standard Film Curve]]<br />
* [[Pop]]<br />
* [[Unclipped]]<br />
</div><br />
</div><br />
<hr/><br />
<br />
=== Tool Description ===<br />
<br />
<div class="RP1columns"><br />
* [[General Comments About Some Toolbox Widgets]]<br />
* [[Favorites Tab]]<br />
</div><br />
<br />
<div class="RP3columns"><br />
<br />
<div class="keeptogether"><br />
==== Exposure Tab ====<br />
<br />
* [[Exposure]]<br />
* [[Shadows/Highlights]]<br />
* [[Tone Mapping]]<br />
* [[Dynamic Range Compression]]<br />
* [[Vignetting Filter]]<br />
* [[Graduated Filter]]<br />
* [[Lab Adjustments|L*a*b* Adjustments]]<br />
</div><br />
<br />
<div class="keeptogether"><br />
==== Detail Tab ====<br />
<br />
* [[Spot Removal]]<br />
* [[Sharpening]]<br />
* [[Local Contrast]]<br />
* [[Edges and Microcontrast]]<br />
* [[Impulse Noise Reduction]]<br />
* [[Noise Reduction]]<br />
* [[Defringe]]<br />
* [[Contrast by Detail Levels]]<br />
* [[Haze Removal]]<br />
</div><br />
<br />
<div class="keeptogether"><br />
<br />
==== Color Tab ====<br />
<br />
* [[White Balance]]<br />
* [[Vibrance]]<br />
* [[Channel Mixer]]<br />
* [[Black-and-White]]<br />
* [[Black-and-White addon]]<br />
* [[HSV Equalizer]]<br />
* [[Film Simulation]]<br />
* [[Film Negative]]<br />
* [[Soft Light]]<br />
* [[RGB Curves]]<br />
* [[Color Toning]]<br />
* [[Color Management]]<br />
* [[Color Management addon | Color Management Supplement]]<br />
</div><br />
<br />
<div class="keeptogether"><br />
<br />
==== Advanced Tab ====<br />
<br />
* [[Retinex]]<br />
* [[CIECAM02|Color Appearance Model Cam02/16 & Jzazbz]]<br />
* [[Wavelet Levels]]<br />
</div><br />
<br />
<div class="keeptogether"><br />
<br />
==== Local Tab====<br />
* [[Local Adjustments]]<br />
</div><br />
<div class="keeptogether"><br />
<br />
==== Transform Tab ====<br />
<br />
* [[Crop]]<br />
* [[Resize]]<br />
* [[Lens/Geometry]]<br />
</div><br />
<br />
<div class="keeptogether"><br />
==== Raw Tab ====<br />
<br />
* [[Sensor with Bayer/X-Trans Matrix]]<br />
* [[Demosaicing]]<br />
* [[Raw Black Points]]<br />
* [[Preprocessing]]<br />
* [[Chromatic Aberration Correction]]<br />
* [[Raw White Points]]<br />
* [[Preprocessing White Balance]]<br />
* [[Dark-Frame]]<br />
* [[Flat-Field]]<br />
* [[Capture Sharpening]]<br />
</div><br />
<br />
<div class="keeptogether"><br />
<br />
==== Metadata Tab ====<br />
<br />
* [[Metadata Copy Mode]]<br />
* [[Exif Tab]]<br />
* [[IPTC Tab]]<br />
</div><br />
</div><br />
<hr/><br />
<br />
=== Interact ===<br />
<br />
<div class="RP1columns"><br />
* [[Forum]]<br />
<!--* [[IRC]]--><br />
</div><br />
<br />
=== Compiling ===<br />
<br />
<div class="RP1columns"><br />
* In [[Linux]]<br />
* In [[Windows]]<br />
* In [[macOS]]<br />
</div><br />
<br />
=== Troubleshooting ===<br />
<br />
<div class="RP1columns"><br />
* [[How to write useful bug reports]]<br />
* [[How to fix crashes on startup]]<br />
* [[Wayland]]<br />
</div><br />
<br />
=== Localization ===<br />
<br />
<div class="RP1columns"><br />
* [[Translating RawTherapee]]<br />
* [[Translating RawPedia]]<br />
</div><br />
</div><br />
<br />
== RawPedia ==<br />
<br />
<div class="container"><br />
<div class="RP1columns"><br />
* [[Contributing]]<br />
</div><br />
</div><br />
<br />
== General Photography ==<br />
<br />
<div class="container"><br />
<br />
<div class="RP1columns"><br />
* [[How to convert raw formats to DNG]]<br />
* [[How to create DCP color profiles]]<br />
* [[How to create LCP profiles]]<br />
* [[How to get LCP and DCP profiles]]<br />
* [[How to extract and examine ICC profiles]]<br />
* [[How to get Nikon ICM profiles]]<br />
* [[Watermarking]]<br />
* [[Image file formats and compression]]<br />
</div><br />
<br />
</div></div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=Main_Page&diff=10103Main Page2023-03-09T13:44:50Z<p>DrSlony: </p>
<hr />
<div><div class="main-page-title">RawPedia. The encyclopedia of RawTherapee, raw shooting and everything raw</div><br />
<br />
[[File:08_rt57_mushroom_blades_rawpedia.png|600px|right|link=]]<br />
<br />
<div class="greetings"><br />
Welcome to '''RawTherapee's''' documentation!<br />
<br />
If you're a new user, don't miss the [[Getting Started]] page to quickly learn your way around this awesome raw image processing program.<br />
<br />
If you're an experienced user, here you have an index of all the topics covered.<br />
</div><br />
<br />
<div class=langsbox-wrapper><br />
<div class="row small-uncollapse large-collapse langsbox"><br />
<span class="langsavail">In other languages</span><br />
<ul class="small-block-grid-2 medium-block-grid-4 large-block-grid-7 columns flagsbox"><br />
<li>[[File:braz.png|90x60px|frameless|link=Main_Page/pt|Brasileiro]]<br>[[Main_Page/pt|Brasileiro]]</li><br />
<li>[[File:ct.png|90x60px|frameless|link=Main_Page/ca|Català]]<br>[[Main_Page/ca|Català]]</li><br />
<li>[[File:deu.png|90x60px|frameless|link=Main_Page/de|Deutsch]]<br>[[Main_Page/de|Deutsch]]</li><br />
<li>[[File:esp.png|90x60px|frameless|link=Main_Page/es|Español]]<br>[[Main_Page/es|Español]]</li><br />
<li>[[File:frc.png|90x60px|frameless|link=Main_Page/fr|Française]]<br>[[Main_Page/fr|Français]]</li><br />
<li>[[File:ita.png|90x60px|frameless|link=Main_Page/it|Italiano]]<br>[[Main_Page/it|Italiano]]</li><br />
<li>[[File:jap.png|90x60px|frameless|link=Main_Page/jp|日本]]<br>[[Main_Page/jp|日本語]]</li><br />
</ul><br />
</div><br />
</div><br />
<br />
<br style="clear: both;"><br />
<br />
== RawTherapee ==<br />
<br />
<div class="container"><br />
=== General Information ===<br />
<br />
<div class="RP3columns"><br />
* [[Getting Started]]<br />
* [[Features]]<br />
* [[Download]]<br />
* [[The Floating Point Engine]]<br />
* [[Bit Depth]]<br />
* [[RGB and Lab]]<br />
* [[About Noise Reduction]]<br />
* [[File Browser|The File Browser]]<br />
* [[Queue|The Queue]]<br />
* [[Editor|The Editor]]<br />
* [[Batch Adjustments - Sync]]<br />
* [[Saving Images]]<br />
* [[Edit Current Image in External Editor]]<br />
* [[Adding Support for New Raw Formats]]<br />
* [[File Paths]]<br />
* [[Preferences]]<br />
* [[GIMP Plugin]]<br />
* [[ICC Profile Creator]]<br />
* [[Making a Portable Installation]]<br />
* [[Command-Line Options]]<br />
* [[Keyboard Shortcuts]]<br />
* [[Toolchain Pipeline|Toolchain pipeline - Colorimetry]]<br />
</div><br />
<hr/><br />
<br />
=== Processing Profiles ===<br />
<br />
<div class="RP3columns"><br />
<br />
<div class="keeptogether"><br />
* [[Sidecar Files - Processing Profiles]]<br />
* [[Creating processing profiles for general use]]<br />
* [[Dynamic processing profiles]]<br />
</div><br />
<br />
<div class="keeptogether"><br />
==== Processing Profile Scripts ====<br />
* [[RTProfileSelector]]<br />
* [[RTbatch]]<br />
</div><br />
<br />
<div class="keeptogether"><br />
==== Bundled Processing Profiles ====<br />
* [[Neutral]]<br />
* [[Auto-Matched Curve]]<br />
* [[Standard Film Curve]]<br />
* [[Pop]]<br />
* [[Unclipped]]<br />
</div><br />
</div><br />
<hr/><br />
<br />
=== Tool Description ===<br />
<br />
<div class="RP1columns"><br />
* [[General Comments About Some Toolbox Widgets]]<br />
* [[Favorites Tab]]<br />
</div><br />
<br />
<div class="RP3columns"><br />
<br />
<div class="keeptogether"><br />
==== Exposure Tab ====<br />
<br />
* [[Exposure]]<br />
* [[Shadows/Highlights]]<br />
* [[Tone Mapping]]<br />
* [[Dynamic Range Compression]]<br />
* [[Vignetting Filter]]<br />
* [[Graduated Filter]]<br />
* [[Lab Adjustments|L*a*b* Adjustments]]<br />
</div><br />
<br />
<div class="keeptogether"><br />
==== Detail Tab ====<br />
<br />
* [[Spot Removal]]<br />
* [[Sharpening]]<br />
* [[Local Contrast]]<br />
* [[Edges and Microcontrast]]<br />
* [[Impulse Noise Reduction]]<br />
* [[Noise Reduction]]<br />
* [[Defringe]]<br />
* [[Contrast by Detail Levels]]<br />
* [[Haze Removal]]<br />
</div><br />
<br />
<div class="keeptogether"><br />
<br />
==== Color Tab ====<br />
<br />
* [[White Balance]]<br />
* [[Vibrance]]<br />
* [[Channel Mixer]]<br />
* [[Black-and-White]]<br />
* [[Black-and-White addon]]<br />
* [[HSV Equalizer]]<br />
* [[Film Simulation]]<br />
* [[Film Negative]]<br />
* [[Soft Light]]<br />
* [[RGB Curves]]<br />
* [[Color Toning]]<br />
* [[Color Management]]<br />
* [[Color Management addon | Color Management Supplement]]<br />
</div><br />
<br />
<div class="keeptogether"><br />
<br />
==== Advanced Tab ====<br />
<br />
* [[Retinex]]<br />
* [[CIECAM02|Color Appearance Model Cam02/16 & Jzazbz]]<br />
* [[Wavelet Levels]]<br />
</div><br />
<br />
<div class="keeptogether"><br />
<br />
==== Local Tab====<br />
* [[Local Adjustments]]<br />
</div><br />
<div class="keeptogether"><br />
<br />
==== Transform Tab ====<br />
<br />
* [[Crop]]<br />
* [[Resize]]<br />
* [[Lens/Geometry]]<br />
</div><br />
<br />
<div class="keeptogether"><br />
==== Raw Tab ====<br />
<br />
* [[Sensor with Bayer/X-Trans Matrix]]<br />
* [[Demosaicing]]<br />
* [[Raw Black Points]]<br />
* [[Preprocessing]]<br />
* [[Chromatic Aberration Correction]]<br />
* [[Raw White Points]]<br />
* [[Preprocessing White Balance]]<br />
* [[Dark-Frame]]<br />
* [[Flat-Field]]<br />
* [[Capture Sharpening]]<br />
</div><br />
<br />
<div class="keeptogether"><br />
<br />
==== Metadata Tab ====<br />
<br />
* [[Metadata Copy Mode]]<br />
* [[Exif Tab]]<br />
* [[IPTC Tab]]<br />
</div><br />
</div><br />
<hr/><br />
<br />
=== Interact ===<br />
<br />
<div class="RP1columns"><br />
* [[Forum]]<br />
<!--* [[IRC]]--><br />
</div><br />
<br />
=== Compiling ===<br />
<br />
<div class="RP1columns"><br />
* In [[Linux]]<br />
* In [[Windows]]<br />
* In [[macOS]]<br />
</div><br />
<br />
=== Troubleshooting ===<br />
<br />
<div class="RP1columns"><br />
* [[How to write useful bug reports]]<br />
* [[How to fix crashes on startup]]<br />
* [[Wayland]]<br />
</div><br />
<br />
=== Localization ===<br />
<br />
<div class="RP1columns"><br />
* [[Translating RawTherapee]]<br />
* [[Translating RawPedia]]<br />
</div><br />
</div><br />
<br />
== RawPedia ==<br />
<br />
<div class="container"><br />
<div class="RP1columns"><br />
* [[Contributing]]<br />
</div><br />
</div><br />
<br />
== General Photography ==<br />
<br />
<div class="container"><br />
<br />
<div class="RP1columns"><br />
* [[How to convert raw formats to DNG]]<br />
* [[How to create DCP color profiles]]<br />
* [[How to create LCP profiles]]<br />
* [[How to get LCP and DCP profiles]]<br />
* [[How to extract and examine ICC profiles]]<br />
* [[How to get Nikon ICM profiles]]<br />
* [[Watermarking]]<br />
* [[Image file formats and compression]]<br />
</div><br />
<br />
</div></div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=IRC&diff=10102IRC2023-03-09T13:44:20Z<p>DrSlony: </p>
<hr />
<div>OBSOLETE<br />
<br />
If you would like to chat with other RawTherapee users about any topic in real time, or catch one of the devs, feel welcome to join our [https://en.wikipedia.org/wiki/Internet_Relay_Chat IRC] channel:<br />
Channel: #rawtherapee<br />
Network: freenode<br />
Server: chat.freenode.net<br />
<br />
To do so, follow these steps:<br />
# Use [http://webchat.freenode.net/?randomnick=1&channels=rawtherapee&prompt=1 webchat], or download an [http://en.wikipedia.org/wiki/Comparison_of_Internet_Relay_Chat_clients IRC client] (which is a piece of software that lets users like us talk on IRC). There are many free clients for all platforms.<br />
#* For Windows: [http://hexchat.github.io/ HexChat], [http://quassel-irc.org/ Quassel] or [http://chatzilla.hacksrus.com/ ChatZilla] (for Firefox).<br />
#* For Linux: [http://konversation.kde.org/ Konversation], [http://hexchat.github.io/ HexChat] or [http://www.weechat.org/ WeeChat] or [http://chatzilla.hacksrus.com/ ChatZilla] (for Firefox).<br />
#* For Mac OS X users the same suggestions apply as for Linux users.<br />
#* For Android: [https://play.google.com/store/apps/details?id=org.yaaic Yaaic]<br />
#: The Opera web browser also has native IRC support.<br />
#: Once you've installed an IRC client, take a look at its settings. You might want to change and set some things, e.g. set your nickname, enable %H:%M:%S timestamps, etc.<br />
# Connect to a freenode server. Type <code>/server chat.freenode.net</code><br />
# Join the #rawtherapee channel. Type: <code>/join #rawtherapee</code><br />
<br />
If you come to our IRC channel and nobody is around at the moment, don't quit after two minutes, just leave your IRC client running in the background and check back in a few hours. Your question will be seen and answered if you are still online, even if you asked it a few hours ago.</div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=White_Balance&diff=10101White Balance2023-03-09T13:36:09Z<p>DrSlony: Restructured, updated raw file copyrights</p>
<hr />
<div><div class="pagetitle">White Balance</div><br />
<br />
== Introduction ==<br />
<br />
Digital images generally consist of a mixture of the three primary colors: red, green and blue. For various reasons which you can read about in-depth elsewhere, the red, green and blue values which serve as the starting point in any raw photo development program need to be corrected in various ways before they resemble the photographed scene. One of these corrections is performed by adjusting the white balance - ensuring that neutral-colored (white) objects in the photographed scene still appear neutral on the photograph. Adjusting the white balance affects all colors, though it is easiest to discern whether the white balance is correct if an object you know to be of a neutral (white, gray) color looks non-neutral.<br />
<br />
White balancing works by multiplying each of the primary colors by a different amount, until a satisfactory result is reached. In order to make this operation more human-friendly, instead of operating on the three multipliers directly, the user is presented with an abstraction in the form of a temperature slider which adjusts colors along a blue-yellow axis, and a tint slider which adjusts them along the magenta-green axis.<br />
<br />
A neutral color is one whose red, green and blue values are equal. For example, R=G=B=65% and R=G=B=90% are both neutral, the former being darker than the latter. You can tell whether the white balance of a spot which should be neutral is correct by checking whether that spot's RGB values match, or whether the a* and b* values in the L*a*b* color space match, or whether the RGB indicator bars under the main histogram are directly over each other. You can do this even if you have a very miscalibrated monitor. Your perception of color changes depending on the color of the surroundings and of the illumination in your room, so don't always trust your eyes - verify using the method described above.<br />
<br />
Having an incorrect white balance results in the image having a color tint, typically warmer (orange) or colder (blue). Some people use this for creative effect, however there are various tools and operations which rely on the assumption that the white balance of the image is correct (for example highlight recovery in the [[Exposure]] tool, skin targeting in the [[Contrast by Detail Levels]] tool, sky targeting in the [[Wavelets]] tool, the [[CIECAM02]] tool), so you should not misuse the white balance tool to create a color cast for artistic effect but rather use it to ensure that neutral areas remain neutral, and then use [[Color Toning]] or any of the other tools to render a creative color tint.<br />
<br />
The white balance tool can be turned on/off. When off, the multipliers are set to R=1 G=1 B=1 when working with raw files. This can be useful for diagnostic purposes or when working with UniWB images.<br />
<br />
== Interface Description ==<br />
<br />
=== Method ===<br />
<br />
* [[image:Wb-camera.png]] Camera<br />
*:Takes the white balance used by the camera. If you shoot only in raw (so no raw+JPG), put the white balance settings of your camera on auto. This should generally give good results.<br />
* [[image:Wb-auto.png]] Automatic<br />
** RGB grey<br />
**:Automatically corrects the white balance, by assuming that the average color of the scene is neutral gray. Works well for a wide range of scenes, and can be a good starting point for manual adjustments.<br />
** Temperature correlation<br />
**:Provides a generally better color balance than auto “RGB grey". The algorithm is based on the best correlation (Student's test) between the colors of the image and an array of 200 spectral reference colors.<br />
*** This algorithm may give erroneous results:<br />
**** If the illuminant does not have a CRI (Color Rendering Index) close to 100, e.g. "Underwater", "Fluorescent", "Led" lighting conditions may give bad results.<br />
**** Some DNG-type files obtained after conversion with a DNG or other converter.<br />
**** If the shooting conditions are extreme (very low luminance values, etc.).<br />
*** The GUI displays the correlation value:<br />
**** A value of 1000 means either that calculation is not performed again and that the previous results are used, or that the algorithm has failed to compute a result in which case T=5002 is displayed.<br />
**** Values less than 0.01 are good.<br />
*** A description of the Itcwb algorithim in French can be found here [[White_Balance/fr#Principe_de_l.27algorithme_Temperature_correlation_-_.28Itcwb_Iterate_temperature_correlation_white_balance.29: |algorithm]] <br />
* [[image:Wb-custom.png]] Custom<br />
: Set your own color temperature and green tint by moving the two sliders and/or using the Spot WB tool.<br />
* Light source presets<br />
** [[image:Wb-sun.png]] Daylight (Sunny)<br />
** [[image:Wb-cloudy.png]] Cloudy<br />
** [[image:Wb-shade.png]] Shade<br />
** [[image:Wb-water.png]] Underwater<br />
** [[image:Wb-tungsten.png]] Tungsten<br />
** [[image:Wb-fluorescent.png]] Fluorescent<br />
** [[image:Wb-lamp.png]] Lamp<br />
** [[image:Wb-led.png]] LED<br />
** [[image:Wb-flash.png]] Flash<br />
<br />
=== Pick ===<br />
<br />
[[File:White balance 1 before.png|thumb|This tank wagon was the whitest object in the scene. We can tell that the white balance is wrong because the RGB levels are not equal, and the RGB indicator bars directly under the histogram are spread apart.]]<br />
<br />
[[File:White balance 1 after.png|thumb|Picking the white balance off the side of this tanker, which we know to have been the whitest object in the scene, adjusts the colors across the whole image such that the RGB levels in that spot are now equal.]]<br />
<br />
When you click on the Pick button [[File:Color-picker.png]] (shortcut: '''w'''), the cursor changes into a pipette when it's over the preview. Click on a neutral area to set the correct white balance for the whole image based on the clicked area.<br />
<br />
Pick a spot which should have a neutral tone - gray or white. This spot should not be clipped in any of the three channels, as clipping means that information from the clipped channel is missing. As far as white balancing is concerned, "white" does not mean R=100% G=100% B=100% as that would be clipped, but instead means a shade of gray - even a very light one, but still one without any clipping. The picked spot should also not be black, as black means that insufficient data was captured for that area, and so a correct white balance calculation cannot be performed.<br />
<br />
You can use the picker multiple times on different places in the photo until you find an ideal spot. Use the ''Size'' drop-down box to change the size of the pipette.<br />
<br />
This tool can be used as well inside a detail window. Right-click to cancel the tool and to get the regular cursor back.<br />
<br />
=== Temperature and Tint ===<br />
<br />
The temperature slider adjusts colors along the blue-yellow axis. Moving it to the left makes the image cooler (bluish); moving it to the right makes it warmer (yellowish).<br />
<br />
The tint slider adjusts colors along the magenta-green axis. Moving it to the left makes the image more magenta; moving it to the right - more green.<br />
<br />
=== Blue/Red Equalizer ===<br />
<br />
The red/blue equalizer allows to deviate from the normal behavior of "white balance", via increase or decrease of the ratio between red and blue. This can be useful when shooting conditions are far from the standard illuminant, e.g. underwater, or are far from conditions where calibrations were performed, for which the color matrices in the input profile are unsuitable.<br />
<br />
=== AWB Temperature Bias ===<br />
<br />
The auto white balance temperature bias slider allows you to specify how much the automatically-calculated temperature should deviate. Use this if you would like the automatically-calculated white balance to be cooler or warmer.<br />
<br />
== White Balance Connection to Exposure ==<br />
<br />
The white balance is described in temperature and tint, but when working with raw images it will be translated into weights of the red, green and blue channels. The weights will be adjusted so that the channel with the smallest weight reaches clipping in the working space (usually ProPhoto RGB) when the raw channel is clipped. In other words, with exposure set to 0.0 and no highlight recovery enabled the full visible range is fully defined by the raw backing. As white-balancing changes the weights you may see a slight exposure change if you make drastic changes to white balance.<br />
<br />
== The Temperature Correlation Algorithm ==<br />
<br />
This section is a technical description of the temperature correlation algorithm and its implementation. It is not necessary to know this if you just want to use the "Automatic > Temperature Correlation" white balance method, but will be of interest to those studying the matter.<br />
<br />
This algorithm is referred to in abbreviation as "ITCWB".<br />
<br />
Unlike the majority of white balance algorithms based on gray tones, this one is based on color. Put simply, the algorithm compares a large number of sample colors in the image with a set of reference colors and their associated spectral data. <br />
<br />
=== Origin ===<br />
<br />
This algorithm was developed by Jacques Desmis. It was based off an unpublished research summary, which divides the process up into 3 phases: <br />
<br />
# xyY comparison <br />
# Spectral data analysis<br />
# Color histogram analysis <br />
<br />
These phases form the basis of the algorithm described below, which was developed from scratch and is not based on any existing algorithms or code.<br />
<br />
=== Performance ===<br />
<br />
The performance of the algorithm depends on:<br />
<br />
* The choice of colors in the image obtained by sampling and selecting the dominant colors (skin, sky, plants etc.). <br />
* The determination of certain parameters, which will be used as the basis for the calculations i.e. camera white-balance temperature, which acts on the red and blue components and tint, which acts on the magenta and green components, etc. <br />
* The choice of the RGB channel multipliers and their calculation based on the temperature of the illuminant.<br />
* The calculation of the XY values of the reference colors (spectral data), using an "exact" formula and samples of spectral data at 5nm. Matrix [Color seen] = Matrix [illuminant] * Matrix [color] / Matrix [Observer 2°]. <br />
* Multiple iteration of the calculations taking into account, in equal proportions, the balance between green-magenta and red-blue. <br />
* Rigorous calculations if the illuminant has a CRI (Color Rendering Index) close to 100 i.e. illuminant close to Daylight in the limit 4100K - 12000K or Blackbody from 2000K to 4100K. <br />
* Statistical correlation using a Student's test.<br />
<br />
=== Reference Spectral Colors ===<br />
<br />
The origin and nature of the 200 reference spectral colors:<br />
<br />
* Data found on the web for flowers, foliage. <br />
* A ColorChecker24 or other color patches. <br />
* The 468 calibration chart that I developed for calibration a few years ago. <br />
* The Colorlab utility (Logo Gmbh). <br />
* These colors are distributed almost equally over the entire color palette (Red, Orange, Yellow, Green, Cyan, Blue, Magenta…). <br />
* These colors are also sorted into neutral or close to gray, slightly saturated, pastel and saturated. <br />
* The luminance has little significance because the comparison is made on the chroma component.<br />
<br />
=== General Principles ===<br />
<br />
* Using the RGB values just after demosaicing, 3 tables are generated (Red, Green, & Blue) for 1 pixel out of every 10 in the image (horizontally and vertically). It is possible to change this value if necessary for more precision. The values are then adjusted so that they are in the range 0 to 65535. <br />
* Then we switch to a procedure called "autowb", which is common to both automatic white balance algorithms. It calculates the RGB channel multipliers, and passes on the values to either to "Itcwb" or "rgbgray".<br />
* The parameters that "wbauto" passes on to "Itcwb" include the important reference temperature (the value present in the Exif camera data) and the tint (also present in the Exif data), whose values are limited to the range between 0.77 and 1.30. There is no Daylight or Blackbody illuminant beyond these arbitrary limits and any calculations would therefore be fanciful or false.<br />
<br />
=== Simplified Temperature Correlation Algorithm ===<br />
<br />
# Phase one<br />
## Calculate the RGB multipliers for each temperature between 2000K and 12000K and for the tint. <br />
## Calculate the XY values from the 200 spectral-data values for each temperature. <br />
## Select a temperature data range relative to the reference. <br />
## Calculate the xy values in the form of a histogram and select from among the 158 possible values, the most commonly used colors (skin, sky, etc.) for each temperature. <br />
## Sort the data in ascending numerical order.<br />
## For the most frequently occurring data values, calculate the chromatic values of the image. <br />
## Use the deltaE chroma values to select the reference colors from the 200 available possibilities.<br />
## Calculate the reference RGB values as a function of the reference temperature.<br />
# Phase two<br />
## Calculate the XY values for each selected reference color as a function of temperature and tint.<br />
## Calculate the RGB values of the image from the XY values using the RGB multipliers. <br />
## First calculation of the Student correlation.<br />
## For each tint and temperature range, calculate the channel multipliers and the XY values from the corresponding spectral data. <br />
## Calculate the correlation coefficient as a function of the color green. <br />
## Sort these values.<br />
## Optimize the values to determine the correct temperature and tint values. <br />
## Send these parameters to "wbauto”.<br />
## Display the results and update Improccoordinator.cc.<br />
<br />
=== User-Modifiable Settings ===<br />
<br />
The development branch [https://github.com/Beep6581/RawTherapee/pull/6643 <code>whitebalanceopt</code>] allows one to modify the parameters used by this algorithm.<br />
<br />
By default the settings should be suitable in most cases. However, it is possible to make custom modifications to the operation of the algorithm.<br />
<br />
In the Color / White Balance tab you can make a series of settings appear that allow you to adapt the algorithm. Eventually (I hope) to be able to remove the majority of these settings (perhaps all). The purpose of this provision of these settings (optional) is essentially the development of the algorithm.<br />
<br />
To make these additional settings appear, go to Preferences / Color Management / White balance - Automatic temperature correlation, and check the corresponding box. If "Temperature correlation" is not selected in "White Balance", the choices appear in gray.<br />
<br />
Only the Observer parameter is accessible only in Preferences / options, common to all Rawtherapee. By default it is set to Observer 2°. This parameter has an influence on the color rendering. Observer 10° is recommended.<br />
<br />
==== Relevant Parameters ====<br />
<br />
I think I can give a relevant opinion, being the designer of the algorithm. Nevertheless, I leave the 'door open' to other hypotheses because the colorimetry in general and the adaptation to Rawtherapee can reserve hypotheses.<br />
<br />
Parameters having an influence (a priori):<br />
<br />
* The first is the 3x3 matrix that ensures the conversion of raw Raw data, after demosaicing, into useful data. In Rawtherapee, these indispensable matrices which are used in several algorithms of the Raw part have their origin in Adobe, either they come from Dcraw, or they come from Adobe DNG converter (Tag matrix). How were these matrices obtained by Adobe ? Internal research, link with the manufacturer,... ? One can think that these matrices are built in a common process, and thus that all things being equal, the same scene, under the same illuminant, taken under the same conditions (speed, diaphragm, lens,...), with a common Raw process, must bring usable color data (and not luminance or Dynamic Range) Raw approximately identical (with the possible reserves due to the parameters developed below). That it is a matrix of Bayer, or other, a case of mark X or Y. Obviously there are differences, in particular for the non-Bayer matrices which have a specific demosaicing algorithm, as well as for the optics... but the differences must be minimal.<br />
* The demosaic algorithm also has a (small) influence, especially the algorithms designed to handle noisy images (LMSSE, IGV), and of course the demosaic algorithm for non-Bayer, for example Xtrans-demosaic (Frank Markesteijn's algorithm, and Ingo Weirich).<br />
* Each sensor - associated with a housing - has :<br />
** a specific DR (Dynamic range) - often around 12Ev for older cameras, close to 15 or 16Ev for recent cameras. This DR must have a low impact on the algorithm, the luminance component is almost ignored (otherwise to determine the gamut).<br />
** White-levels and Black-levels : if these 2 components have a strong importance for the whole of the Raw processing, except if they are very badly adjusted, they should not have an influence on the algorithm.<br />
** the gamut of the sensor : I do not know of official documents showing the limits of transcription of the colors. It is reasonable to think that before conversion matrix, these limits are largely sufficient and beyond Prophoto, and thus have no or little influence on the algorithm.<br />
* The nature and intensity of colors: the distribution in the xyY diagram. Are we with an image where the colors are close to the white point (pastel colors or neutral), or images with colors at the limits of those of human perception?<br />
* The distribution of these colors in relation to each of the primary Red / Green / Blue.<br />
* As the algorithm divides the 'xy' space into 236 areas, covering the entire visible space, the algorithm must take into account this distribution: for example a majority of tones very close to the white point (neutral) or a dominant important (sky, or skin).<br />
* And of course the illuminants. An image with parts in the sun and shade is actually with 2 illuminants Daylights (near 5000K in the sun and 7000K in the shade). This is almost insoluble with a single setting of the white balance (temperature, hue). Of course it is even more complex if Fluorescent or LED illuminants are present. But these remarks are not specific to Itcwb, but to all white balance algorithms. Local adjustments (Warm/cool) allows you to correct double illuminants (sun, shadow...) quite well.<br />
* Still on the subject of illuminants, they have a theoretical definition that links spectral data to a temperature. These formulas by principle can not be perfect and respond to all environments: latitude, altitude, time, meteorological conditions (fog, gradients, ...) that must have an impact on the shade (green) that becomes different from 1.<br />
* Observer 2° (1931) or Observer 10° (1964): the second provides a better perception of human vision. It is the one used by default in Itcwb.<br />
* As a reminder, a perceived color with its XYZ data is the combination of 3 matrices:<br />
** spectral data of the illuminant (function of temperature and nature of the illuminant).<br />
** spectral data of the base color (measured with the spectro).<br />
** spectral data of the observer (2° or 10°).<br />
<br />
By principle this algorithm is not designed to correct the malfunctions of the processing (which is always very complex). Of course it can (possibly) correct a problem, but this is not its purpose.<br />
<br />
==== Settings ====<br />
<br />
We can classify these settings in several categories:<br />
<br />
# Those that have a strong or medium impact on the result, related to the composition of the image, or that ensure compatibility with Rawtherapee 5.9: restrient or very wide gamut, strong or weak color dispersion.<br />
# Those which must be checked for the development of the algorithm, but eventually be deleted: they are not accessible through the GUI interface but in the pp3 files.<br />
# Those - if any - whose relevance is to be checked, modifiable only in the C++ code (nevertheless I left in the code the possibility to reuse them in pp3).<br />
<br />
* CIExy diagram and gamut: You can see on the 2 diagrams below, that it is not because a color is in the CIExy diagram that it is in the gamut. <br />
** Example for a luminance of 10 and a luminance of 50 [0..100]. <br />
<br />
[[File:Gamu-comp10.jpg|thumb|Gamut comparison for L=10 : yellow=ACESp0 gray=Prophoto green=sRGB]]<br />
<br />
[[File:Gamu-comp50.jpg|thumb|Gamut comparison for L=50 : yellow=ACESp0 gray=Picture green=sRGB]]<br />
<br />
High and medium impact settings:<br />
<br />
* Force use of entire CIE diagram (strong): by default (unchecked box) the data scanned during sampling is brought back to the sRGB profile, which is the most common one, both for calibrating DCP or ICC profiles with the Colorchecker24, or used on the web. If you have images with very high gamut (some flowers, artificial colors, then it may be necessary to use the entire CIExy diagram, the profile used will be ACESP0. In this second case the number of colors that can be used internally to the algorithm will be more important.<br />
* Sort in chroma order instead of histogram (strong) : If the box is not checked the algorithm will use the data in the order of the frequency of the presence of each color. If the box is checked the order will be from the highest saturation to the lowest.<br />
* Number of color used in picture (average): limits the comparison sampling between spectral data and image data. The default value should be suitable in most cases. Very high gamut images may require high values.<br />
* No purple color used : by default when "Inpaint opposed" is activated, purple colors are not taken into account. However, if the image does not need reconstruction of the highlights, or if this image naturally contains purple tints (flowers...), it may be necessary to deactivate, to take into account all the colors.<br />
* Itcwb_findgreen - Find green student : number of iterations to find the best compromise between the correlation (student) and the value of green which for Daylight / Blackbody illuminants is close to 1. By default : 5. Range of settings taken into account [3..6].<br />
* Low sampling: Hard-code that allows the current algorithm to have a response similar to Rawtherapee 5.9. To ensure a good response, Observer 10° must be activated in 'Preferences / Color Management / White Balance'.<br />
<br />
Parameters to check, to change if necessary in pp3:<br />
<br />
* Itcwb_rangegreen - Geen range: sets the range of examination of the green value in the iterations, from a low range of 0.82 to 1.25 to the maximum range of 0.4 to 4. Default: 1. Range of settings taken into account [0..3]<br />
* Itcwb_delta - Delta temperature in green loop: Sets the temperature difference to be taken into account for each "green" iteration tried. Default: 2. Range of settings taken into account [1..4]<br />
<br />
Possible parameter to change in the C++ code:<br />
<br />
* Variable - int maxnb (Itcwb) - Size of reference color compare to histogram: this setting is mostly important when 'Force use of entire CIE diagram' (or to a lesser degree when 'Sort in chroma order instead of histogram') is enabled. It sets the number of iterations to find the best match between the reference spectral colors and those in xyY value of the image. The value of 3 is a good compromise. Why "possible", because despite the large number of spectral data, especially when we are at the limits of the CIExy diagram, the probability that the reference colors are far from those of the image is strong and can lead to questionable results.<br />
* Variable - int precision (getrgbloc, getAutoWBMultipliersitc) - Precision algorithm - scale used: the lower the value, the more relevant the data. The processing time being low, this parameter is set to 3 by default.<br />
<br />
==== Chromatic Adaptation ====<br />
<br />
The results of the Itcwb algorithm, reflect the relevance of calculations on objective mathematical foundations. but this result - as indeed all settings of the white balance - do not take into account in full human perception: surround, simultaneous contrast, ... and especially the adaptation of our eye / brain to temperature differences from D50 (which is the reference in colorimetry). <br />
To overcome this gap, it is possible to set up a chromatic adaptation "integrated" with the white balance (this is what I had proposed in 2018...) or let the user set up this adaptation with the module "Color Appearance & Lighting".<br />
<br />
To achieve this and limit the role of Ciecam, put Ciecam in "Automatic symmetric" mode, the system will apply 2 chromatic adaptations, the first from "Scene conditions" to the reference illuminant (usually D50, but you can change it), the second from the reference illuminant to "Viewing conditions". By default the 2 adaptation percentages are set to 90%, you can increase or decrease these values. You can also modify the temperature in "Viewing conditions" to obtain a warmer or colder rendering.<br />
You can, if you wish, change the Ciecam settings like "Absolute luminance", "Surround", etc. See the tutorial on Ciecam.<br />
<br />
=== Examples ===<br />
<br />
I have (arbitrarily) chosen these 6 examples, to show what Itcwb can (and cannot) do, associated or not with Color Appearance & Lighting.<br />
<br />
* [https://drive.google.com/file/d/1azCxu1midw6dcuN7SbvbAiJH4pxX5BTA/view?usp=sharing Salt mountain in Turkey] (<code>_ASC4145.NEF</code> CC BY-SA 4.0 Jacques Desmis)<br />
*: This image that seems harmless is complex in terms of photography, for several reasons:<br />
** the white of the salt mountain is difficult to process, and is affected by a complex structure that makes it difficult to process in general. <br />
** The point that interests us here is the white balance and color distribution. The majority of the image sky, trees, mountain is in sRGB, but the flowers at the bottom of the image (red, orange, yellow) are well beyond: how to treat, incidences of settings<br />
* [https://drive.google.com/file/d/1MMNzw3tPQuMeD5baqDlBXRvl4lDy2mLX/view?usp=sharing Lunching Room] (<code>LunchingRoom.CR2</code> CC BY-SA 4.0 Jacques Desmis)<br />
*: This image shows that the algorithm can handle complex situations. <br />
** By default with White Balance set to "Camera" the image is green. <br />
** Try successively, White Balance auto : 'Rgb grey' and "Temperature correlation". <br />
* [https://drive.google.com/file/d/1CiQ2t4KyD3tdCiNNhskqUG2cH9LT2ly7/view?usp=sharing London Bridge] (<code>london_bridge_moving_1.pef</code> CC BY-SA 4.0 Maciej Dworak)<br />
*: This image shows both the need for chromatic adaptation and the relevance of the Itcwb algorithm.<br />
** The default setting 'Camera' gives a green/yellowish cast. <br />
** Itcwb allows to find a good mathematical compromise, but the temperature is high, giving the image a warm coloring, which can be seen on the faces, the deck stays. <br />
** Try Color Appearance in "Automatic symmetric" mode <br />
* [https://drive.google.com/file/d/1YFeoPL-RhStftDCCkbDNlmj8New_SgX0/view?usp=share_link Calibration test pattern] (<code>DSCF5334.RAF</code> CC BY-SA 4.0 RawTherapee)<br />
** I chose this test pattern for two reasons: the first is that it is a RAF file, so it is not a Bayer file; the second is that it contains almost pure whites and blacks (the grays are dominant in the image, which could interfere with the algorithm).<br />
** Nevertheless it does not seem to examine the results (neutral) that the camera has been calibrated (or I do not have the profile), the information is therefore orders of magnitude, but quite close to reality (whites, blacks, ColorChecker)<br />
** Itcwb doesn't know it's a calibration test pattern, try because of the high gamut 'Force use of the entire CIE diagram' on or off, 'Sort in chroma order' off or on and 'no purple used' off - the results are very close to those with Camera (which are better?), but there is no drift.<br />
* [https://drive.google.com/file/d/1iqpj-vT3dqUmaXKOQE7QB_rynf4cbRPC/view?usp=share_link Caribbean Backlight] (<code>DSC02973.ARW</code> CC BY-SA 4.0 Jacques Desmis)<br />
** I chose this image, taken with my old Sony during a trip to the Caribbean, where I had chosen the automatic white balance.<br />
** Try with 'Camera' then 'Itcwb'.<br />
* [https://drive.google.com/file/d/1ZxucMREXAAFlBijiBiBZoH9kG4-O2GYb/view?usp=share_link Using Inpaint-opposed] (<code>Nikon - D800 - 14bit uncompressed (3_2).NEF</code> CC0 1.0 Pascal Obry)<br />
** I chose this image to show the impact of the white balance on "Inpaint opposed" (highlight reconstruction), especially the green (tint) influence<br />
** Try "Inpaint opposed" with White Balance set to Camera, notice the large artifacts in the sky<br />
** Choose "Itcwb" and try various settings.</div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=Toolchain_Pipeline&diff=10100Toolchain Pipeline2023-03-09T12:54:12Z<p>DrSlony: </p>
<hr />
<div><div class="pagetitle">Toolchain Pipeline and Colorimetry</div><br />
<br />
== Toolchain Pipeline ==<br />
<br />
=== Processing Order ===<br />
<br />
Everything that happens to an image, from the moment you open the file to the moment it is displayed on screen or saved, takes place in a fixed order. The data flows from one module to another - this is the toolchain pipeline. RawTherapee contains four pipelines (one for the main preview, one for the saved image, one for the thumbnail, and one other that currently escaped me). The following list shows a simplified order of operations:<br />
<br />
# Preprocess<br />
## Dark frame<br />
## Flat field<br />
## Bad pixels<br />
## Hot pixels<br />
## Scale colors (internal, no tool in UI)<br />
## Raw black point<br />
## Lens distortion correction<br />
## Green equilibration<br />
## Line noise filter<br />
## Chromatic aberration Correction<br />
## Raw white point<br />
## Raw histogram<br />
## Prepare Auto Exposure<br />
# Demosaic<br />
# Retinex<br />
# Highlight recovery<br />
# White balance<br />
# Crop<br />
# Convert colorspace<br />
# Noise reduction<br />
# Dehaze<br />
# Dynamic range compression<br />
# Auto-match tone curve<br />
# (Local Adjustments branch) avoid color shift, Log encoding, blur-noise denoise, tone-mapping, dehaze & retinex, contrast by detail levels, vibrance, soflight, local contrast, wavelet, sharp, exposure, color and light, Color appearance (Cam16 & JzCzhz), avoid color shift<br />
# Tone response curve<br />
# Process RGB<br />
## Channel mixer<br />
## Tone curve<br />
## Highlights<br />
## Shadows<br />
## RGB curves<br />
## HSV curves<br />
## Color toning<br />
## Film simulation<br />
## Black-and-white<br />
## L*a*b* color correction grid (Lab)<br />
# Process Lab<br />
## Shadows/Highlight (Lab)<br />
## Local contrast (Lab)<br />
## Lab adjustements<br />
## Vibrance<br />
## L*a*b* color correction grid (Lab)<br />
## Vignette filter<br />
## Graduated filter<br />
## Tone mapping<br />
## Impulse noise reduction<br />
## Defringe<br />
## Edges<br />
## Microcontrast<br />
## Sharpening<br />
## Contrast by Detail Levels<br />
## Wavelets<br />
## Soft light<br />
## Abstract Profile<br />
## CIECAM02<br />
## Resize<br />
## Post-resize sharpening<br />
# Final Lab -> RGB conversion<br />
<br />
=== List of All Tools in RawTherapee ===<br />
<br />
* Generic/Main preview<br />
** Input profile<br />
** Monitor Color Profile<br />
** Working profile<br />
** Output profile<br />
** Clipping indication<br />
** Red/Green/Blue/Luminosity/Focus mask previews<br />
** Colorimetric intent<br />
* Exposure Tab<br />
** Exposure<br />
** Shadows/Highlights<br />
** Tone Mapping<br />
** Dynamic Range Compression<br />
** Vignette Filter<br />
** Graduated Filter<br />
** Lab Adjustments<br />
* Detail Tab<br />
** Sharpening<br />
** Local Contrast<br />
** Edges<br />
** Microcontrast<br />
** Impulse Noise Reduction<br />
** Noise Reduction<br />
** Defringe<br />
** Contrast by Detail Levels<br />
** Haze Removal<br />
* Color Tab<br />
** White Balance<br />
** Vibrance<br />
** Channel Mixer<br />
** Black-and-White<br />
** HSV Equalizer<br />
** Film Simulation<br />
** Soft Light<br />
** RGB Curves<br />
** Color Toning<br />
** Color Management<br />
* Advanced Tab<br />
** Retinex<br />
** CIE Color Appearance Model 2002<br />
** Wavelet Levels<br />
* Transform Tab<br />
** Crop<br />
** Resize<br />
** Lens/Geometry<br />
*** Rotate<br />
*** Perspective<br />
*** Profiled Lens Correction<br />
*** Distortion Correction<br />
*** Chromatic Aberration Correction<br />
*** Vignetting Correction<br />
* Raw Tab<br />
** Sensor with Bayer matrix<br />
*** Demosaicing<br />
*** Raw Black Points<br />
*** Preprocessing<br />
*** Chromatic Aberration Correction<br />
** Sensor with X-Trans matrix<br />
*** Demosaicing<br />
*** Raw Black Points<br />
** Raw White Points<br />
** Preprocessing<br />
** Dark Frame<br />
** Flat-Field<br />
** Film Negative<br />
** Capture Sharpening<br />
<br />
== Colorimetry ==<br />
<br />
=== The Importance of CIECAM and L*a*b* ===<br />
<br />
Colorimetry gives rise to a lot of debate but we have to remember that it is not an exact science. No amount of equations, however complex, can ensure that the human eye will necessarily be satisfied with an image. <br />
<br />
Currently RawTherapee uses the L*a*b* color space and CIECAM02/16 for chromatic adaptation and work has begun on exploring other color spaces (Jzazbz) and CAM models, for HDR applications (ZCAM does not work)..<br />
<br />
The use of the L*a*b* (or CIELAB) color space does have its limitations but many of its shortcomings can be successfully mitigated, at least for SDR applications.<br />
<br />
For example:<br />
<br />
* One of the most frequent criticisms is that L*a*b* is non-linear and that it "distorts" the colors, in particular for blue-violet and red-orange. This is certainly true if you simply adjust the image using curves or chromaticity sliders. However in RawTherapee, if you click on "Avoid color shift" (Munsell correction), nearly 200 LUTs will correct these shifts and make the image perfectly linear. <br />
* It is also said that L*a*b* addresses imaginary colors if the working profile allows it. This is also true but again, this can be compensated in RawTherapee by enabling "Avoid color shift". In this case, a relative colorimetric correction is applied to the working gamut as follows: <br />
** It analyzes the image data.<br />
** If it is within gamut no action is taken.<br />
** If it is outside gamut,the chroma is reduced and if this is insufficient, or if it is close to L=0 or L=100, then L is adjusted.<br />
** However this should rarely occur if Prophoto is used in the Working Profile and is probably not important.<br />
** If the saturation has been adjusted (chroma, vibrance,…), a Munsell correction using nearly 200 LUTs is applied. This will correct any color shifts with a high degree of accuracy e.g a red that has turned orange because of L*a*b*, will become red again. There will still be some errors but they are very small.<br />
** You can use just the Munsell correction by checking “Munsell correction only”.<br />
<br />
==== L*a*b* ====<br />
<br />
* L*a*b* is a reversible transformation of XYZ (in simplified terms, Y is transformed into L* using a gamma of 3.0 and a slope of 9.03). L*a*b* has more or less the same characteristics in terms of its limits (those of the primaries) as XYZ, which serves as a reference for the Working Profile and determines the basis of the gamut. Therefore L*a*b* and XYZ have essentially the same characteristics (exposure range, gamut, etc.). One point however, in many processes the values of L* can be bounded (clipped), to limit artifacts (high contrasts, highlights...), but in most cases L* is unbounded. If we ever get to HDR processing, we'll probably have to switch to "HDR-Lab". The data is not lost, even for high-dynamic range images (> 15Ev), but the progression in the highlights is not progressive enough when used with monitors capable of displaying luminance values in the range of 120 cd/m² and beyond.<br />
* I don’t think that the RGB->Lab transformation itself prevents complete HDR processing. This is because the calculations are generally carried out using ‘float’ or ‘double’ data values (32 or 64 bits) or using SSE (128 bit - 4x32 or 2x64 bits). The linear part of the Lab transform allows shadows with values of 0.005 cd/m2 or less to be processed. The parabolic part (gamma = 3.0) limits the distribution of data in the highlights allowing them to be reproduced more accurately (on suitable monitors) with luminance values above 120 cd/m2. The XYZ<=>Lab conversion leads to hardly any loss of data (insignificant due to double conversions) and can be considered as a kind of lossless compression. Of course if we want to achieve complete HDR processing, it is necessary to ensure that the way the data is processed, prior to being sent to the monitor, allows for more progression in the highlights. The preferred approach for Rawtherapee would be to implement HDR-Lab instead of Lab. But in the meantime I have implemented the possibility of changing the gamma of Lab (3.0) for several tools (wavelets, tone-mapping, etc.) notably to make it linear. It should be noted that Rawtherapee is designed to overcome one of the problems with Lab, which is the non-preservation of the hue when the saturation changes (especially in oranges and purples), by using "Perceptual Uniform Lab". This involves using a series of Munsell LUTs, as well as gamut control to prevent virtual colors.<br />
<br />
==== CIECAM02/16 ====<br />
<br />
* One criticism of Ciecam02 is that is not able to process high dynamic range and wide color gamut images, which is partially true. A number of improvements were made by the development team a few years ago to mitigate this problem (bearing in mind that a large number of user images fall within the sRGB gamut and do not pose a problem). However, by using Log Encoding in conjunction with Cam16, or Color appearance (Cam16 & JzCzHz), the vast majority of problems can be solved. Of course some images will still present problems, in particular with highlight reconstruction, but this is not specific to Ciecam. The addition of Ciecam16 (Cam16) solves some of these problems.<br />
* Ciecam02/16 is one of the only ways to achieve true colorimetric correction because it takes into account human perception and the surrounding environment. With Ciecam for example, any adjustments to the luminosity and/or the saturation, will take into account the image and its environment.<br />
<br />
==== White Balance ====<br />
<br />
* White balance is also subject to debate. The Temperature Correlation module recently introduced in Rawtherapee is almost mathematically (cognitively) perfect. It makes the xyY colors of the image coincide with known spectral data. However, on images where the temperature deviates a long way from D50, the colorimetry will not be correct because there will not be the necessary chromatic adaptation expected by our eyes and brain. Ciecam however, can take this into account.<br />
<br />
=== Importance of the Linear-RGB Model and Colorimetry ===<br />
<br />
The merits of the RGB model, and in particular, the linear RGB model are frequently cited. It is certainly the best way to carry out “upstream” processing (demosaicing, white balance, defringing, chromatic aberration correction, etc.) and anything that can be done in this mode should be.<br />
<br />
However, CIELAB and Ciecam02/16 still have their place despite their shortcomings. As we have seen above, they are both derived from the CIE XYZ tristimulus values with Ciecam being one of the only ways to achieve true colorimetric correction.<br />
<br />
So what about tone curves?<br />
<br />
* Not only are they non-linear but they only provide limited colorimetric compensation, if any (with the exception of the Perceptual mode, which uses Ciecam02). This is in contrast to the Tone Response Curves -TRC- used for output (monitor, TIF etc.).<br />
* The Auto-Matched Tone Curve, which is a copy of the in-camera TRC, is applied mid-process and introduces non-linearities in the processing pipeline.<br />
<br />
What about saturation?<br />
<br />
* Maintaining RGB linearity when you change the saturation is not impossible but it is difficult and is not implemented in Rawtherapee. On the other hand, if you adjust the saturation using Ciecam, it will take into account variations in luminance (or brightness) and adapt the color accordingly.<br />
<br />
In conclusion, RGB, L *a *b *, and Ciecam all have their advantages and disadvantages. They simply need to be understood so that they can be used appropriately.</div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=Noise_Reduction&diff=10099Noise Reduction2023-03-09T12:38:35Z<p>DrSlony: Updated URL</p>
<hr />
<div><div class="pagetitle">Noise Reduction</div><br />
<br />
{{1:1}}<br />
<br />
== Introduction ==<br />
<br />
[[File:Noise-cactus-0-ba.png|thumb|600px|Before and after noise reduction.]]<br />
<br />
Photography is based on recording light which falls on a medium during an exposure. The medium is typically film or a digital sensor. The light signal ''recorded'' on the medium is not an ideal representation of the signal which ''fell upon'' that medium - these differences constitute noise. Film and digital photographs alike are susceptible to noise (called "grain" in film), however there are various types of noise from various sources specific to each medium.<br />
<br />
In order to effectively deal with mitigating noise it is useful to understand what types of noise exist and where they come from. The topic of noise is well explained in this paper by one of RawTherapee's developers and physics professor at the Enrico Fermi Institute, Emil J. Martinec:<br />
[https://homes.psd.uchicago.edu/~ejmartin/pix/20d/tests/noise/index.html Noise, Dynamic Range and Bit Depth in Digital SLRs]<br />
<br />
Light consists of packets of energy called photons. A [https://en.wikipedia.org/wiki/Image_sensor digital sensor] comprises of millions of light-sensitive elements called ''photosites'' (also known as ''sensels'' - sensor elements). Each photosite is capable of recording a signal from a certain range of photons - too few and the photosite will not register anything; too many, and the photosite will "clip" to pure white (completely overexposed). Think of it as a bucket collecting water - despite there being moisture in the air, if it doesn't rain then the bucket is empty, but if it rains too much then it overflows.<br />
<br />
Note that the idea of "pixel" does not exist at this point yet - information from several photosites will later be combined into one pixel during a process called [[demosaicing]]. Also note that some sources do write "pixels" when they mean "photosites".<br />
<br />
The physical sensitivity of the sensor is constant, however the photographer can amplify the recorded signal by modifying a setting you know as ISO (see the [https://en.wikipedia.org/wiki/Film_speed Film Speed] article on Wikipedia). Since the signals recorded by the sensor are not perfect, using a higher ISO amplifies not only the desired signal, but also the noise. Sensors are susceptible to noise at every ISO level, however the higher the ISO the more apparent the noise.<br />
<br />
There are different tools for dealing with different types of noise:<br />
* The Noise Reduction tool is best at dealing with photon shot noise ([https://en.wikipedia.org/wiki/Gaussian_noise Gaussian] and [https://en.wikipedia.org/wiki/Shot_noise Poisson] noise) and film grain, and some sensor read noise.<br />
* Sensor read noise and thermal noise are best handled by the [[Dark-Frame]] tool.<br />
* Salt and pepper noise (sudden white or black pixels) is best handled by the [[Impulse Noise Reduction]] tool.<br />
* Hot and dead pixels are best dealt with using the [[Preprocessing#Hot.2FDead_Pixel_Filter|Hot/Dead Pixel Filter]].<br />
* Pattern noise (periodic, anisotropic) is best handled by the [[Preprocessing#Line_Noise_Filter|Line Noise Filter]]. You can also fix pattern noise (de-screen) after RawTherapee in GIMP, using the Fourier transform in G'MIC.<br />
<br />
Regardless the source, noise will manifest itself as blotches of deviating color - "chrominance noise", and deviating brightness - "luminance noise".<br />
# Chrominance noise is endemic to digital images, it is generally unattractive and something you will always want to remove.<br />
# Luminance noise, on the other hand, looks like film grain and can be attractive, so it's not uncommon to want to remove chrominance noise but keep luminance noise.<br />
<br />
<div align="center"><br />
<gallery caption="Examining Noise" mode=nolines widths=600px heights=450px><br />
File:noise-wall.png|A noisy test photo taken at ISO 6400.<br />
File:Noise-wall-demosaic-amaze.png|AMaZE demosaicing leads to small maze-like patterns.<br />
File:Noise-wall-demosaic-lmmse.png|LMMSE demosaicing avoids maze-like patterns while preserving detail.<br />
File:Noise-wall-luminance100-chrominance-off.png|This is what chrominance noise looks like. Luminance detail was obliterated to make the chrominance noise more clear. Notice the color blotches in what should be a smooth wall.<br />
File:Noise-wall-luminance100-chrominance-on.png|Enabling chrominance noise reduction eliminates the colored blotches.<br />
File:Noise-wall-chrominance.png|This is what luminance noise looks like. Chrominance noise was removed to make the luminance noise more clear.<br />
File:Noise-wall-luminance-tweaked-chrominance-on-median-off.png|Both chrominance and luminance noise were removed.<br />
File:Noise-wall-luminance-tweaked-chrominance-on-zoom-median-off.png|Tiny pixel-sized artifacts are left-over from noise reduction.<br />
File:Noise-wall-luminance-tweaked-chrominance-on-zoom-median-on.png|These artifacts can be removed using the median filter.<br />
</gallery><br />
</div><br />
<br />
Not everyone's requirement for good noise reduction is the same. Some like a completely clean, smooth result, while others prefer to have some grain left over to give the photo a more film-like quality. RawTherapee's powerful ''Noise Reduction'' tool caters to all your needs - it lets you eliminate noise while retaining detail. It uses [http://en.wikipedia.org/wiki/Wavelet wavelets], a [https://en.wikipedia.org/wiki/Fourier_transform Fourier transform] and a [https://en.wikipedia.org/wiki/Median_filter median filter] to work its magic. Read on to learn how to use it efficiently.<br />
<br />
== Usage ==<br />
<br />
This section details the order of operations for removing noise.<br />
<br />
# Start by ensuring you're using the optimal demosaicing algorithm. AMaZE is recommended for general RawTherapee use, however, when working with very noisy, high-ISO images, it is recommended to use the LMMSE or IGV demosaicing methods instead. AMaZE can lead to tiny maze-like artifacts appearing in very noisy images, whereas LMMSE and IGV are designed to prevent that from happening.<br />
# Check the sharpening tools to make sure that you're not sharpening any fine detail, because your noisy photo has no fine detail! If you're using [[Contrast by Detail Levels]] or [[Wavelets]], make sure that the first one or two fine-detail contrast sliders are at 0 to prevent these tools from amplifying noise.<br />
# Zoom into the photo to 100% or more and find an area that has both sharp, in-focus parts as well as large, plain or out-of-focus ones, so that you have a good overview of the effects of the tool.<br />
# Enable the [[Preprocessing#Hot.2FDead_Pixel_Filter|Hot/Dead Pixel Filter]] if you notice salt-and-pepper noise (black and/or white pixels).<br />
# Enable the Noise Reduction tool. Chrominance noise is automatically removed and usually does not require any tweaking. At this point the remaining noise looks more like film grain. If you are happy with keeping it then you are done, else keep reading.<br />
# To remove luminance noise, set the ''Detail recovery'' slider to 0, and increase the ''Luminance'' slider until the noise has been smoothed-away.<br />
# Increase the ''Detail recovery'' slider until you regain a satisfactory level of detail.<br />
# You may notice some small artifacts remain from the noise reduction process. Use the Median filter to remove them.<br />
# While it is generally not recommended to combine sharpening with noise reduction, RawTherapee-5.5 has a "contrast threshold" adjuster in the [[Sharpening]] tool, thanks to which you can sharpen details while preserving the smoothness of uniform, flat areas.<br />
<br />
<div align="center"><br />
<gallery caption="Noise Reduction Step by Step" mode=nolines widths=600px heights=450px><br />
File:Noise-cactus-1-amaze.png|The noisy image.<br />
File:Noise-cactus-2-lmmse.png|Changing the demosaicing method to LMMSE eliminates the small maze-like patterns and makes the salt-and-pepper noise more clear.<br />
File:Noise-cactus-3-pixelfilter.png|Enabling the [[Preprocessing#Hot.2FDead_Pixel_Filter|Hot/Dead Pixel Filter]] eliminates the salt-and-pepper noise.<br />
File:Noise-cactus-4-nr-chroma.png|Enabling automatic chromaticity noise reduction renders a pleasantly-grainy image.<br />
File:Noise-cactus-5-nr-luminance.png|Luminance noise was smoothed-away using the ''Luminance'' slider.<br />
File:Noise-cactus-6-nr-detailrecovery.png|Detail was restored using the ''Detail recovery'' slider.<br />
File:Noise-cactus-7-nr-median.png|The median filter was used to eliminate left-over artifacts.<br />
File:Noise-cactus-8-sharpen.png|Sharpness was restored using an unsharp-mask with a contrast threshold to prevent sharpening areas which should be smooth.<br />
</gallery><br />
</div><br />
<br />
== Interface ==<br />
<br />
=== General ===<br />
<br />
Closely examine large areas of strong saturation with fine detail - such as the pattern on a colored shirt or the petal of a flower - as you switch between the RGB and L*a*b* spaces.<br />
<br />
The following images demonstrate the effects of various types of noise reduction, exaggerated for clarity. While the source image does not contain any very-low-frequency ''noise'', it was chosen because it does display the effects (and side-effects) very well.<br />
<br />
<div align="center"><br />
<gallery caption="Comparison of Noise Reduction - Color Spaces" mode=nolines widths=600px heights=450px><br />
File:Noise-handkerchief-1-off.png|The noisy image. Detail recovery will be intentionally left at 0, and chromaticity strength will be intentionally set very high, to emphasize effect.<br />
File:Noise-handkerchief-2-luminance-lab-conservative.png|Luminance noise reduction in L*a*b* space, conservative.<br />
File:Noise-handkerchief-3-luminance-lab-aggressive.png|Luminance noise reduction in L*a*b* space, aggressive.<br />
File:Noise-handkerchief-4-luminance-rgb-conservative.png|Luminance noise reduction in RGB space, conservative.<br />
File:Noise-handkerchief-5-luminance-rgb-aggressive.png|Luminance noise reduction in RGB space, aggressive.<br />
File:Noise-handkerchief-6-chrominance-lab-conservative.png|Chrominance noise reduction in L*a*b* space, conservative.<br />
File:Noise-handkerchief-7-chrominance-lab-aggressive.png|Chrominance noise reduction in L*a*b* space, aggressive. Notice how colors bleed one into another in areas where one hue meets the other - navy blue bleeds into cyan, green bleeds into dull-red, dull-red bleeds into crimson-red, etc.<br />
File:Noise-handkerchief-8-chrominance-rgb-conservative.png|Chrominance noise reduction in RGB space, conservative.<br />
File:Noise-handkerchief-9-chrominance-rgb-aggressive.png|Chrominance noise reduction in RGB space, aggressive. Low-frequency detail is lost.<br />
</gallery><br />
</div><br />
<br />
==== Color Space ====<br />
<br />
Noise reduction can be performed in the L*a*b* and RGB color spaces.<br />
<br />
When working in the L*a*b* space, the L* channel is used for luminance and the a* and b* channels are used for chromaticity.<br />
<br />
When working in the RGB space, the Y from the CIE XYZ color space is used for luminance and (X-Y) and (Y-Z) are used for chromaticity.<br />
<br />
==== Mode ====<br />
<br />
There are two general noise reduction modes which control whether only high frequency or also low frequency noise is removed. ''Low frequency'' noise is noise whose blotches cover a large area; conversely, ''high frequency'' noise has smaller blotches which cover fewer pixels.<br />
# Conservative - removes all except very low-frequency noise, so color detail is better preserved at the expense of not removing very large blotches. Use in most cases.<br />
# Aggressive - removes also very low-frequency noise at the expense of being more aggressive with higher frequency noise. Use only on extremely noisy photos.<br />
<br />
==== Gamma ====<br />
<br />
Gamma varies noise reduction strength across the range of tones. Smaller gamma values let noise reduction affect all tones emphasizing the action on shadows, while higher gamma values limit the effect to brighter tones only.<br />
<br />
=== Luminance ===<br />
<br />
[[File:Rt nr luminancecurve books.jpg|thumb|600px|The Luminance Curve in RawTherapee-4.1 was used to completely remove noise in dark areas while fully retaining structure of lighter areas.]]<br />
<br />
"Luminance control" lets you choose whether you want to manipulate the luminance noise reduction via sliders or a curve.<br />
<br />
Adjusting the "Luminance" slider is equivalent to manipulating the amplitude of the luminance curve - both affect how strong the noise reduction effect is. The curve has the additional advantage of letting you control noise reduction strength as a function of the pixels' luminance - e.g. it allows you to have strong luminance noise reduction in the shadows and none in the highlights.<br />
<br />
The "Detail recovery" slider allows you to recover structure while not reintroducing noise, unless you set this value too high.<br />
<br />
=== Chrominance ===<br />
<br />
; Method<br />
Chrominance noise reduction can be performed using one of three methods:<br />
* Manual<br />
* Automatic global<br />
* Preview<br />
<br />
; Preview noise<br />
The "Preview noise" indicator gives the estimated chromatic noise values after "Chrominance" processing:<br />
* Mean: estimates the average noise value across all channels.<br />
* High: estimate the highest noise value across all channels.<br />
<br />
==== Manual ====<br />
<br />
The three sliders and the curve act on the full image. You control the settings manually.<br />
<br />
; Master<br />
Controls the strength of chrominance noise reduction. Functions as an offset independently to the red-green and blue-yellow values. For example if master=50, red-green=-50 and blue-yellow=-50, the end result is 0; no effect.<br />
<br />
; Red-Green<br />
Reduce/boost noise reduction in the red-green channel (a* in L*a*b*).<br />
<br />
; Blue-Yellow<br />
Reduce/boost noise reduction in the blue-yellow channel (b* in L*a*b*).<br />
<br />
<br />
; Chrominance curve<br />
The chrominance curve lets you control chrominance noise as a function of the pixels' chrominance - e.g. it allows you to have strong chrominance noise reduction in areas of low saturation and weak noise reduction in areas of high saturation. This curve modulates the "Master", "Red-Green" and "Blue-Yellow" sliders' action by multiplying their values by the curve ordinate. For example, if the master slider is set to 30 and the curve is at mid-height, the equivalent result will be about 45. It can be useful to boost noise reduction in grey or drab areas, as we distinguish noise more easily in areas of low saturation than we do in areas of high saturation. When using the "automatic global" noise reduction method, the automatically-calculated parameters are an average for the whole image, and they might be insufficient to remove noise in these low-saturation areas - the chrominance curve can help.<br />
<br />
==== Automatic Global ====<br />
<br />
The algorithm splits the image into multiple cells. For each cell the following are calculated:<br />
* An average noise level for the red-green channel and the blue-yellow channel.<br />
* A maximum noise level for the same channels.<br />
<br />
==== Preview ====<br />
<br />
This method is only operational when zoomed to 100% or more. It analyzes the areas currently visible in the preview (if you are zoomed to 100% or more) and calculates:<br />
* An average noise level for the red-green channel and the blue-yellow channel.<br />
* A maximum noise level for the same channels.<br />
<br />
The three sliders - Master, Red-Green and Blue-Yellow - as well as the "Preview noise" values, are updated accordingly.<br />
<br />
If you would like to keep the currently calculated values then you should switch back to "manual" method, else the values will be re-calculated when you pan or when you copy the profile to other images.<br />
<br />
=== Median ===<br />
<br />
[[File:Rt nr median books.jpg|600px|thumb|The Median filter in RawTherapee-4.1 was used to eliminate artifacts which fit in a 3x3 window left over from the noise reduction process.]]<br />
[[File:Rt nr median zoom books.jpg|thumb|600px|Comparison of noise reduction without and with median filtering, zoomed to 200%. While the filtered image on the right may appear less sharp, notice that the unfiltered image on the left does not really contain any more detail - the noise gives the illusion of sharpness. At the same time, the filtered image when saved to JPEG/92/standard was almost 40% smaller than the unfiltered one (350kB vs 215kB). RawTherapee-4.1.]]<br />
<br />
Use this filter to remove tiny, sharp-looking artifacts left-over from noise reduction.<br />
<br />
; Median Type<br />
The [https://en.wikipedia.org/wiki/Median_filter median filter] replaces each pixel with the median value of its neighboring pixels. The contiguous group of pixels being sampled is called the "windows". This window slides pixel by pixel over the entire image. You can choose the size of this window using the "Median type" drop-down. The larger the size, the longer it takes.<br />
<br />
Available window sizes:<br />
* 3x3 soft: treats 5 pixels in a 3x3 pixel window.<br />
: ○●○<br />
: ●●●<br />
: ○●○<br />
* 3x3: treats 9 pixels in a 3x3 pixel window.<br />
: ●●●<br />
: ●●●<br />
: ●●●<br />
* 5x5 soft: treats 13 pixels in a 5x5 pixel window.<br />
: ○○●○○<br />
: ○●●●○<br />
: ●●●●●<br />
: ○●●●○<br />
: ○○●○○<br />
* 5x5: treats 25 pixels in a 5x5 pixel window.<br />
: ●●●●●<br />
: ●●●●●<br />
: ●●●●●<br />
: ●●●●●<br />
: ●●●●●<br />
* 7x7: treats 49 pixels in a 7x7 pixel window.<br />
: ●●●●●●●<br />
: ●●●●●●●<br />
: ●●●●●●●<br />
: ●●●●●●●<br />
: ●●●●●●●<br />
: ●●●●●●●<br />
: ●●●●●●●<br />
* 9x9: treats 81 pixels in a 9x9 pixel window.<br />
: ●●●●●●●●●<br />
: ●●●●●●●●●<br />
: ●●●●●●●●●<br />
: ●●●●●●●●●<br />
: ●●●●●●●●●<br />
: ●●●●●●●●●<br />
: ●●●●●●●●●<br />
: ●●●●●●●●●<br />
: ●●●●●●●●●<br />
<br />
Sometimes it is possible to achieve higher quality running several iterations with a small window size than one iteration with a large window size.<br />
<br />
;Median Method<br />
You have five methods at your disposal:<br />
* Luminance only: works in the L*a*b* space, but only affects the L* channel.<br />
* Chroma only: works in the L*a*b* space, but only affects the a* and b* channels.<br />
* Weighted L* (little) + a*b* (normal): affects all channels in the L*a*b* space, but acts more weakly on the L* channel.<br />
* L*a*b*: affects all channels equally.<br />
* RGB: works in the RGB space, and the window size choice is limited to 3x3 soft, 3x3 and 5x5.<br />
<br />
When using the "Luminance only" and "L*a*b*" methods, median filtering will be performed just after the wavelet step in the noise reduction pipeline. When using the RGB color space, it will be performed at the very end of the noise reduction pipeline.<br />
<br />
You may wonder what other uses median filtering has apart from the elimination of pixels which strongly differ from their surrounding neighbors for aesthetic reasons. One of these benefits is a reduction in file size when saving to compressed formats such as JPEG and PNG. Median filtering removes variations which you will lose anyway if you downscale the image. You are also likely not to see these variations if you print the image. Removing them using median filtering can reduce the file size by even 40% (tested using JPEG compression strength 92 with "balanced quality" [https://en.wikipedia.org/wiki/Chroma_subsampling chroma subsampling]), so give it a try if output file size is a factor.<br />
<br />
Finally, the "chroma only" median filter method can be used as a complement to automatic chrominance noise reduction calculation - by reducing sharp outliers it can soften the calculated values, thereby avoiding fading out color detail too much.</div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=Edges_and_Microcontrast&diff=10098Edges and Microcontrast2023-03-09T12:36:05Z<p>DrSlony: </p>
<hr />
<div><div class="pagetitle">Edges and Microcontrast</div><br />
__TOC__<br />
{{1:1}}<br />
<br />
==General==<br />
<br />
{{Sharpening_gallery}}<br />
<br />
Unlike ''[[Sharpening#Unsharp_Mask|Unsharp Mask]]'', ''Edges'' is a true sharpening algorithm. It does not introduce halos, it can be used on noisy images and it works in the Lab color space. It emphasizes only the edges, and can be combined with [[Edges_and_Microcontrast#Microcontrast|Microcontrast]] to also enhance the texture.<br />
<br />
Both algorithms were originally implemented by [https://github.com/ManuelLlorens Manuel Llorens].<br />
<br />
== Edges ==<br />
<br />
This tool sharpens any edges that have sufficient contrast for them to be considered an edge. In other words, it sharpens edges that are already sharp, ignoring edges that do not have enough contrast. The algorithm is not affected by image noise and does not generate halos.<br />
<br />
This type of sharpening can make the edges look a bit unnatural, as if they had been "cut out". Also, if the settings are too high, the resulting edges may exhibit [https://en.wikipedia.org/wiki/Aliasing Aliasing]. This is why you should be careful when applying it to images with curved edges. However, when straight lines predominate (especially if they are not diagonal), it is a useful method of sharpening, especially if you reduce the size of the image at the end of processing.<br />
<br />
To get the best results, the following settings are recommended:<br />
# Iterations: number of iterations carried out by the algorithm. A high number produces an overly sharp effect around the edges. With a value set to 2 this problem can already be observed in some cases. In general, 1 or 2 iterations give the best results.<br />
# Quantity: number of adjacent pixels to be analyzed when deciding what constitutes an edge. Higher values produce sharper edges and a greater "saw-tooth" effect.<br />
# Luminance only: the tool works in the L*a*b* color space and with this option, only the L* component is enhanced.<br />
<br />
[[File:edges.jpg|thumb|"Edges" demonstration. Original image on the left, "Edges" on the right. The arrows indicate much sharper edges, though a saw-tooth effect is visible if you look very closely.]]<br />
<br />
Additional information can be found here: [https://web.archive.org/web/20110625093654/http://www.rawness.es/sharpening/?lang=en www.rawness.es/sharpening]<br />
<br />
== Microcontrast ==<br />
<br />
"Microcontrast" can be defined as contrast on a pixel level[https://web.archive.org/web/20110625093654/http://www.rawness.es/sharpening/?lang=en#comment-306], as opposed to "local contrast" which pertains to contrast between larger (lower frequency) areas.<br />
<br />
The Microcontrast tool increases the contrast of a pixel relative to its neighbors, effectively leading to an apparent increase in texture. The intention is to allow recovering texture lost due to noise reduction. It does not introduce halos.[https://web.archive.org/web/20100324142513/http://www.rawness.es/contraste-local-y-microcontraste/?lang=en]<br />
<br />
[[File:seagull-microcontrast.jpg|thumb|"Microcontrast" demonstration.]]<br />
<br />
The tool's controls are progressive and allow you to choose a balance between increasing the contrast at the pixel level and the appearance of artifacts:<br />
<br />
* Contrast threshold: sets the minimum contrast at which the tool will act on the pixels.<br />
* Quantity: the intensity of the effect. The higher the value, the greater the difference between the pixels.<br />
* Uniformity: to the left, the algorithm tends to respect the initial contrast gradients. To the right, the contrasts are more intense and the initial contrast gradients are ignored, which makes the image harsher.<br />
* Matrix: defines the area that will be used to calculate the contrast variation. There are two possibilities, a 3x3 pixel matrix around the pixel being analyzed, or a 5x5 pixel matrix. By default, it will be 5x5, giving a more intense effect, the 3x3 matrix will be more appropriate for noisy images.</div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=Edges_and_Microcontrast&diff=10097Edges and Microcontrast2023-03-09T12:35:38Z<p>DrSlony: </p>
<hr />
<div><div class="pagetitle">Edges and Microcontrast</div><br />
__TOC__<br />
{{1:1}}<br />
<br />
==General==<br />
<br />
{{Sharpening_gallery}}<br />
<br />
Unlike ''[[Sharpening#Unsharp_Mask|Unsharp Mask]]'', ''Edges'' is a true sharpening algorithm. It does not introduce halos, it can be used on noisy images and it works in the Lab color space. It emphasizes only the edges, and can be combined with [[Edges_and_Microcontrast#Microcontrast|Microcontrast]] to also enhance the texture.<br />
<br />
Both algorithms were originally implemented by [https://github.com/ManuelLlorens Manuel Llorens].<br />
<br />
== Edges ==<br />
<br />
This tool sharpens any edges that have sufficient contrast for them to be considered an edge. In other words, it sharpens edges that are already sharp, ignoring edges that do not have enough contrast. The algorithm is not affected by image noise and does not generate halos.<br />
<br />
This type of sharpening can make the edges look a bit unnatural, as if they had been "cut out". Also, if the settings are too high, the resulting edges may exhibit [https://en.wikipedia.org/wiki/Aliasing Aliasing]. This is why you should be careful when applying it to images with curved edges. However, when straight lines predominate (especially if they are not diagonal), it is a useful method of sharpening, especially if you reduce the size of the image at the end of processing.<br />
<br />
To get the best results, the following settings are recommended:<br />
# Iterations: number of iterations carried out by the algorithm. A high number produces an overly sharp effect around the edges. With a value set to 2 this problem can already be observed in some cases. In general, 1 or 2 iterations give the best results.<br />
# Quantity: number of adjacent pixels to be analyzed when deciding what constitutes an edge. Higher values produce sharper edges and a greater "saw-tooth" effect.<br />
# Luminance only: the tool works in the L*a*b* color space and with this option, only the L* component is enhanced.<br />
<br />
[[File:edges.jpg|thumb|"Edges" demonstration. Original image on the left, "Edges" on the right. The arrows indicate much sharper edges, though a saw-tooth effect is visible if you look very closely.]]<br />
<br />
Additional information can be found here: [https://web.archive.org/web/20110625093654/http://www.rawness.es/sharpening/?lang=en www.rawness.es/sharpening]<br />
<br />
== Microcontrast ==<br />
<br />
"Microcontrast" can be defined as contrast on a pixel level[https://web.archive.org/web/20110625093654/http://www.rawness.es/sharpening/?lang=en#comment-306], as opposed to "local contrast" which pertains to contrast between larger (lower frequency) areas.<br />
<br />
The Microcontrast tool increases the contrast of a pixel relative to its neighbors, effectively leading to an apparent increase in texture. The intention is to allow recovering texture lost due to noise reduction. It does not introduce halos.[https://web.archive.org/web/20100324142513/http://www.rawness.es/contraste-local-y-microcontraste/?lang=en]<br />
<br />
[[File:seagull-microcontrast.jpg|thumb|Example of Microcontrast.]]<br />
<br />
The tool's controls are progressive and allow you to choose a balance between increasing the contrast at the pixel level and the appearance of artifacts:<br />
<br />
* Contrast threshold: sets the minimum contrast at which the tool will act on the pixels.<br />
* Quantity: the intensity of the effect. The higher the value, the greater the difference between the pixels.<br />
* Uniformity: to the left, the algorithm tends to respect the initial contrast gradients. To the right, the contrasts are more intense and the initial contrast gradients are ignored, which makes the image harsher.<br />
* Matrix: defines the area that will be used to calculate the contrast variation. There are two possibilities, a 3x3 pixel matrix around the pixel being analyzed, or a 5x5 pixel matrix. By default, it will be 5x5, giving a more intense effect, the 3x3 matrix will be more appropriate for noisy images.</div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=Graduated_Filter&diff=10096Graduated Filter2023-03-09T12:28:39Z<p>DrSlony: Removed image references as someone deleted the source images</p>
<hr />
<div>The graduated filter tool simulates a real neutral density graduated filter. These can be used used in for example landscape photography to limit the brightness of the sky. It applies an exposure adjustment in the form of a gradient.<br />
<br />
== Strength ==<br />
<br />
The strength of the filter, in stops.<br />
<br />
== Angle ==<br />
<br />
The angle slider allows to rotate the direction in which gradient is applied.<br />
<br />
== Feather ==<br />
<br />
The feather slider controls the width of the filter’s feather (gradient). At 0 there is no feathering, just a sharp edge which can be useful as a temporary setting when choosing position and angle of the filter. The slider value (0 - 100) specifies the width of the feather as percent of the image diagonal.<br />
<br />
== Center X and Center Y ==<br />
<br />
The Center X and Center Y adjustments moves the center of the filter’s feather (ie the rotation anchor point) horizontally and vertically respectively.</div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=Vignetting_Filter&diff=10095Vignetting Filter2023-03-09T12:22:56Z<p>DrSlony: </p>
<hr />
<div>The vignette filter is intended for adding artistic vignetting to your image. This vignetting filter is placed relative to the crop, if cropping is used.<br />
<br />
For correcting vignetting caused by the lens light fall-off (as opposed to this filter which is not for correction but for artistic effect), use the [[Lens/Geometry#Vignetting_Correction | Vignetting Correction]] filter in the Transform tab, in the Lens/Geometry tool. Even better, use the [[Flat Field]] tool.<br />
<br />
== Strength ==<br />
<br />
The amount of darkening the filter will apply, in stops. The full strength is reached in the corners of the image. If you apply a negative amount the corners will be brightened instead of darkened.<br />
<br />
== Feather ==<br />
<br />
The feather slider controls the width of the feathering. If at 0 only the corners will be feathered and the rest of the image will not be affected by the filter. At 50 the feather reaches halfway to center and the rest is unaffected, and at 100 the feather reaches all the way into the center.<br />
<br />
<gallery caption="Effects of Feather" mode=packed><br />
File:Vignette-filter_4.00_00_50.jpg|Feather = 0<br />
File:Vignette-filter_4.00_99_50.jpg|Feather = 100<br />
</gallery><br />
<br />
== Roundness ==<br />
<br />
The roundness slider controls the geometry of the filter. At 0 the shape is rectangular (with rounded corners), at 50 it is a fitted ellipse, and at 100 it’s circular. Note that if your image is square the fitted ellipse will of course be a circle, so the shape will then not change in the range 50 to 100.<br />
<br />
<gallery caption="Effects of Roundness" mode=packed><br />
File:Vignette-filter_4.00_50_00.jpg|Roundness = 0<br />
File:Vignette-filter_4.00_50_99.jpg|Roundness = 100<br />
</gallery></div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=Vignetting_Filter&diff=10094Vignetting Filter2023-03-09T12:19:03Z<p>DrSlony: </p>
<hr />
<div>[[File:Vignette-filter_4.00_50_50.png|thumb]]<br />
<br />
The vignette filter is intended for adding artistic vignetting to your image. This vignetting filter is placed relative to the crop, if cropping is used.<br />
<br />
For correcting vignetting caused by the lens light fall-off (as opposed to this filter which is not for correction but for artistic effect), use the [[Lens/Geometry#Vignetting_Correction | Vignetting Correction]] filter in the Transform tab, in the Lens/Geometry tool. Even better, use the [[Flat Field]] tool.<br />
<br />
== Strength ==<br />
<br />
The amount of darkening the filter will apply, in stops. The full strength is reached in the corners of the image. If you apply a negative amount the corners will be brightened instead of darkened.<br />
<br />
== Feather ==<br />
<br />
The feather slider controls the width of the feathering. If at 0 only the corners will be feathered and the rest of the image will not be affected by the filter. At 50 the feather reaches halfway to center and the rest is unaffected, and at 100 the feather reaches all the way into the center.<br />
<br />
<gallery caption="Effects of Feather" mode=packed><br />
File:Vignette-filter_4.00_00_50.jpg|Feather = 0<br />
File:Vignette-filter_4.00_99_50.jpg|Feather = 100<br />
</gallery><br />
<br />
== Roundness ==<br />
<br />
The roundness slider controls the geometry of the filter. At 0 the shape is rectangular (with rounded corners), at 50 it is a fitted ellipse, and at 100 it’s circular. Note that if your image is square the fitted ellipse will of course be a circle, so the shape will then not change in the range 50 to 100.<br />
<br />
<gallery caption="Effects of Roundness" mode=packed><br />
File:Vignette-filter_4.00_50_00.jpg|Roundness = 0<br />
File:Vignette-filter_4.00_50_99.jpg|Roundness = 100<br />
</gallery></div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=Dynamic_Range_Compression&diff=10093Dynamic Range Compression2023-03-09T12:14:18Z<p>DrSlony: </p>
<hr />
<div>== Introduction ==<br />
<br />
Dynamic range is the ratio of the largest to the smallest value of a measured signal. In photography it commonly refers to the ratio of the brightest element of a scene to the darkest. An outdoor scene on a very foggy day commonly has very little difference between the brightest and darkest elements, which is known as a ''low dynamic range'' scene. In contrast, an indoor scene with a visible sunny sky through a window is known as a ''high dynamic range'' scene.<br />
<br />
The dynamic range of a scene can easily exceed the dynamic range of the "sensor" that captures the scene. The [https://en.wikipedia.org/wiki/Dynamic_range#Human_perception human visual system] has an adaptive and wide dynamic range (you can see faint stars at night but also bright skies during day). This is very different from the fixed, lower dynamic range of your camera sensor and the (usually even lower) dynamic range of your monitor. As such, photography and image processing needs to deal with mapping high dynamic ranges to lower ones.<br />
<br />
In general there are two ways to handle dynamic range changes: either discard a portion of the data outside the destination range (e.g. clipping highlights), or compress the data so that it fits the destination range. The Dynamic Range Compression tool uses the latter approach based on the [http://www.cs.huji.ac.il/~danix/hdr/ Gradient Domain High Dynamic Range Compression] algorithm developed by R. Fattal and coworkers. This algorithm is often simply referred to as "Fattal", e.g. in Luminance HDR.<br />
<br />
The algorithm uses two parameters to control the compression (&alpha; and &beta;) which can be tuned by the "detail" and "amount" sliders of the tool, respectively. The tool operates in RGB space and is applied right after [[Noise_Reduction|Noise Reduction]] and [[Haze_Removal|Haze Removal]], but before other tone curve adjustments such as the [[Exposure]] controls.<br />
<br />
N.B. There are alternative ways of compressing the dynamic range using other tools. The simplest would be a negative contrast value in the [[Exposure]] tool to reduce (or rather to redistribute) the dynamic range, however the effect would most likely appear flat and unappealing. A curve gives more control over the process, but may need a lot of fine-tuning.<br />
<br />
== Usage ==<br />
<br />
Use this tool when the dynamic range of the photographed scene is too high to be reproduced on your monitor in an aesthetically pleasing way, that is when you find that the difference between the dark tones and the bright tones (the contrast) is so strong that there is a lack of detail in those areas.<br />
<br />
Heads-up panorama stitchers! The effects of this tool depend on the dynamic range (and histogram) of the image being edited. If you are processing a series of images intended for stitching, where each image contains a section of a scene adjacent to the one before it, even if you were to apply identical parameters to these images using this tool, the end results would not be consistent - there would be sudden changes in brightness between adjacent images. Do not use this Dynamic Range Compression tool on the source images. If you need to compress the dynamic range across a series of images in a consistent way, use a curve instead. You can, however, use this tool on the stitched panorama.<br />
<br />
[[File:DRC-Example.jpg|thumb|Demonstration of the effects of the "amount" and "detail" parameters.]]<br />
<br />
== Interface ==<br />
<br />
=== Amount ===<br />
<br />
Sets the strength of the compression. Higher values lead to a narrower dynamic range (you can easily see the effect by observing the histogram).<br />
<br />
=== Detail ===<br />
<br />
Sets how much local contrast is preserved. Positive values reduce the compression in favor of more contrast, negative values reduce the contrast.<br />
<br />
=== Anchor ===<br />
<br />
Biases the compression towards the shadows or highlights, effectively functioning as an exposure compensation.</div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=File:Profile-partial.png&diff=10092File:Profile-partial.png2023-03-09T12:03:05Z<p>DrSlony: DrSlony uploaded a new version of File:Profile-partial.png</p>
<hr />
<div>icons - light - actions</div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=File:Profile-filled.png&diff=10091File:Profile-filled.png2023-03-09T12:02:41Z<p>DrSlony: DrSlony uploaded a new version of File:Profile-filled.png</p>
<hr />
<div>icons - light - actions</div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=RTProfileSelector&diff=10090RTProfileSelector2023-03-09T11:49:56Z<p>DrSlony: </p>
<hr />
<div>The '''RTProfileSelector''' is a RawTherapee plugin that automatically selects custom processing profiles (.pp3 files) based on user-defined rules. The rules are sets of Exif fields and values which are matched against the actual values extracted from the raw files the first time they are opened in RawTherapee. <br />
<br />
<br />
A few things you can automate in RawTherapee through RTProfileSelector:<br />
* Assign your own custom processing profiles to approximatelly match your camera settings (such as "monochrome"/"black-and-white", "vivid color", "film modes", etc.)<br />
* Set noise reduction parameters in RawTherapee according to camera model and ISO value<br />
* Assign lens correction profiles (LCP) based on the lens and camera model used<br />
<br />
<br />
RTProfileSelector is written in C++11 and compiles on both Windows and Linux. Source code and Windows executable can be downloaded from its [https://github.com/marcapelini/RTProfileSelector GitHub repository]. RTProfileSelector uses [http://www.sno.phy.queensu.ca/~phil/exiftool/ ExifTool] for extracting metadata from images.<br />
<br />
For installation procedures and online documentation, please go to the project's [https://github.com/marcapelini/RTProfileSelector/wiki wiki section].</div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=Dynamic_processing_profiles&diff=10089Dynamic processing profiles2023-03-09T11:49:47Z<p>DrSlony: </p>
<hr />
<div>[[File:dynamic-profile-rules-screenshot.png|thumb|The Dynamic Profile Rules panel in RawTherapee-5.4.]]<br />
<br />
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.<br />
<br />
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).<br />
<br />
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<br />
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.<br />
<br />
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.<br />
<br />
In order to invoke the dynamic processing profile chain in batch, after having configured the dynamic profile rules and set the default profile for raw/non-raw photos to "(Dynamic)", select multiple images in the File Browser, right-click any selected image and select "Processing Profile Operations > Reset to Default" in the popup context menu.<br />
<br />
Dynamic profile rules work on the following image metadata:<br />
<br />
; Camera<br />
: 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 (the name is case-insensitive). 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.<br />
<br />
; Lens<br />
: The full lens name. As above, a regular expression can be used by starting with the <code>re:</code> prefix.<br />
<br />
; ISO<br />
: The range of ISO values.<br />
<br />
; Aperture<br />
: The range of apertures of the lens, measured in [https://en.wikipedia.org/wiki/F-number f-stops].<br />
<br />
; Focal length<br />
: The range of focal lengths used, in mm.<br />
<br />
; Shutter<br />
: The range of shutter speeds, in seconds. For example, enter 0.03 for a speed of 1/30".<br />
<br />
; Exposure compensation<br />
: The range of exposure compensation values, in stops.</div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=Creating_processing_profiles_for_general_use&diff=10088Creating processing profiles for general use2023-03-09T11:48:55Z<p>DrSlony: </p>
<hr />
<div>In RawTherapee, we call the sidecar files 'processing profiles'. We supply a bunch of processing profiles with RT, so that you can start off with an existing look and modify it to your liking, saving you some time. One example of such a profile is "Pop 1" - it will make your photo vibrant and lively, lifting the shadows and bringing out detail.<br />
<br />
You can see the whole list of processing profiles in the ''[[The_Image_Editor_Tab | Image Editor]]'' tab, if you expand the ''Processing Profiles'' list. You can also see them if you right-click on a thumbnail in the ''File Browser'' tab and move your mouse over to "''Processing Profile Operations > Apply Profile''".<br />
<br />
Read the short "[[The_Image_Editor_Tab#Processing_Profile_Selector | Processing Profile Selector]]" article to make sure you understand how to make full use of the selector, partial profiles and the fill mode toggle button.<br />
<br />
== Creating Processing Profiles ==<br />
<br />
[[File:Rt filebrowser customprofile.jpg|right|frame|Apply a custom-made processing profile using the context menu in the File Browser (or [[The_Image_Editor_Tab#The_Filmstrip | Filmstrip]]).]]<br />
[[File:Rt imageeditor customprofile cropped.jpg|frame|Apply a custom-made processing profile using the drop-down menu in the [[The_Image_Editor_Tab#Processing_Profile_Selector | Processing Profile Selector]] in the [[The_Image_Editor_Tab | Image Editor]].]]<br />
You can create your own processing profiles and have them shown in the [[The_Image_Editor_Tab#Processing_Profile_Selector | Processing Profile Selector]] drop-down list.<br />
* Open a photo you want to create a good starting point profile for.<br />
* You could start off with the 'Neutral' profile, or make changes to any of the other profiles that come bundled with RawTherapee. Just apply the desired profile to your photo.<br />
* Make the changes you like, remembering that the more specific your tweaks, the fewer photos they will work well with because every photo is different so what works well for one may not work well for another if they differ significantly. For example if your camera has a very low-noise sensor and your lens is not very sharp you could probably enable [[Sharpening|sharpening]], or conversely if your camera has a noisy sensor you may want to apply a certain level of [[Noise_Reduction|noise reduction]] by default. Maybe you'd like to set your name in the [[IPTC Tab|IPTC]] "Author" field and have RawTherapee [[Metadata Copy Mode|copy your metadata changes to the saved files]]. You will generally want to leave the [[White Balance|white balance]] set to "Camera" since your photos will be taken under various lighting.<br />
* When you are done tweaking, click the ''Save Current Profile'' icon [[File:save.png]] in the ''Processing Profiles'' panel. Enter any name; you don't need to specify the extension - RawTherapee will add it for you. To have it appear in the drop-down list you need to save it to the "profiles" sub-folder in the "config" folder - refer to the [[File Paths]] page to find out where this folder is on your system.<br />
* Restart RawTherapee, and now your new processing profile will appear in the drop-down list under "My profiles".<br />
<br style="clear: both"><br />
<br />
== Partial Processing Profiles ==<br />
<br />
[[image:Pp3_partial_window.png|thumb|Save Partial Processing Profile window]]<br />
<br />
Sometimes, you will want to save only a subset of the parameters available, e.g. to avoid storing geometric parameters like rotate, crop and resize. In this case, hold the ''Control'' key while clicking on the ''Save'' button. When you select the output file name and click ''Save'', a window will let you choose which parameters to select. You can then share these profiles with your friends or in our forum.<br />
<br />
Remember that in order for a profile to be universally applicable to all photos of the same scene and situation (baby portrait photos in this example), you need to think of all the variations in all of the baby portrait photos you might want to apply it to. Remember that exposure will vary between shots, even if you shot the baby in a studio, as the little one is likely to be crawling around, and even more so if you upload your profile on the internet for other baby photographers with different cameras and different lighting gear to use, so instead of setting a specific exposure, such as +0.60, you should rather turn on ''Auto Levels''. This applies to all other settings - remember to set just the bare minimum number of options to achieve the effect you want. Leave the rest untouched, as it is very likely that if you had set those other options, they will not apply well to other photos. If your processing profile is meant to make baby face photos look soft and cuddly by a clever mixture of highlight recovery, auto exposure, Lab and RGB tone curves, then don't enable noise reduction (as photos might be shot at different ISO values), don't set custom white balance (as light may have changed between shots), don’t rotate the photo, and so forth. All these superfluous parameters are likely to change between photos and not influence your soft baby look in any way, so turning them on will just litter your profile. Double-check these things before sharing your profiles.<br />
<br />
== Default Raw/Non-raw Processing Profile ==<br />
<br />
To use your own processing profile as the default for raw or non-raw photos, set it under "''Preferences > Image Processing > Default Processing Profile''".<br />
<br />
If you want to use a dynamic profile, then set "Default processing profile for (non/)raw" to "(Dynamic)".</div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=Sidecar_Files_-_Processing_Profiles&diff=10087Sidecar Files - Processing Profiles2023-03-09T11:48:34Z<p>DrSlony: </p>
<hr />
<div>== Introduction ==<br />
<br />
Processing profiles (with a PP3 extension for version 3 or PP2 for the older version 2) are text files which contain all of the tool settings which RawTherapee applies to the associated photo. If you are familiar with other raw processors, you may know their equivalent as "presets". They are stored alongside their associated photos, which is why they are also called [https://en.wikipedia.org/wiki/Sidecar_file sidecar files].<br />
<br />
When you open a folder with photos in RawTherapee's File Browser for the first time, none of the images will have PP3 sidecar files. The thumbnails shown for images which have no processing profile assigned (images which have never been opened or edited) are created from the JPEG image embedded in each raw file. A processing profile is assigned to the image the moment one of these actions are taken:<br />
* You open the photo for [[The Image Editor Tab|editing]].<br />
* You apply a processing profile manually, by using the right-click context menu in the [[The File Browser Tab|File Browser]] or [[The_Image_Editor_Tab#The_Filmstrip|Filmstrip]].<br />
* You apply a [[Dynamic processing profiles|dynamic processing profile]].<br />
<br />
When you open an image for editing, or when a processing profile is assigned, RawTherapee will convert the real raw data into a viewable image. In order to do this, there are many settings which need to be set to ''something'', and what these specific values are depends on:<br />
* Your [[Preferences#Default_Processing_Profile|default processing profile]].<br />
* Your [[Dynamic processing profiles|dynamic processing profile rules]], if any.<br />
* Or on the processing profile you selected from the right-click context menu if you right-clicked on a thumbnail.<br />
<br />
== Sources ==<br />
<br />
Processing profiles come from three quite different sources, though they work in exactly the same way:<br />
* "Bundled profiles".<br />
*: RawTherapee comes with a bundle of profiles. Their purpose is to give you a good starting point, to demonstrate how the tools can be used together. They are the ones you see in the [[The Image Editor Tab#Processing Profile Selector|Processing Profile Selector]] drop-down list's "Bundled profiles" section, in the [[The_Image_Editor_Tab|Image Editor]].<br />
* "My profiles".<br />
*: When you make a processing profile which you want to re-use, for example one which works well with your camera and your style, you can save it so that it also appears in the Processing Profile Selector drop-down list, in the "My profiles" section. To have it appear there, save it to the "profiles" folder within the "config" folder - see the [[File Paths]] article to find it.<br />
* Automatically generated profiles.<br />
*: Whenever you edit an image, the tool settings you want applied to that image are stored in a processing profile that is particular to that image (ranking information, the history panel contents and snapshots are not stored in these files yet, see [https://code.google.com/p/rawtherapee/issues/detail?id=473 issue #473]).<br />
<br />
== Saving ==<br />
<br />
As simply viewing the image requires processing, RawTherapee stores the settings it used to show you the image in a sidecar processing profile. That processing profile also stores all the tool tweaks you made in the Editor tab.<br />
<br />
The processing profile is written to disk:<br />
* When you apply a processing profile manually or using a dynamic profile.<br />
* When you close the current image (the Editor tab) if using [[The_Image_Editor_Tab#Editor_Tab_Modes|Multiple Editor Tabs Mode]] (METM).<br />
* When you close the current image by opening a different image if using [[The_Image_Editor_Tab#Editor_Tab_Modes|Single Editor Tab Mode]] (SETM).<br />
* When you close the current image by closing RawTherapee.<br />
* When you manually save the processing profile using the [[The_Image_Editor_Tab#Processing_Profile_Selector|Processing Profile Selector]] panel in the Editor tab.<br />
* When you use the "force saving current settings to the processing profile" [[Keyboard_Shortcuts|keyboard shortcut]] from the Editor tab.<br />
<br />
If a photo has an associated processing profile, a green check mark will appear over its thumbnail.<br />
<br />
If you have a photo opened in an Editor tab and you make changes to it from the File Browser, the changes are reflected immediately in the Editor tab.<br />
<br />
== Storage ==<br />
<br />
Where the processing profile is stored can be configured in [[Preferences#Processing_Profile_Handling|Preferences > Processing Profile Handling]].<br />
<br />
By default, the processing profile for an image is stored alongside the input image (if you open <code>kitty.raw</code>, a new file <code>kitty.raw.pp3</code> will be created next to it), but they can also be stored in a [[File_Paths|central cache]]. You can choose whether RawTherapee should use the cache, write the processing profile alongside the image, or both, from "''Preferences > Image Processing''". We suggest you store these files alongside your input image files so that if you decide to move the images you can move the processing profiles easily along with them.<br />
<br />
When saving an image you have the option of ticking the "Save processing parameters with image" checkbox. If it is ticked, and if you are working on <code>kitty.raw</code> and saving to a JPG file, then the processing profile used to develop that image will be stored in a file called <code>kitty.jpg.out.pp3</code>. The ".out" part if there so that conflicts do not occur if you are working on a non-raw file.<br />
<br />
== Defaults ==<br />
<br />
The default processing profile used when opening '''non-raw''' images is called "[[Neutral]]". This profile has all tool settings at their neutral values, so they have no effect. Since non-raw images usually have already been processed and are ready for viewing, having RawTherapee not introduce any tweaks by default is the desirable behavior.<br />
<br />
The default profile for '''raw''' photos is called "[[Auto-Matched Curve]]" (from RawTherapee 5.4 onward). This profile makes your raw image look like the out-of-camera JPEG, which is usually a desirable starting point.<br />
<br />
Furthermore, most tools in the Editor tab have a reset button.<br />
* Clicking the reset button resets the tool to its hard-coded neutral value, usually zero.<br />
* Ctrl+clicking the reset button resets the tool to whatever value it had when you opened the image, i.e. the way it was if you rewind the history stack to the top.<br />
<br />
== Partial Processing Profiles and Fill Modes ==<br />
<br />
[[File:Processing-profiles-selector.png|center|frame|The processing profile buttons.]]<br />
<br />
Processing profile storage (saving to a file or copying to memory) and application (loading from a file or pasting from memory) can be partial, where only a subset of the parameters are involved, or full, involving all parameters. These operations are performed using the buttons in the [[Editor#Processing_Profile_Selector|Processing Profile Selector]] located in the top-right corner of the [[Editor]] tab. Clicking these buttons invokes an operation on the full profile, while {{k|ctrl}}+clicking invokes an operation only on a subset of parameters. When a partial operation is invoked, a windows pops up letting you choose which parameters to include. This feature, for instance, allows you to copy only the white balance and noise reduction parameters from one image to another, while omitting all other parameters.<br />
<br />
The processing profile fill mode allows you to decide what happens when you apply (load or paste) a partial processing profile.<br />
<br />
* [[image:Profile-filled.png]] "Fill" mode takes missing values from RawTherapee's hard-coded defaults. For instance, if you apply a partial profile containing only sharpening settings, all of the remaining tools will be set to their default parameters, overwriting any edits you have made.<br />
* [[image:Profile-partial.png]] "Preserve" mode applies only those parameters that are available in the partial profile and leaves missing values unchanged. Using the previous example, only the sharpening settings would be applied and all other parameters would be left intact.<br />
<br />
Most of the profiles that come bundled with RawTherapee are partial profiles. The [[File Paths]] article explains where the processing profiles shown in the drop-down list can be found on your file system.<br />
<br />
== Creating Your Own Processing Profiles ==<br />
<br />
Using certain tools in certain ways may make your processing profile only usable with that specific image. For example if you set a white balance, cropping and rotation, you won't get good results if you apply that profile to an image taken under different lighting with the camera rotated any other way. See the article [[Creating processing profiles for general use]] for advice on how to make processing profiles which can be used on many images.<br />
<br />
== Compatibility ==<br />
<br />
Processing profiles evolve from one version of RawTherapee to the next. We strive to ensure backward compatibility (e.g. a profile created in 5.3 and opened in 5.4 should look the same), but this is not always possible.<br />
<br />
Processing profiles can gain new parameters or lose ones which became obsolete. Tool behavior can also evolve, wherein default values change or in extreme cases the meaning of a value is interpreted differently; an example of this is the noise reduction tool, where a luminance noise reduction value of 10 in RawTherapee-3.0 would lead to a different result in RawTherapee-4.0.10 as the whole noise reduction engine has been greatly improved.<br />
<br />
Consolidating processing profiles into a cache allows one to store isolated copies of the processing profiles per specific version of RawTherapee. In such a case, the cache can be used to re-process photos in order to get the same output as originally intended (but e.g. with a new size or output color space) using the same version of RawTherapee in which the image was originally edited. Whether this is desirable is debatable. Consider that you want to squeeze as much out of your raw files as possible. If two years later you want to go back to an old raw file, perhaps getting the same result as you did two years ago is not the best idea, because RawTherapee's capabilities would have greatly improved in that time, you may have acquired a better monitor, and your taste and skill would also have evolved. Nevertheless, by backing up the whole cache folder, when installing a new version of RawTherapee you retain the option of going back to an older version of RawTherapee in order to get the exact same result.<br />
<br />
The [[File Paths]] article describes where you can find the "''cache''" and "''config''" folders on your system.<br />
<br />
When releasing a major new version of RawTherapee, it may happen that we use a new suffix for the "''cache''" and "''config''" folders. This means that the new version of RawTherapee will not see your old configuration or processing profiles. Though this sounds undesirable, there are good reasons we may (rarely) choose to do that.<br />
* Backward compatibility. There may be changes in behavior between old and new versions of a specific tool. For instance, the effects of the Auto Levels tool have changed (for the better) between versions 4.0.11 and 4.0.12, so if your old processing profiles had it enabled, the results in 4.0.12 will be a little different and may require tuning your old profiles.<br />
* Some users have not checked "[[Preferences]]" in a long time, and their program is tuned for what worked best long ago, not for what works best now. Our defaults are good defaults, we keep them up to date to make RawTherapee look and function well out-of-the-box, so sometimes having RawTherapee start with fresh defaults is a good thing, and it will motivate users to look into "[[Preferences]]" again.<br />
* Some users have never looked inside "[[Preferences]]" in the first place, and are unaware of some of the features that can be unlocked there. As above, fresh defaults will activate these things.<br />
* Some old cache and config files can cause RawTherapee to crash. While we patch the specific cases made known to us, it is safe to assume there will always be cases unknown to us which will still cause instability. Starting with clean cache and config folders mitigates this problem.</div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=Local_Contrast&diff=10086Local Contrast2023-03-09T09:23:27Z<p>DrSlony: Restructured</p>
<hr />
<div>== Introduction ==<br />
<br />
The Local Contrast tool adds local contrast to an image by applying an unsharp mask with a large blur radius. It it an easy way to give an image a little more 'punch'. In effect, the image is blended with a blurred version of itself, amplifying the local tones (highlights get lighter, shadows get darker), thus creating more contrast. The contrast can be tuned by several parameters explained below.<br />
<br />
This tool was first implemented by [http://gmic.eu/ G'MIC] and then ported to RawTherapee. Its effect is applied in L*a*b* space and only on the lightness channel. Its position in the [http://rawpedia.rawtherapee.com/Toolchain_Pipeline processing pipeline] is after the Shadows / Highlight tool and before all other tools that operate in L*a*b* space.<br />
<br />
<div align="center"><br />
<gallery caption="Local Contrast Demonstration" mode=packed widths=600px heights=600px><br />
File:LocalContrast-Off.jpg|Original image.<br />
File:LocalContrast-On.jpg|Local Contrast applied (Radius = 100, Amount = 0.5)<br />
</gallery><br />
</div><br />
<br />
== Interface ==<br />
<br />
=== Radius===<br />
<br />
Determines the extent of the local contrast (i.e. the radius of the blurring). Higher values give a smoother, but stronger contrast. Lower values give a more localized, less pronounced contrast.<br />
<br />
=== Amount ===<br />
<br />
Determines the overall strength of the effect. Higher values amplify the differences between the original image and the blurred image, thereby increasing contrast.<br />
<br />
=== Darkness/Lightness Levels ===<br />
<br />
The "Darkness Level" parameter modifies only those areas of the image that were darkened with respect to the original. Higher values amplify the change (making darker parts even darker), lower values diminish the change. N.B. A value of 0 means the local contrast is only modified by making the image lighter.<br />
<br />
The "Lightness Level" parameter works similarly, but only on areas that were lightened.<br />
<br />
Note that setting both the "Darkness Level" and "Lightness Level" to 0 effectively disables the tool.</div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=Local_Contrast&diff=10085Local Contrast2023-03-09T09:16:43Z<p>DrSlony: Removed imgcomp</p>
<hr />
<div><div class="pagetitle">Local Contrast</div><br />
<br />
The Local Contrast tool adds local contrast to an image by applying an unsharp mask with a large blur radius. It it an easy way to give an image a little more 'punch'. In effect, the image is blended with a blurred version of itself, amplifying the local tones (highlights get lighter, shadows get darker), thus creating more contrast. The contrast can be tuned by several parameters explained below.<br />
<br />
This tool was first implemented by [http://gmic.eu/ G'MIC] and then ported to RawTherapee. Its effect is applied in L*a*b* space and only on the lightness channel. Its position in the [http://rawpedia.rawtherapee.com/Toolchain_Pipeline processing pipeline] is after the Shadows / Highlight tool and before all other tools that operate in L*a*b* space.<br />
<br />
<div align="center"><br />
<gallery caption="Local Contrast" mode=packed widths=600px heights=600px><br />
File:LocalContrast-Off.jpg|Original image.<br />
File:LocalContrast-On.jpg|Local Contrast applied (Radius = 100, Amount = 0.5)<br />
</gallery><br />
</div><br />
<br />
=== Parameters ===<br />
* '''Radius''' determines the extent of the local contrast (i.e. the radius of the blurring). Higher values give a smoother, but stronger contrast. Lower values give a more localized, less pronounced contrast.<br />
* '''Amount''' determines the overall strength of the effect. Higher values amplify the differences between the original image and the blurred image, thereby increasing contrast.<br />
* '''Darkness level''' modifies only those areas of the image that were darkened with respect to the original. Higher values amplify the change (making darker parts even darker), lower values diminish the change. N.B. A value of 0 means the local contrast is only modified by making the image lighter.<br />
* '''Lightness level''' works similarly, but only on areas that were lightened.<br />
<br />
Note that setting both the "Darkness level" and "Lightness level" to 0 effectively disables the tool.</div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=Download&diff=10084Download2023-03-02T18:51:27Z<p>DrSlony: No longer use template</p>
<hr />
<div><!-- In order to prevent the annually recurring situation of someone making a forum post with download links and explanations which end up becoming outdated and only confusing users, this page is the ONLY place which should describe the various download options available to users and testers. It should explain a concept once and only once, and the same concept should not be explained elsewhere. It must be kept current. --><br />
== Stable Releases ==<br />
<br />
Stable builds can be downloaded from [https://rawtherapee.com/downloads '''our website'''] or through your '''package manager'''. Stable builds are tried and tested and suitable for production use.<br />
<br />
== Development Builds ==<br />
<br />
Development builds can be downloaded from our official [https://github.com/Beep6581/RawTherapee/releases/tag/nightly-github-actions '''GitHub repository'''].<br />
<br />
Development build filenames follow this structure:<br />
<br />
<code>RawTherapee_<branch>_[operating-system]_<build-type>.<extension></code><br />
<br />
; Branch<br />
: Each commit happens on a branch. The main branch is called <code>dev</code>. New features are developed on their own branches, and then merged into <code>dev</code> when ready. When in doubt, get <code>dev</code>.<br />
; Operating system<br />
: A build is made for a specific operating system: <code>win64</code> builds run on any modern 64-bit version of Windows, <code>macOS_10.15</code> builds run on the specified version of macOS or newer, and Linux builds which should run on any modern distro omit the OS segment and instead use <code>AppImage</code> as the extension.<br />
; Build type<br />
: The build type is either <code>release</code> or <code>debug</code>. Release-type builds are optimize to run fast, but do not provide any useful information in case of a crash. Conversely, debug-type builds are capable of producing useful information during a crash [https://rawpedia.rawtherapee.com/How_to_write_useful_bug_reports for a bug report], but will run significantly slower. When in doubt, get <code>release</code>.<br />
<br />
Every time the source code is changed, a development build is automatically created. These builds are provided for the sole purpose of allowing you to try out the newest features and the latest fixes, and to report your findings back to us via [https://github.com/Beep6581/RawTherapee/ GitHub] or [https://discuss.pixls.us/c/software/rawtherapee/ the forum].<br />
<br />
Development builds are '''not intended for production use''' and we provide '''no backward or forward compatibility for [[Sidecar_Files_-_Processing_Profiles|sidecar files (pp3)]]''' created using a development build! That means that a sidecar file created using a dev build will very likely lead to different results when used in a stable release or in another dev build. If stability and compatibility are key for you, we always recommend that you use the latest stable release. If you want to make use of a feature or fix present in the latest dev build in production, you have to wait until we release the next stable version.</div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=Getting_Started&diff=10083Getting Started2023-03-02T18:47:05Z<p>DrSlony: Updated Downloads section</p>
<hr />
<div><div class="pagetitle">Getting Started</div><br />
<br />
== Scope ==<br />
<br />
RawTherapee is a powerful cross-platform raw image processing program, released under the GNU General Public License Version&nbsp;3. Started in 2005 by Gábor Horváth, it was released as open-source software in 2010 and has been under development by an international team ever since. RawTherapee has an extensive set of tools specifically aimed at processing photographs. It works very well in conjunction with raster graphics editors, such as Photoshop or GIMP, and a digital asset manager, such as digiKam.<br />
<br />
== Get RawTherapee ==<br />
<br />
Head over to the [[Download]] page to get stable builds for production use or unstable development builds for testing.<br />
<br />
== Start RawTherapee==<br />
<br />
[[File:Rt setm fb.png|thumb|RawTherapee in Single Editor Tab Mode - Vertical Tabs, showing: 1- Main sections: [[File Browser]] (currently opened), Queue, Editor and Preferences. 2- Panels used for navigating to files and folders. 3- Thumbnails of the currently opened folder. 4- Filters to limit the thumbnails shown to only those which match some metadata or state. 5- Thumbnail zooming and info. 6- Quick image operations. 7- Sub-tabs of the File Browser: Filter (currently opened), Inspect (to see a full-sized embedded JPEG preview), Batch Edit (to apply some setting to all selected images) and Fast Export (low quality and bypasses some tools but fast saving - don't use this for typical saving!). 8- Right-click context menu (you will typically use this to apply some processing profile to all selected files).]]<br />
<br />
When you start RawTherapee you will land in the [[File Browser]] tab, and it might be empty. You need to point RawTherapee to where your raw photos are stored. Use the folder tree browser on the left of the ''File Browser'' tab to navigate to your raw photo repository and double-click on the folder to open it. Then double-click on a raw photo to start editing it.<br />
<br />
== Edit your first image ==<br />
<br />
First, a little background. A raw photo contains a dump of sensor data, which makes up the bulk of the raw file. This sensor data does not look like a pretty image, in fact it does not look like anything - it is "raw" data, ergo the name. It must be "cooked" to look like the image you saw through the viewfinder. Your camera cooks the raw data into a pretty image, which it stores as a JPEG file inside the raw file (yes, even when you're shooting in only "RAW" mode as opposed to "RAW+JPEG" mode). Due to this fundamental fact of the data being "raw", there is no one correct way for a raw photo to look - the way your camera makes it look is not "the right way", nor is it the only way. However, many photographers would like to use the "camera look" as a starting point for further adjustments, and RawTherapee makes this possible.<br />
<br />
When displaying a raw photo in the [[File Browser]] which has never been edited in RawTherapee before, the photo's thumbnail is based on the JPEG image embedded inside that raw file -- the exact same image you see when viewing that photo on your camera or in most other software. Once you open that photo in the [[Editor]], RawTherapee creates a new thumbnail based on the actual raw data. Since creating an image from raw data requires "cooking" it, and since you have not manually edited that image yet, RawTherapee uses parameters from the [[Preferences#Default_Processing_Profile|default processing profile for raw photos]] to process it. From that moment on, the photo's thumbnail is no longer based on the embedded JPEG but on the actual raw data. When you make adjustments to the image in the Editor, the thumbnail is updated to reflect your changes.<br />
<br />
Editing is done in the [[Editor]]. This is where you work with RawTherapee to create stunning works of art - or perhaps just apply first aid to your snapshots. When you open a raw photo in the Editor for the first time, the [[Preferences#Default_Processing_Profile|default processing profile for raw photos]] is applied, which as of RawTherapee 5.4 is set to "Auto-Matched Curve - ISO Low" (unless you changed it in Preferences), and it automatically adjusts your raw photo to look like the out-of-camera JPEG. It does so by analyzing the JPEG image which was created by your camera and is stored within the raw file, and adjusting the tone curve so as to match it. In most cases this match is very close to the "camera look". In rare cases it may fail. See the [[Auto-Matched Curve]] article for more information.<br />
<br />
[[File:Rt setm editor.png|thumb|The Editor.]]<br />
<br />
Take a moment to look around this Editor tab.<br />
Notice that there are tabs within this tab - on the right of screen towards the top. These tabs and the controls under them are the Toolbox. You probably have the first tab open and, if you hover your mouse over it, you'll find that it's called the Exposure tab. Below the choice of tabs are the tools the chosen tab contains – Exposure, Shadows/Highlights, Tone Mapping etc. If you click on one of them it will expand so that you can see its contents. Click again and it will collapse. Right-click on one and that one will expand while all others will collapse - a time-saving shortcut. To the left of each tool's label is a power button ([[File:Power-on-small.png]] on / [[File:Power-off-small.png]] off) which lets you turn it on or off, or in some cases instead of a power button there is a triangular expander [[File:Expander-closed-small.png]]. Read the [[General_Comments_About_Some_Toolbox_Widgets#Tools|Tools section of the General Comments About Some Toolbox Widgets]] article for a detailed explanation.<br />
Browse through the tabs and panels until you feel totally overwhelmed by all that's available.<br />
<br />
Before you start working on an image, here is some important advice – '''Don't Panic!''' You are in no danger of destroying any of your prized images if you make a mistake. RawTherapee has some features which help you protect your images:<br />
* RawTherapee does non-destructive editing of your raw files. This means that RawTherapee will never, ever change the raw file itself. All changes are stored in sidecar files. You can find out more about them in the [[Sidecar Files - Processing Profiles]] article.<br />
* When using the Editor, you'll see the [[Editor#History|History]] panel on the left. This panel shows a history stack of every change you have made to your image. To go back to any step (including when the image was first loaded), just click on the relevant line in the History panel.<br />
* Under the History panel you'll see a [[Editor#Snapshots|Snapshots]] panel. You can skip it for now, but you'll find it handy when you gain experience with RawTherapee. This panel stores the state of all the tools as a "snapshot". This allows you to easily, for example, tweak your photo to a nice and colorful look and take a snapshot, then tweak it again to a lovely black-and-white look and take a snapshot, and then compare the two just by clicking on either snapshot. (Note: RawTherapee does not save snapshots to the PP3 file yet, it will do so in the future. If you have three snapshots which you want to retain, you will need to click through them and save a PP3 file each time under a unique name).<br />
* As you might expect, Control-z will undo the previous change.<br />
<br />
=== Basics ===<br />
<br />
# Open the raw photo. RawTherapee automatically makes it look like your camera's output. If you're happy with the result, you're done. Else read on.<br />
# Click on the [[File:Color-circles.png]] Color tab and expanding the [[White Balance]] tool by right-clicking on it (or use the {{k|w}} [[Keyboard Shortcuts|keyboard shortcut]]). RawTherapee will start with the white balance used by your camera. Most white balance adjustments involve moving the Temperature and Tint sliders, or using the [[File:Color-picker.png]] Spot White-Balance Picker on a colorless (neutral gray) patch. Adjust to taste.<br />
# Next, fix the exposure by going to the [[File:Exposure.png]] Exposure tab, expanding the [[Exposure]] tool and adjusting it to taste. For now, just use the Exposure Compensation and Saturation sliders.<br />
# If your image is noisy, switch to the [[File:Detail.png]] Detail tab, zoom to 100% either using the [[File:Magnifier-1to1.png]] button or using the {{k|z}} keyboard shortcut, because the effects of the tools in this tab are only visible in the zoomed-to-100% preview (and of course in the saved image), and enable the [[Noise Reduction]] tool by clicking on the power button [[File:Power-on-small.png]] leaving the settings at their default values for now. RawTherapee has automatically removed color (chrominance) noise. Luminance noise is removed [[Noise_Reduction#Usage|manually]], though leave it for now as luminance noise generally lends a pleasing, grainy, film-like look. As a general rule, when using noise reduction don't use sharpening. Zoom back out to see the whole image either using the [[File:Magnifier-fit.png]] button or using the {{k|f}} keyboard shortcut key.<br />
# Now you decided you want to fix the [[Lens/Geometry|geometry]] and composition of your photo.<br />
#* First make the horizon level, or correct the things which should be vertical such as street lamps or building edges. To easily do this, press the "s" key on your keyboard (the same as clicking the [[File:Rotate-straighten.png]] button), and click-and-drag a line along the horizon or along the edge of a building over the preview. Your image will rotate accordingly and you will automatically be taken into the [[File:Transform.png]] Transform tab.<br />
#* To crop the photo, press the {{k|c}} shortcut key on your keyboard (or use the [[File:Crop.png]] button) and click-and-drag a crop over the preview; you will notice that the [[Crop]] tool becomes automatically enabled. There is no need to "apply" a crop - it takes effect the moment you draw it. You can zoom to fit the crop area by using the {{k|f}} keyboard shortcut, or {{k|alt}}+{{k|f}} if you want to fit the whole image. You may want to set the Crop "Guide type" to "none" if it's a problem.<br />
#* Finally, you want to downscale the photo, because who wants to upload a 10MB JPEG to your social network. Enable the [[Resize]] tool and the [[Resize#Post-Resize_Sharpening|Post-Resize Sharpening]] sub-tool, and leave them at the default settings. The resizing effect is only applied to the saved image, not to the preview, so you won't see any change in the preview as you enable these tools.<br />
# You're all set, let's [[Saving|save]] it straight away. Click the [[File:save.png]] Save Current Image button (located below the lower left corner of the preview area), or use the {{k|Ctrl}}+{{k|s}} keyboard shortcut. Save it as a JPG file using default settings (quality at "92", subsampling at "balanced"). These are good all-round settings. Choose a folder where you want it saved to, and after a few seconds your file will be ready in the folder you selected. If you close RawTherapee, the settings you used will be stored in a [[Sidecar_Files_-_Processing_Profiles|PP3 sidecar file]] next to the raw file, so that you can re-open the raw photo in the future and retain the tool settings you used.<br />
<br />
Now that you went through basic photo adjustment and are familiar with the steps, let's recap the steps but with more advanced details.<br />
<br />
=== Advanced ===<br />
<br />
Always read each tool's article here on RawPedia before using it, to get a firm understanding of what it does. The articles explain how the tools work in RawTherapee, while the general concepts unspecific to RawTherapee are left to the user to find on Wikipedia or elsewhere.<br />
<br />
Be sure to see the [[Keyboard Shortcuts]].<br />
<br />
The order of the tools inside RawTherapee's engine pipeline is hard-coded, so from that point of view it does not matter when you enable or disable a tool. However some tools can make a large impact on other tools, e.g. changing exposure may require you to re-adjust color toning, and some tools may require plenty of CPU power to calculate the preview making updates of the preview from then on slow, so it is for this reason we suggest you stick to this general order of operations:<br />
# Start off by making sure that RawTherapee's environment is set up correctly, meaning:<br />
#* Make sure that RawTherapee is using your monitor's color profile if you use a color-managed workflow. Check Preferences > Color Management. You may also need to load the appropriate calibration curves into your graphics card if you built your monitor color profile on top of them, though how you do that is outside the scope of RawTherapee.<br />
#* Make sure that the Color Management tool is configured correctly. Usually the defaults are best. Read the [[Color Management]] and [[Color Management addon]] articles. If instead of using the color matrix or DCP or ICC profiles shipped with RawTherapee you decide to use an external one, for example a self-made DCP or one from Adobe, load it as the first thing you do, otherwise you may need to re-adjust some of the color tools. Always use an output profile - in most cases the default one, RT_sRGB. If you think you're being smart by selecting "No ICM: sRGB Output", you're mistaken.<br />
# If you want to use a [[Flat Field|Flat-Field]] and/or [[Dark Frame|Dark-Frame]] image, do so now, to avoid re-adjustment.<br />
# Now set the correct [[White Balance]]. You may fix the exposure first if the image is too dark (or too bright) to see white balance changes.<br />
# Next, adjust the [[Exposure]], using the Exposure Compensation and Black sliders to get the image into the right ballpark. Once in the right ballpark, continue with using both tone curves. Be sure to read the [[Exposure#Tone_Curves|Tone Curve section]] in the Exposure article to learn why there are two of them and how best to use them - they are a very powerful tool!<br />
# In the Basics section above we suggested that you use the [[Exposure#Saturation|Saturation]] slider (in the Exposure tool). Now that you've learned the basics and are exploring more advanced techniques, we suggest you not use the Saturation slider anymore, and instead use the more powerful [[Lab_Adjustments#CC_Curve|CC curve]] in the [[Lab Adjustments]] tool, as it gives you finer control.<br />
# The order of the rest gets fuzzy. Some tools will unavoidably influence others. Carry on with the [[Lab Adjustments]] tool and then the rest of the tools in the Exposure tab. <br />
# Then use the tools in the [[File:Color-circles.png]] Color tab.<br />
# Then zoom to 100% and use the tools in the [[File:Detail.png]] Detail tab. Generally, don't sharpen if you're using noise reduction.<br />
# Finally, zoom out again and use the tools in the [[File:Transform.png]] Transform tab. The reason you left these for last is that they may make the preview image appear a bit blurry, because in order for the preview to be responsive, RawTherapee uses that very preview image you see at the very resolution you see - small - to show what the tools do, and when you rotate or otherwise change the geometry of a small image, there is a clear softening. This is not a problem when saving as by that point RawTherapee does its processing on the full-sized image, which is slow but of high quality.<br />
# You can edit metadata in the [[File:Metadata.png]] [[Metadata_Copy_Mode|Meta]] tab at any time before saving.<br />
# Save, either directly [[file:save.png]] when you want to save a single photo, or via the [[file:gears.png]] [[The_Batch_Queue|Batch Queue]] when you want to process many photos. See the [[Saving Images]] article.</div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=Download&diff=10082Download2023-03-02T18:36:16Z<p>DrSlony: Updated</p>
<hr />
<div><!-- In order to prevent the annually recurring situation of someone making a forum post with download links and explanations which end up becoming outdated and only confusing users, this page is the ONLY place which should describe the various download options available to users and testers. It should explain a concept once and only once, and the same concept should not be explained elsewhere. It must be kept current. --><br />
<br />
== Stable Releases ==<br />
<br />
{{Template:Download_stable}}<br />
<br />
== Development Builds ==<br />
<br />
Development builds can be downloaded from our [https://github.com/Beep6581/RawTherapee/releases/tag/nightly-github-actions official GitHub repository].<br />
<br />
Development build filenames follow this structure:<br />
<br />
<code>RawTherapee_<branch>_[operating-system]_<build-type>.<extension></code><br />
<br />
; Branch<br />
: Each commit happens on a branch. The main branch is called <code>dev</code>. New features are developed on their own branches, and then merged into <code>dev</code> when ready. When in doubt, get <code>dev</code>.<br />
; Operating system<br />
: A build is made for a specific operating system: <code>win64</code> builds run on any modern 64-bit version of Windows, <code>macOS_10.15</code> builds run on the specified version of macOS or newer, and Linux builds omit the OS segment and instead use <code>AppImage</code> as the extension.<br />
; Build type<br />
: The build type is either <code>release</code> or <code>debug</code>. Release-type builds are optimize to run fast, but do not provide any useful information in case of a crash. Conversely, debug-type builds are capable of producing useful information during a crash [https://rawpedia.rawtherapee.com/How_to_write_useful_bug_reports for a bug report], but will run significantly slower. When in doubt, get <code>release</code>.<br />
<br />
Every time the source code is changed, a development build is automatically created. These builds are provided for the sole purpose of allowing you to try out the newest features and the latest fixes, and to report your findings back to us via [https://github.com/Beep6581/RawTherapee/ GitHub] or [https://discuss.pixls.us/c/software/rawtherapee/ the forum].<br />
<br />
Development builds are '''not intended for production use''' and we provide '''no backward or forward compatibility for [[Sidecar_Files_-_Processing_Profiles|sidecar files (pp3)]]''' created using a development build! That means that a sidecar file created using a dev build will very likely lead to different results when used in a stable release or in another dev build. If stability and compatibility are key for you, we always recommend that you use the latest stable release. If you want to use a feature or fix present in the latest dev build in production, you have to wait until we release the next stable version.</div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=File_Paths&diff=9937File Paths2023-01-04T18:57:57Z<p>DrSlony: /* Temporary Folder */</p>
<hr />
<div><div class="pagetitle">File Paths</div><br />
<br />
RawTherapee makes use of a "cache" folder to store temporary files which are safe to delete, and a "config" folder which stores your RawTherapee settings, custom processing profiles and other user-editable files. These folders reside in a special place, described below, and have a name that begins with the word "RawTherapee" optionally followed by a suffix. This suffix is set by the person who made the build of RawTherapee you're using. Some examples of what it can look like:<br />
* RawTherapee<br />
* RawTherapee'''4.2'''<br />
* RawTherapee'''5'''<br />
* RawTherapee'''5-dev'''<br />
* RawTherapee'''_test'''<br />
* And other possibilities always beginning with "RawTherapee"<br />
<br />
The first part, "RawTherapee", is hard-coded. The second part, the suffix, is up to the person who made the build. It might be specific, like "5.0-gtk2-123-g87654321", it could be general, like "5", it could be anything else, like "_test", or it could be not set. We recommend that RawTherapee stable releases not use a suffix at all, while all development versions use "5-dev" - hopefully the person who made the build you're using took this into account.<br />
<br />
== Config ==<br />
<br />
The RawTherapee config folder contains:<br />
* the "options" file, which contains all of your settings from [[Preferences]],<br />
* the "batch" folder, which stores temporary [[Sidecar Files - Processing Profiles|processing profiles]] of the photos you sent to the [[The Batch Queue|Queue]],<br />
* the user-editable [[Adding Support for New Raw Formats|camconst.json]] file, where you can define details of how a specific raw format is to be treated (this overrides the values from the system camconst.json file),<br />
* the [[Dynamic processing profiles|dynamic profile]] rules,<br />
* and the "profiles" folder where you can save your custom [[Sidecar Files - Processing Profiles|processing profiles]] to if you want them to appear in RawTherapee's drop-down list.<br />
<br />
You could include this folder in your backups so that you can regain all of your settings and custom processing profiles if you install RawTherapee on a new system.<br />
<br />
Default locations for the RawTherapee config folder (look for the "RawTherapee*" prefix as described above):<br />
; Windows XP<br />
: <code>%USERPROFILE%\Local Settings\Application Data\</code><br />
; Windows 7, 8 and 10<br />
: <code>%LOCALAPPDATA%</code><br />
; Linux<br />
: <code>~/.config/</code><br />
; macOS<br />
: <code>~/Library/Application Support/RawTherapee/config/</code><br />
: Under the Finder's 'Go' menu click 'Go to Folder' (shortcut Command+Shift+g), you can then type/paste any path you want to navigate to, even if it's hidden.<br />
<br />
== Cache ==<br />
<br />
The RawTherapee cache folder contains sets of cached items, where each set consists of:<br />
* a thumbnail,<br />
* metadata,<br />
* a sidecar file,<br />
* and optionally an embedded profile.<br />
<br />
By default, RawTherapee keeps up to 20 000 cached sets. Keep an eye on the "cache" folder as over time it may grow considerably in size! This is mostly due to the cached thumbnails which are stored in the "images" sub-folder. Deleting the "images" sub-folder is safe, you will not lose any image settings, RawTherapee will just have to regenerate the thumbnails.<br />
<br />
Default locations for the RawTherapee cache folder (look for the "RawTherapee*" prefix as described above):<br />
; Windows XP<br />
: <code>%USERPROFILE%\Local Settings\Application Data\</code><br />
; Windows 7, 8 and 10<br />
: <code>%LOCALAPPDATA%</code><br />
; Linux<br />
: <code>~/.cache/</code><br />
; macOS<br />
: <code>~/Library/Application Support/RawTherapee/cache/</code><br />
: Under the Finder's 'Go' menu click 'Go to Folder' (shortcut Command+Shift+g), you can then type/paste any path you want to navigate to, even if it's hidden.<br />
<br />
A cached set used to include a 32kB histogram file, but as of RawTherapee 5.5 the need for storing the histogram was eliminated.<br />
<br />
== Custom config and cache folders ==<br />
<br />
You can have RawTherapee use a custom config folder by setting the <code>RT_SETTINGS</code> environment variable to an '''absolute''' path which you have read and write access to, and likewise you can use a custom cache folder by setting the <code>RT_CACHE</code> environment variable. How you do that depends on your operating system, so just search on the internet for "how to set environment variables in ''<your operating system>''".<br />
<br />
Some examples:<br />
; Windows<br />
: Variable name: <code>RT_SETTINGS</code>, value: <code>%LOCALAPPDATA%\rawtherapee\5.7</code><br />
: Variable name: <code>RT_CACHE</code>, value: <code>Z:\rawtherapee\cache</code><br />
; Linux and macOS<br />
: <code>RT_SETTINGS=/home/bob/.config/rawtherapee/5.7</code><br />
: <code>RT_CACHE=/home/bob/junk/rtcache</code><br />
<br />
== Processing Profiles ==<br />
<br />
If you create your own [[Sidecar Files - Processing Profiles | processing profiles]], to have them appear in RawTherapee's "Processing Profiles" list you should save them to the "profiles" folder which you will find inside the "config" folder as described above.<br />
<br />
== Temporary Folder ==<br />
<br />
The "[[Edit Current Image in External Editor]]" tool stores intermediate image files in the folder specified in [[Preferences#External_Editor|Preferences > External Editor > Output Directory]]. By default this is the operating system's default temp folder. RawTherapee will use a subdirectory with the name format <code>rawtherapee-<username></code>, e.g. <code>rawtherapee-Lawrence37</code>, and permissions are set to user-only read/write access. If this subdirectory already exists but has the wrong permissions, a new directory will be created with the correct permissions and with the name format <code>rawtherapee-<username>-xxxxxx</code> where <code>xxxxxx</code> is a random sequence of 6 characters, e.g. <code>rawtherapee-Lawrence37-abc123</code>.<br />
<br />
; Windows<br />
: The operating system's default temp folder is the one stored in the <code>$TEMP</code> environment variable, which is usually <code>%LOCALAPPDATA%/Temp</code><br />
: If you do not have the <code>$TEMP</code> environment variable set, <code>C:\</code> is used.<br />
; Linux and macOS<br />
: The operating system's default temp folder is the one stored in the <code>$TMPDIR</code> environment variable, which is usually <code>/tmp</code><br />
: If you do not have the <code>$TMPDIR</code> environment variable set, <code>/tmp</code> is used.</div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=Edit_Current_Image_in_External_Editor&diff=9936Edit Current Image in External Editor2023-01-04T18:48:11Z<p>DrSlony: </p>
<hr />
<div>The "''Edit current image in external editor''" feature allows you to have RawTherapee fully process the current image and immediately open it in any external application. You can use this feature to easily send the image to an image editor such as GIMP or Photoshop for further processing, or to preview the processed image in an image viewer.<br />
<br />
The button to send the image to an external application [[File:Rt510 edit in external editor gimp.png]] is located at the bottom-left of the preview panel. When the button is clicked, the image will be processed and sent to the currently selected external application. The button's icon and tooltip reflect the current external application. To select a different application, click on the drop-down arrow and select an item from the list (this list can be configured via [[Preferences#External_Editor|Preferences > External Editor]]). Note that the last entry in the list is "Other". If this option is selected, clicking the button will open a list of installed applications. RawTherapee will then send the processed image to the chosen application.<br />
<br />
When using this feature, RawTherapee processes your image and saves it as a gamma-encoded 16-bit integer TIFF to the temporary folder as specified in [[Preferences#External_Editor|Preferences > External Editor > Output Directory]].</div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=File:Rt510_edit_in_external_editor_gimp.png&diff=9935File:Rt510 edit in external editor gimp.png2023-01-04T18:46:53Z<p>DrSlony: </p>
<hr />
<div></div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=Preferences&diff=9934Preferences2023-01-04T18:26:50Z<p>DrSlony: External Editors</p>
<hr />
<div><div class="pagetitle">Preferences</div><br />
<br />
You can access the Preferences window by clicking on the Preferences button [[image: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]].<br />
<br />
== About ==<br />
<br />
The About button opens a window which contains a splash screen, technical details of the specific RawTherapee build you're running, credits, licence and release notes.<br />
<br />
Please include these technical details when filing a [[How to write useful bug reports|bug report]].<br />
<br />
== General Tab ==<br />
<br />
=== Layout ===<br />
<br />
* Editor Layout<br />
<br />
: The layout of RawTherapee's user interface can be adapted to suite your taste and needs, specifically pertaining to whether you would like to have more than one raw file open simultaneously, and whether you use one monitor or more. The following modes are available:<br />
:* Single Editor Tab Mode<br />
:* Single Editor Tab Mode, Vertical Tabs<br />
:* Multiple Editor Tabs Mode<br />
:* Multiple Editor Tabs Mode (if available on second monitor)<br />
<br />
: Remember that if you simultaneously open several images each in its own [[The Image Editor Tab|Editor]] tab, each tab and instance will require a significant 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, and so forth, however a rule of thumb could be to not use multiple Editor tabs unless you have more than 8GB of RAM.<br />
<br />
: A restart is required for these changes to take effect.<br />
<br />
* Position of Curve Copy & Paste Buttons<br />
<br />
: Curves include adjacent buttons for copying, pasting, opening and saving the curve, and some include buttons for placing a node on the curve by picking a sample from the preview and for setting numeric in/out values. This option lets you decide where these buttons will be positioned relative to the curve widget.<br />
<br />
: A restart is required for these changes to take effect.<br />
<br />
* Histogram in Left Panel<br />
<br />
: Position the main histogram in the left panel above "History", or in the right tool panel above the tools.<br />
<br />
* Show Filmstrip Toolbar<br />
<br />
[[File:Rt_setm_fb.png|thumb|The filter and ratings toolbar (4) can be shown in the Filmstrip.]]<br />
<br />
: The Filmstrip is a narrow panel which you can toggle to appear within the Editor tab. It contains thumbnails of the images in the currently opened folder, along with the filter and ratings toolbar. It can be useful to see the Filmstrip while working in the Editor tab, but you can hide it if you need the extra vertical screen space. Use this option to show or hide it. Note that you can also toggle its visibility from the Editor tab by using the "Toggle the visiblity of the Filmstrip's toolbar" [[Keyboard_Shortcuts|keyboard shortcut]].<br />
<br />
* Compact Toolbars in File Browser<br />
<br />
[[File:Single-row-file-browser-toolbar-off.png|thumb|Disabled, great for low-resolution screens.]]<br />
[[File:Single-row-file-browser-toolbar-on.png|thumb|Enabled, requires that the screen has a high enough resolution to fit all the elements horizontally.]]<br />
<br />
: Enable this option if you have a high resolution screen to merge all the toolbars at the top of the File Browser tab into one.<br />
<br />
: {{:Scrollable Toolbar}}<br />
<br />
* Hide Vertical Scrollbar<br />
<br />
: You can hide the vertical scrollbar from the toolbox to save a little horizontal screen space. Use the mouse scroll-wheel to scroll when the scrollbar is hidden.<br />
<br />
* Tool Collapsed/Expanded State<br />
<br />
: If you have a few favorite tools which you would like to always see expanded, you can expand them now, hide the others, then return here to Preferences, disable "Automatically save tools' collapsed/expanded state before exiting", click "Save tools' collapsed/expanded state now", and click "OK" to close the Preferences window and commit your changes.<br />
<br />
: Alternatively, if you would instead like RawTherapee to remember which tools are collapsed and which are expanded at the end of every editing session, then enable "Automatically save tools' collapsed/expanded state before exiting".<br />
<br />
=== Language ===<br />
<br />
Select a language for the user interface. "Use system language" will try to auto-detect your language based on environment variables. You can override the auto-detected language by selecting one manually.<br />
<br />
If you would like to help by updating one of the translations or creating a new one, see this post:<br />
: https://discuss.pixls.us/t/localization-how-to-translate-rawtherapee-and-rawpedia/2594<br />
<br />
A restart is required for these changes to take effect.<br />
<br />
=== Appearance ===<br />
<br />
[[File:Image editor.png|thumb|The Image Editor tab showing:<br />
(1) the preview background,<br />
(2) the crop mask,<br />
(3) lockable color pickers and<br />
(4) buttons which toggle the color of the preview background between black, white and theme-based.]]<br />
<br />
* Theme<br />
: Choose a theme for the user interface. Although you will see theme-related changes as soon as you hit the "OK" button, you need to restart for the changes to take affect correctly.<br />
: The way human vision perceives colors depends on various factors, of particular importance to this paragraph are the properties of the area which surround the observed region. The way you perceive the colors of a photograph viewed on a screen depends in part on the colors of the area surrounding the photograph. You can read more about this in the [[CIECAM02]] article. In order to mitigate the errors the user makes while adjusting a photo, RawTherapee ships themes which use neutral background colors. While all of the themes are based on shades of grey, the theme which is most suited to avoid affecting human perception is "TooWaGrey - Average Surround", available from version 5.2 onward.<br />
<br />
* Main font, and color picker font<br />
: Choose a custom main font, and a font for the Lockable Color Picker in the [[The_Image_Editor_Tab|Image Editor]] tab, marked "3" in the screenshot.<br />
: Some users will find the default font size too small or too large due to their screen resolution and DPI setting. You can fix that by changing the font size.<br />
<br />
* Crop mask color<br />
: Adjust the color and transparency of the area outside of a cropped region, marked "2" in the screenshot. By clicking on the colored button, a new window appears where you can select a standard color or click on "Custom" to specify a new color. The vertical axis adjusts hue, while the horizontal axis adjusts transparency. Partial transparency is useful as it allows the cropped-off part of the photo to remain somewhat visible (2), so that you can move the crop around to find the best composition (hold the '''Shift''' key and move the crop with the mouse).<br />
<br />
[[File:Image editor navigator.png|thumb|The Image Editor tab showing:<br />
(1) the Navigator panel,<br />
(2) the Navigator guide which marks the area currently visible in the main preview when zoomed-in.]]<br />
<br />
* Navigator guide color<br />
: Adjust the color and transparency of the frame (marked "2" in the second screenshot) visible in the [[The_Image_Editor_Tab#Navigator|Navigator]] panel (marked "1") when the main preview is zoomed-in.<br />
<br />
[[File:Rt56 hidpi.png|thumb|Normal interface and HiDPI scaled interface.]]<br />
<br />
* Pseudo-HiDPI mode<br />
: Scales the user interface so that text and images remain sharp even on a HiDPI screen. Introduced in RawTherapee 5.6. Scaling in RawTherapee depends on font size, DPI and display scaling. While scaling has been tested to work well in Windows, Linux and macOS, there are some macOS display modes which are incompatible with it, specifically those modes suffixed by "(HiDPI)" in macOS Display settings. Some versions of macOS (10.14.*) seem to not list any modes, in which case the user must just give it a try.<br />
<br />
=== Clipping Indication ===<br />
<br />
{{:Clipping_Indication}}<br />
<br />
=== Pan Rate Amplification ===<br />
<br />
Imagine you are viewing a high resolution images while zoomed-in to 100%. In order to pan the image around the screen you would have to make multiple mouse movements (or have a very large mouse pad). RawTherapee saves you from this by using "pan rate amplification" - when set to 5, RawTherapee multiplies every pixel you pan by 5. If you'd normally move the cursor 500 pixels in one comfortable mouse movement, you will have panned 2500 pixels with this option set to 5.<br />
<br />
The effect is most visible when you are zoomed in, and least visible when zoomed out.<br />
<br />
When "Remember zoom % and pan offset" is enabled, when you open the next image RawTherapee will try to show the same area at the same zoom level as the current image. This only works in "Single Editor Tab Mode" and when "[[Preferences#Preview_Demosaicing_Method|Demosaicing method used for the preview at <100% zoom]]" is set to "As in PP3".<br />
<br />
=== External Editor ===<br />
<br />
[[File:Rt510 preferences external editor.png|thumb|Ability to specify multiple external editors was added in RawTherapee 5.10.]]<br />
<br />
RawTherapee can send the processed image directly to an external program, e.g. an image editor, an image viewer or a script. This is done 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 the processed image is to be sent to when you click the button.<br />
<br />
To get started, click the [[File:Add-small.png]] plus button. This will add a new entry to the list. Then, click Change Application or Change Executable to select the external editor. The Change Application button opens a list of installed applications to choose from, while the Change Executable button opens an executable file selector. Multiple external editors can be added this way. To remove an editor, select the entry in the list and click the [[File:Remove-small.png]] minus button.<br />
<br />
The external editor names and commands can be edited directly by double clicking the text. You must confirm the edit by hitting enter, else your edit will be discarded.<br />
<br />
Processed images are stored in the location specified by "Output directory", and are not deleted when RawTherapee is closed. However, the default location is the operating system's temp directory which is typically lost when the operating system shuts down.<br />
<br />
Suggestions for external editor commands:<br />
* <code>geeqie --remote</code> will open images in a single Geeqie window, preventing clutter caused by multiple Geeqie windows.<br />
* macOS users may use the "open" command, <code>open -a "External Program"</code>, for example <code>open -a "/My stuff/Programs/Turbo Pixels"</code>. 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.<br />
<br />
== Image Processing Tab ==<br />
<br />
=== Default Processing Profile ===<br />
<br />
Specify which profile RawTherapee is to use when opening a raw or non-raw photo.<br />
<br />
* The default processing profile '''for raw photos''' as of RawTherapee 5.4 is "[[Auto-Matched Curve]] - ISO Low".<br />
* The default processing profile '''for non-raw photos''' (such as JPEG, TIFF or PNG) is "[[Neutral]]". The "Neutral" profile just loads the photo as it is, without applying any changes.<br />
<br />
To have processing profiles you have made yourself appear in the list, save them to the "''profiles''" sub-folder within the "''config''" folder. You can find out where it is on the [[File_paths#Processing_Profiles | file paths]] page.<br />
<br />
The special entry "Dynamic" activates the support for [[Dynamic_processing_profiles | Dynamic Processing Profiles]].<br />
<br />
When you right-click on a thumbnail and select "Processing profile operations > Reset to default" RawTherapee will apply whichever processing profile is selected as default for that image type. If the default is set to "Dynamic", then RawTherapee will run through the dynamic profile rules to generate a profile dynamically.<br />
<br />
=== Custom Processing Profile Builder ===<br />
<br />
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.<br />
<br />
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]]<br />
<br />
<b>Note:</b> You are responsible for using double quotes where necessary if you're using paths containing spaces.<br />
<br />
=== Processing Profile Handling ===<br />
<br />
* Processing profile saving location<br />
*: Choose whether you want RawTherapee to store the processing profiles next to the input file (the default behavior), to a [[File_Paths#Cache|central cache]], or both.<br />
*: It is a good idea to save the processing profiles next to the input files, as that lets you easily backup and handle your photos and their associated processing profiles.<br />
* Processing profile loading location<br />
*: RawTherapee will look for processing profiles alongside the images, and in the central cache. If a profile exists in both places and they are not identical, this setting allows you to choose which one should have the deciding say.<br />
<br />
=== Directories ===<br />
<br />
Specify the location of your [[Dark-Frame]], [[Flat-Field]] and [[Film Simulation|HaldCLUT Film Simulation]] folders.<br />
<br />
=== Crop Editing ===<br />
<br />
This section lets you decide which guides are shown when the crop is _not_ being manipulated. "Original" means the guide type currently selected, so for example if you would like to see the "Rule of Thirds" guide while dragging a crop, and to have the guide automatically disappear once you are done dragging the crop, then set this option to "Frame" or "None".<br />
<br />
Once a crop is in place, RawTherapee can automatically zoom the cropped area to fit the screen if you enable this option.<br />
<br />
== Dynamic Profile Rules Tab ==<br />
<br />
Here you can define your custom rules for creating [[Dynamic_processing_profiles | Dynamic Processing Profiles]].<br />
<br />
== File Browser Tab ==<br />
<br />
=== Image Directory at Startup ===<br />
<br />
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.<br />
<br />
=== File Browser / Thumbnail Options ===<br />
<br />
These options determine which information is visible in the thumbnails and how it should be displayed.<br />
<br />
=== Context Menu Options ===<br />
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]]).<br />
<br />
=== Parsed Extensions ===<br />
<br />
Choose which files are recognized as images and displayed in the [[The File Browser Tab|File Browser]]. All supported extensions are set by default, except for PNG which is disabled by default.<br />
<br />
If a desired extension is missing you can easily add it by clicking the "Add" [[File:Add-small.png]] button.<br />
<br />
Some users reported that their Parsed Extensions panel is empty. This could happen after updating from an unspecified older version of RawTherapee. If your parsed extensions panel is empty, we recommend you close RawTherapee, then find and delete the "[[File_Paths#Config|options]]" file. The next time you run RawTherapee you will be using the latest defaults, and your list of parsed extensions will contain all supported formats.<br />
<br />
=== Cache Options ===<br />
<br />
To understand this section, first read the [[File_Paths#Cache|Cache]] article. The typical user should not need to change these defaults.<br />
<br />
The maximum thumbnail height decides how large you can make the thumbnails. Each thumbnail is stored in RawTherapee's [[File_Paths#Cache|cache]] folder and requires disk space, so keep this in mind if you increase the default size.<br />
<br />
The maximum number of cache entries decides how many of these cached files are kept before the oldest ones are deleted once the limit is reached.<br />
<br />
You can manually clear elements of the cache using the "Clear" buttons.<br />
<br />
You could "clear all cached files except for cached processing profiles" when updating RawTherapee to keep your disk clean and benefit from new cache-related improvements.<br />
<br />
== Color Management Tab ==<br />
<br />
Use the "Directory containing color profiles" button to point RawTherapee to the folder which contains color profiles.<br />
<br />
Standard locations where color profiles are stored:<br />
:; Windows<br />
:: <code>C:\Windows\system32\spool\drivers\color</code><br />
:; Linux<br />
:: <code>/usr/share/color/icc/</code><br />
:; macOS<br />
:: <code>/library/ColorSync/Profiles/Displays/</code><br />
<br />
=== Monitor ===<br />
<br />
Set the "Default color profile" to the ICC file you generated when calibrating and profiling your monitor. You can have RawTherapee try to auto-detect the profile by using the "Use operating system's main monitor color profile" option.<br />
<ul><br />
<li>In Linux, the <code>[http://www.burtonini.com/computing/x-icc-profiles-spec-latest.html _ICC_PROFILE]</code> X11 atom is used to automatically find the monitor's ICC profile. Since there is only one such atom, and it is used by the "main" monitor, automatic detection is also limited to the main monitor, though you can copy multiple ICC profiles into the standard location and then you will be able to manually select them under the preview in the Editor.<br><br />
One very simple way of "installing" a monitor profile in Linux so that the atom gets set correctly is using [https://displaycal.net/ DisplayCAL], via the menu "File &gt; Install profile".<br><br />
To see if the X11 atom is set, run this in a console:<br />
<pre>xprop -len 8 -root _ICC_PROFILE</pre><br />
If the result is "_ICC_PROFILE: no such atom on any window", then the atom is not set. If the result is a bunch of numbers, then it is set.</li><br />
<li>In Windows, right-click an ICC (or ICM, they're identical) file and select "Install profile" in the context menu, or search for "colour management" in the Start menu.</li><br />
<li>In macOS, monitor profiles on an application level are not supported. All displayed colors will be in the [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 in macOS. 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. For more information, see: https://discuss.pixls.us/t/wide-gamut-preview-in-macos/2481<br />
</li><br />
</ul><br />
<br />
Rendering intents and black point compensation are explained below.<br />
<br />
The monitor profile must be of the "device" class in the RGB colorspace.<br />
<br />
=== Printer (Soft-Proofing)===<br />
<br />
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.<br />
<br />
The printer profile must be of the "output" class in either the RGB or CMYK colorspaces.<br />
<br />
See below for Black Point Compensation.<br />
<br />
=== Rendering Intents ===<br />
<br />
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. When in the "Monitor" section, the "source" is the color space within which lies the image data at the end of the pipeline before being put into the monitor profile's color space, and the "destination" is the selected monitor profile's color space. When in the "Printer (Soft-Proofing)" section, the "source" is the image data at the end of the pipeline, and the "destination" is the selected printer profile's color space.<br />
<br />
:; Relative Colorimetric<br />
:: Colors from the source which lie outside the gamut of the destination color space will be shown using the nearest in-gamut color without affecting other in-gamut colors. The white point will be corrected. This is the default option and works with all profiles.<br />
<br />
:; Perceptual<br />
:: Colors from the source which lies outside the gamut of the destination color space will be compressed into the destination's gamut at the expense of also affecting in-gamut colors. How the compression is performed is up to the gamut mapping contained within the color profile - it usually involves desaturation, and sometimes even hue shifts. The perceptual intent only works with LUT profiles which contain the required gamut mapping tables - most ICC profiles do not, and in those cases "relative colorimetric" will be silently used instead (this is standard behavior across most software).<br />
<br />
:; Absolute Colorimetric<br />
:: Similar to relative colorimetric, but the white point will not be corrected. For this reason, it is used when you want to match paper whiteness to screen. You might want to use it when proofing, but not otherwise.<br />
<br />
=== Black Point Compensation ===<br />
<br />
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.<br />
<br />
== Batch Edit Tab ==<br />
<br />
Batch editing is making adjustments to more than one image at the same time. This is done through the [[The_File_Browser_Tab#Batch_Adjustments_-_Sync|Batch Edit]] tab in the File Browser.<br />
<br />
The tool panel in the Batch Edit tab looks similar to the tool panel from the [[The_Image_Editor_Tab|Image Editor]] tab, but it uses checkboxes to communicate which tool settings are consistent across the selected images and which are not. These checkboxes have three states:<br><br />
<code>[ ]</code> Disabled<br><br />
<code>[✓]</code> Enabled<br><br />
<code>[-]</code> Values differ across selected images.<br><br />
<br />
Batch editing is done by selecting multiple images in the [[The_File_Browser_Tab|File Browser]] (hold the {{k|Shift}} or {{k|Ctrl}} key, then click the images you want to select), then you can edit those images using the tools in the Batch Edit panel on the right.<br />
<br />
The controls (sliders, spinboxes, etc.) in the Batch Edit panel show the values of the processing parameters for the selected images. These can be the values of the default processing profile or the values from your last edit session of those photos.<br />
<br />
If an image is currently being edited in the [[The_Image_Editor_Tab|Editor]], the editor's values will be reflected in real time in the Batch Edit panel, and vice versa, so take care what you're doing.<br />
<br />
What happens to the tool values as you manipulate them depends on the "Behavior" setting in this Batch Edit tab.<br />
<br />
; The "Add" Mode<br />
: 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.<br />
<br />
: 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.<br />
<br />
; The "Set" Mode<br />
: 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).<br />
<br />
: 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.<br />
<br />
== Performance Tab ==<br />
<br />
The "Performance" tab is only for people who know what they're doing. It lets you poke under the hood and tweak some parameters depend on available RAM and CPU speed.<br />
<br />
=== Preview Demosaicing Method ===<br />
<br />
The "Demosaicing method used for the preview at <100% zoom" option sets which [[demosaicing]] method is used for the main preview in the Editor. By default, the same demosaicing method is used as specified in the Demosaicing section of the Raw tab, but if you are on a a very slow computer you can save a few hundred milliseconds by using the "Fast" demosaicing method. The trade-off is that the "Fast" method has the worst quality, though in most cases the difference is slight.<br />
<br />
=== TIFF Read Settings ===<br />
<br />
"Serialize read of TIFF files", enabled by default, can speed up thumbnail generation when opening for the first time a folder full of uncompressed TIFF files.<br />
<br />
=== HaldCLUT Cache ===<br />
<br />
The "Maximum number of cached CLUTs" setting lets you specify how many last-used HaldCLUT ([[Film Simulation]]) images are stored in RAM for faster access when switching back and forth between them in the Editor.<br />
<br />
=== Inspect ===<br />
<br />
Most raw files contain an embedded JPEG preview image. To show that image in the [[File_Browser#Inspect|Inspect]] tab it needs to be extracted, which takes a fraction of a second. The "Maximum number of cached images" setting lets you specify how many of the last-viewed embedded images are kept in RAM, so that if you view the previous image in the Inspect tab, RawTherapee will not need to re-extract it, but just access it from RAM.<br />
<br />
The "Image to show" option lets you decide whether to use the embedded JPEG image or to render one based on the real raw data using the "[[Neutral]]" processing profile. Using the embedded image is faster than rendering from the real raw data.<br />
<br />
=== Threads ===<br />
<br />
Splitting calculations and running them as concurrent [https://en.wikipedia.org/wiki/Thread_(computing) threads] allows them to complete faster, however doing so requires more RAM. By default, RawTherapee decides automatically how many threads to use. You can override this value here.<br />
<br />
Most modern CPUs run two threads per physical core. Find out what CPU you have and how many cores it has, multiply that number 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.<br />
<br />
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.<br />
<br />
== Sounds Tab ==<br />
<br />
The "Sounds" tab lets you set an audible notification when a lengthy operation ends. It is currently only supported on Windows and Linux.<br />
<br />
The "Queue processing done" sound is played after the last [[The_Batch_Queue|Queue]] image finishes processing.<br />
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.<br />
<br />
Sounds can be muted either by disabling the "Enabled" checkbox or by setting fields with sound file references to blank values.<br />
<br />
The "Queue" and "Editor processing done" text boxes can either point to wave (.wav) files, or can specify one of the following values:<br />
; Windows:<br />
* SystemAsterisk<br />
* SystemDefault<br />
* SystemExclamation<br />
* SystemExit<br />
* SystemHand<br />
* SystemQuestion<br />
* SystemStart<br />
* SystemWelcome<br />
<br />
; Linux<br />
* bell<br />
* camera-shutter<br />
* complete<br />
* dialog-warning<br />
* dialog-information<br />
* message<br />
* service-login<br />
* service-logout<br />
* suspend-error<br />
* trash-empty<br />
* possibly the name of any file in <code>/usr/share/sounds/freedesktop/stereo/</code> without the path or extension.<br />
<br />
RawTherapee relies on libcanberra to produce sounds. In case of issues in Linux, you can trigger a sound to play from a terminal by invoking the following command (replace "bell" with any of the above):<br />
<pre>canberra-gtk-play -i bell</pre></div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=File:Rt510_preferences_external_editor.png&diff=9933File:Rt510 preferences external editor.png2023-01-04T18:08:20Z<p>DrSlony: </p>
<hr />
<div></div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=Template:AdobeDngConverterLinux&diff=9852Template:AdobeDngConverterLinux2022-11-30T14:49:35Z<p>DrSlony: </p>
<hr />
<div># Install [http://www.winehq.org/ Wine], preferably using your package manager. At the time of writing, wine-7.20 is confirmed to work well with Adobe DNG Converter 15.0.<br />
# Download Adobe DNG Converter for Windows. Try the newest version first. If that doesn't work, try an older version. You can download the newest version from [https://helpx.adobe.com/camera-raw/using/adobe-dng-converter.html Adobe], or you can download older versions from [https://www.filehorse.com/download-adobe-dng-converter/old-versions/ FileHorse].<br />
# Set Wine to Windows 10 mode:<br />
#: <pre style="white-space:pre-wrap;">WINEPREFIX="$HOME/wine-dng" winecfg</pre><br />
#: Wine might ask you to install Mono. At the time of writing, it was not needed to run Adobe DNG Converter, so installing it is not required but not needed either.<br />
#: In the "Applications" tab set "Windows Version" to "Windows 10". Hit "Ok" to close Wine configuration.<br />
# Install Adobe DNG Converter:<br />
#: <pre style="white-space:pre-wrap;">WINEPREFIX="$HOME/wine-dng" wine ~/Downloads/AdobeDNGConverter_x64_15_0.exe</pre><br />
#: It will install to <code>$HOME/wine-dng/drive_c/Program Files/Adobe/Adobe DNG Converter/Adobe DNG Converter.exe</code><br />
# This step is optional. There is an issue affecting all versions of Wine older than 5.0-rc5 when using Adobe DNG Converter version 11.2 or newer. The issue results in Wine crashing on startup. The issue was fixed in Wine 5.0-rc5, see Wine bug [https://bugs.winehq.org/show_bug.cgi?id=46972 #46972]. If you use any version of Wine lower than 5.0-rc5, you can easily circumvent the issue.<br />
#: Run Wine configuration:<br />
#: <pre style="white-space:pre-wrap;">WINEPREFIX="$HOME/wine-dng" winecfg</pre><br />
#: Go to the "Libraries" tab, add a new override for <code>api-ms-win-core-winrt-error-l1-1-0</code>, then edit it and select "Disable". Done.<br />
# Run Adobe DNG Converter:<br />
#: <pre style="white-space:pre-wrap;">WINEPREFIX="$HOME/wine-dng" wine "$HOME/wine-dng/drive_c/Program Files/Adobe/Adobe DNG Converter/Adobe DNG Converter.exe"</pre><br />
# Add an alias so that you can run Adobe DNG Converter from a console with ease:<br />
#: <pre style="white-space:pre-wrap;">echo "alias dng='WINEPREFIX=\"\$HOME/wine-dng\" wine \"\$HOME/wine-dng/drive_c/Program Files/Adobe/Adobe DNG Converter/Adobe DNG Converter.exe\"'" >> ~/.bashrc && exec bash</pre><br />
# To run Adobe DNG Converter, just type <code>dng</code> in a console.</div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=Template:AdobeDngConverterLinux&diff=9851Template:AdobeDngConverterLinux2022-11-30T14:41:18Z<p>DrSlony: Updated for Adobe DNG Converter 15.0</p>
<hr />
<div># Install [http://www.winehq.org/ Wine], preferably using your package manager. <br />
# Download Adobe DNG Converter for Windows. Try the newest version first. If that doesn't work, try an older version. You can download the newest version from [https://helpx.adobe.com/camera-raw/using/adobe-dng-converter.html Adobe], or you can download older versions from [https://www.filehorse.com/download-adobe-dng-converter/old-versions/ FileHorse].<br />
# Set Wine to Windows 10 mode:<br />
#: <pre style="white-space:pre-wrap;">WINEPREFIX="$HOME/wine-dng" winecfg</pre><br />
#: Wine might ask you to install Mono. At the time of writing, it was not needed to run Adobe DNG Converter, so installing it is not required but not needed either.<br />
#: In the "Applications" tab set "Windows Version" to "Windows 10". Hit "Ok" to close Wine configuration.<br />
# Install Adobe DNG Converter:<br />
#: <pre style="white-space:pre-wrap;">WINEPREFIX="$HOME/wine-dng" wine ~/Downloads/AdobeDNGConverter_x64_15_0.exe</pre><br />
#: It will install to <code>$HOME/wine-dng/drive_c/Program Files/Adobe/Adobe DNG Converter/Adobe DNG Converter.exe</code><br />
# This step is optional. There is an issue affecting all versions of Wine older than 5.0-rc5 when using Adobe DNG Converter version 11.2 or newer. The issue results in Wine crashing on startup. The issue was fixed in Wine 5.0-rc5, see Wine bug [https://bugs.winehq.org/show_bug.cgi?id=46972 #46972]. If you use any version of Wine lower than 5.0-rc5, you can easily circumvent the issue.<br />
#: Run Wine configuration:<br />
#: <pre style="white-space:pre-wrap;">WINEPREFIX="$HOME/wine-dng" winecfg</pre><br />
#: Go to the "Libraries" tab, add a new override for <code>api-ms-win-core-winrt-error-l1-1-0</code>, then edit it and select "Disable". Done.<br />
# Run Adobe DNG Converter:<br />
#: <pre style="white-space:pre-wrap;">WINEPREFIX="$HOME/wine-dng" wine "$HOME/wine-dng/drive_c/Program Files/Adobe/Adobe DNG Converter/Adobe DNG Converter.exe"</pre><br />
# Add an alias so that you can run Adobe DNG Converter from a console with ease:<br />
#: <pre style="white-space:pre-wrap;">echo "alias dng='WINEPREFIX=\"\$HOME/wine-dng\" wine \"\$HOME/wine-dng/drive_c/Program Files/Adobe/Adobe DNG Converter/Adobe DNG Converter.exe\"'" >> ~/.bashrc && exec bash</pre><br />
# To run Adobe DNG Converter, just type <code>dng</code> in a console.</div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=Template:WinePrefix&diff=9850Template:WinePrefix2022-11-30T14:35:35Z<p>DrSlony: </p>
<hr />
<div>When you run Wine it will create a basic Windows system by default in <code>$HOME/.wine</code>. That is called a "Wine prefix". While it's fine to leave it like that, you can run each Windows program in its own Wine prefix, so that you can easily and cleanly remove all traces of one program without affecting the others. For example you might keep Adobe DNG Converter in its own Wine prefix in <code>$HOME/wine-dng</code> and decide to try out some proprietary Windows HDR program. You might find out that you don't like this program, or that the trial period has expired, or that it simply doesn't work. Uninstalling it, if the uninstaller even works, is known to leave things behind. If, on the other hand, you installed this program to its own Wine prefix, say <code>$HOME/wine-hdr</code>, you could simply delete that folder and that program would be gone without a trace, without affecting Adobe DNG Converter.<br />
<br />
Creating a new Wine prefix is very simple. All you have to do is to prepend <code>WINEPREFIX="$HOME/some-folder"</code> before the <code>wine</code> command. If that folder does not exist, Wine will create it for you. It is a good idea to double-quote the path. For instance, <code>WINEPREFIX="$HOME/wine-hdr" wine</code></div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=How_to_release_RawTherapee&diff=9849How to release RawTherapee2022-11-29T18:37:22Z<p>DrSlony: </p>
<hr />
<div><div class="pagetitle">How to Release RawTherapee</div><br />
<br />
# Tea<br />
# Pull and update<br />
# Run: <pre>./tools/generateTranslationDiffs</pre> Perform final language file updates.<br />
# Run: <pre>dos2unix rtdata/languages/* rtdata/profiles/*</pre><br />
# Update splash screen, <code>RELEASE_NOTES.txt</code>, AppData, language files, profiles, etc. Once ready, commit to new branch:<br />
#:<pre><br />
#::git checkout -b release-5.10<br />
#::git commit -a -m "Preparing for release 5.10-rc1"<br />
#::git push --set-upstream origin release-5.10</pre><br />
# Once others have revised the changes, merge this <code>release-5.10</code> branch into <code>releases</code>:<br />
#:<pre><br />
#::git checkout releases<br />
#::git pull<br />
#::git merge release-5.10</pre><br />
# Tag and push:<br />
#:<pre><br />
#::git tag -a "5.10-rc1" -m "Tagged RawTherapee 5.10-rc1"<br />
#::git push origin "5.10-rc1"<br />
#::git push</pre><br />
# Make a source tarball:<pre>./tools/generateSourceTarball</pre><pre>sha1sum rawtherapee-5.10-rc1.tar.xz > rawtherapee-5.10-rc1.tar.xz.sha1</pre><br />
# Over at GitHub, create a release for the new tag. Copy the description from the previous tag, updating the version as necessary. Attach the source tarball and hash file to the release: https://github.com/Beep6581/RawTherapee/tags<br />
# Upload the source tarball and hash file to the website, to <code>shared/source</code>.<br />
# Upload Linux/Windows/macOS installers/packages to the website, to <code>shared/builds</code>.<br />
# Update the website, see https://gitlab.com/patdavid/rawtherapee-web/-/blob/master/README.md<br />
## <code>cd</code> into your cloned website repo and run <code>hugo</code> (no arguments) to generate the static website in the <code>/public</code> folder.<br />
## Log in via ssh, <code>cd rawtherapee.com/web/</code> and run <code>./danger_cleanup_hugo.sh</code> to delete the contents of the <code>public</code> folder without deleting files placed there manually and used by third-party services (screenshots for appdata, etc).<br />
## Then upload everything from inside your local <code>public</code> folder.<br />
<br />
When ready for a final release (5.10, not 5.10-rc1), do as above, merge <code>release-5.10</code> into <code>releases</code>, tag <code>5.10</code>, finally deleted branch <code>release-5.10</code>. Never delete branch <code>releases</code>.<br />
<br />
Once done with the release, you may need to merge <code>releases</code> back into <code>dev</code> if new commits were made exclusively to the <code>release-5.10</code> branch. To do that,<br />
# <code>git checkout releases</code>,<br />
# Edit <code>RELEASE_NOTES.txt</code> and revert the contents to describe the development build (<code>git show dev:RELEASE_NOTES.txt</code>).<br />
# Edit the splash screen in Inkscape to revert it to the dev one.<br />
# <code>git commit -a -m "Preparing to merge back to dev"</code><br />
# <code>git checkout dev</code><br />
# <code>git merge releases</code><br />
# <code>git push</code></div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=How_to_release_RawTherapee&diff=9848How to release RawTherapee2022-11-27T19:31:20Z<p>DrSlony: </p>
<hr />
<div><div class="pagetitle">How to Release RawTherapee</div><br />
<br />
# Tea<br />
# Pull and update<br />
# Run: <pre>./tools/generateTranslationDiffs</pre> Perform final language file updates.<br />
# Run: <pre>dos2unix rtdata/languages/* rtdata/profiles/*</pre><br />
# Update splash screen, <code>RELEASE_NOTES.txt</code>, AppData, language files, profiles, etc. Once ready, commit to new branch:<br />
#:<pre><br />
#::git checkout -b release-5.10<br />
#::git commit -a -m "Preparing for release 5.10-rc1"<br />
#::git push --set-upstream origin release-5.10</pre><br />
# Once others have revised the changes, merge this <code>release-5.10</code> branch into <code>releases</code>:<br />
#:<pre><br />
#::git checkout releases<br />
#::git pull<br />
#::git merge release-5.10</pre><br />
# Tag and push:<br />
#:<pre><br />
#::git tag -a "5.10-rc1" -m "Tagged RawTherapee 5.10-rc1"<br />
#::git push origin "5.10-rc1"<br />
#::git push</pre><br />
# Make a source tarball:<pre>./tools/generateSourceTarball</pre><pre>sha1sum rawtherapee-5.10-rc1.tar.xz > rawtherapee-5.10-rc1.tar.xz.sha1</pre><br />
# Over at GitHub, create a release for the new tag. Copy the description from the previous tag, updating the version as necessary. Attach the source tarball and hash file to the release: https://github.com/Beep6581/RawTherapee/tags<br />
# Upload the source tarball and hash file to the website, to <code>shared/source</code>.<br />
# Upload Linux/Windows/macOS installers/packages to the website, to <code>shared/builds</code>.<br />
# Update the website, see https://gitlab.com/patdavid/rawtherapee-web/-/blob/master/README.md<br />
<br />
When ready for a final release (5.10, not 5.10-rc1), do as above, merge <code>release-5.10</code> into <code>releases</code>, tag <code>5.10</code>, finally deleted branch <code>release-5.10</code>. Never delete branch <code>releases</code>.<br />
<br />
Once done with the release, you may need to merge <code>releases</code> back into <code>dev</code> if new commits were made exclusively to the <code>release-5.10</code> branch. To do that,<br />
# <code>git checkout releases</code>,<br />
# Edit <code>RELEASE_NOTES.txt</code> and revert the contents to describe the development build (<code>git show dev:RELEASE_NOTES.txt</code>).<br />
# Edit the splash screen in Inkscape to revert it to the dev one.<br />
# <code>git commit -a -m "Preparing to merge back to dev"</code><br />
# <code>git checkout dev</code><br />
# <code>git merge releases</code><br />
# <code>git push</code></div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=How_to_release_RawTherapee&diff=9847How to release RawTherapee2022-11-27T19:29:58Z<p>DrSlony: </p>
<hr />
<div><div class="pagetitle">How to Release RawTherapee</div><br />
<br />
# Tea<br />
# Pull and update<br />
# Run: <pre>./tools/generateTranslationDiffs</pre> Perform final language file updates.<br />
# Run: <pre>dos2unix rtdata/languages/* rtdata/profiles/*</pre><br />
# Update splash screen, <code>RELEASE_NOTES.txt</code>, AppData, language files, profiles, etc. Once ready, commit to new branch:<br />
#:<pre><br />
#::git checkout -b release-5.9<br />
#::git commit -a -m "Preparing for release 5.9-rc1"<br />
#::git push --set-upstream origin release-5.9</pre><br />
# Once others have revised the changes, merge this <code>release-5.9</code> branch into <code>releases</code>:<br />
#:<pre><br />
#::git checkout releases<br />
#::git pull<br />
#::git merge release-5.9</pre><br />
# Tag and push:<br />
#:<pre><br />
#::git tag -a "5.9-rc1" -m "Tagged RawTherapee 5.9-rc1"<br />
#::git push origin "5.9-rc1"<br />
#::git push</pre><br />
# Make a source tarball:<pre>./tools/generateSourceTarball</pre><pre>sha1sum rawtherapee-5.9-rc1.tar.xz > rawtherapee-5.9-rc1.tar.xz.sha1</pre><br />
# Over at GitHub, create a release for the new tag. Copy the description from the previous tag, updating the version as necessary. Attach the source tarball and hash file to the release: https://github.com/Beep6581/RawTherapee/tags<br />
# Upload the source tarball and hash file to the website, to <code>shared/source</code>.<br />
# Upload Linux/Windows/macOS installers/packages to the website, to <code>shared/builds</code>.<br />
# Update the website, see https://gitlab.com/patdavid/rawtherapee-web/-/blob/master/README.md<br />
<br />
When ready for a final release (5.9, not 5.9-rc1), do as above, merge <code>release-5.9</code> into <code>releases</code>, tag <code>5.9</code>, finally deleted branch <code>release-5.9</code>. Never delete branch <code>releases</code>.<br />
<br />
Once done with the release, you may need to merge <code>releases</code> back into <code>dev</code> if new commits were made exclusively to the <code>release-5.9</code> branch. To do that,<br />
# <code>git checkout releases</code>,<br />
# Edit <code>RELEASE_NOTES.txt</code> and revert the contents to describe the development build (<code>git show dev:RELEASE_NOTES.txt</code>).<br />
# Edit the splash screen in Inkscape to revert it to the dev one.<br />
# <code>git commit -a -m "Preparing to merge back to dev"</code><br />
# <code>git checkout dev</code><br />
# <code>git merge releases</code><br />
# <code>git push</code></div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=How_to_release_RawTherapee&diff=9846How to release RawTherapee2022-11-27T18:34:39Z<p>DrSlony: </p>
<hr />
<div><div class="pagetitle">How to Release RawTherapee</div><br />
<br />
# Tea<br />
# Pull and update<br />
# Run: <pre>./tools/generateTranslationDiffs</pre> Perform final language file updates.<br />
# Run: <pre>dos2unix rtdata/languages/* rtdata/profiles/*</pre><br />
# Update splash screen, <code>RELEASE_NOTES.txt</code>, AppData, language files, profiles, etc. Once ready, commit to new branch:<br />
#:<pre><br />
#::git checkout -b release-5.9<br />
#::git commit -a -m "Preparing for release 5.9-rc1"<br />
#::git push --set-upstream origin release-5.9</pre><br />
# Once others have revised the changes, merge this <code>release-5.9</code> branch into <code>releases</code>:<br />
#:<pre><br />
#::git checkout releases<br />
#::git pull<br />
#::git merge release-5.9</pre><br />
# Tag and push:<br />
#:<pre><br />
#::git tag -a "5.9-rc1" -m "Tagged RawTherapee 5.9-rc1"<br />
#::git push origin "5.9-rc1"<br />
#::git push</pre><br />
# Make a source tarball:<pre>./tools/generateSourceTarball</pre><pre>sha1sum rawtherapee-5.9-rc1.tar.xz > rawtherapee-5.9-rc1.tar.xz.sha1</pre><br />
# Over at GitHub, create a release for the new tag. Copy the description from the previous tag, updating the version as necessary. Attach the source tarball and hash file to the release: https://github.com/Beep6581/RawTherapee/tags<br />
# Upload the source tarball and hash file to the website, to <code>shared/source</code>.<br />
# Upload Linux/Windows/macOS installers/packages to the website, to <code>shared/builds</code>.<br />
# Update the website, see https://gitlab.com/patdavid/rawtherapee-web/-/blob/master/README.md<br />
<br />
When ready for a final release (5.9, not 5.9-rc1), do as above, merge <code>release-5.9</code> into <code>releases</code>, tag <code>5.9</code>, finally deleted branch <code>release-5.9</code>. Never delete branch <code>releases</code>.<br />
<br />
Once done with the release, you may need to merge <code>releases</code> back into <code>dev</code> if new commits were made exclusively to the <code>release-5.9</code> branch. To do that,<br />
# <code>git checkout releases</code>,<br />
# Edit <code>RELEASE_NOTES.txt</code> and revert the contents to describe the development build (<code>git show dev:RELEASE_NOTES.txt</code>).<br />
# Edit the splash screen in Inkscape to revert it to the dev one.<br />
# <code>git commit -a -m "Preparing to merge back to dev"</code><br />
# <code>git checkout dev</code><br />
# <code>git checkout merge releases</code><br />
# <code>git push</code></div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=How_to_release_RawTherapee&diff=9845How to release RawTherapee2022-11-27T18:19:33Z<p>DrSlony: </p>
<hr />
<div><div class="pagetitle">How to Release RawTherapee</div><br />
<br />
# Tea<br />
# Pull and update<br />
# Run: <pre>./tools/generateTranslationDiffs</pre> Perform final language file updates.<br />
# Run: <pre>dos2unix rtdata/languages/* rtdata/profiles/*</pre><br />
# Update splash screen, <code>RELEASE_NOTES.txt</code>, AppData, language files, profiles, etc. Once ready, commit to new branch:<br />
#:<pre><br />
#::git checkout -b release-5.9<br />
#::git commit -a -m "Preparing for release 5.9-rc1"<br />
#::git push --set-upstream origin release-5.9</pre><br />
# Once others have revised the changes, merge this <code>release-5.9</code> branch into <code>releases</code>:<br />
#:<pre><br />
#::git checkout releases<br />
#::git pull<br />
#::git merge release-5.9</pre><br />
# Tag and push:<br />
#:<pre><br />
#::git tag -a "5.9-rc1" -m "Tagged RawTherapee 5.9-rc1"<br />
#::git push origin "5.9-rc1"<br />
#::git push</pre><br />
# Make a source tarball:<pre>./tools/generateSourceTarball</pre><pre>sha1sum rawtherapee-5.9-rc1.tar.xz > rawtherapee-5.9-rc1.tar.xz.sha1</pre><br />
# Create a release for the new tag. Copy the description from the previous tag, updating the version as necessary. Attach the source tarball and hash file to the release: https://github.com/Beep6581/RawTherapee/tags<br />
# Upload the source tarball and hash file to the website, to <code>shared/source</code>.<br />
# Upload Linux/Windows/macOS installers/packages to the website, to <code>shared/builds</code>.<br />
# Update the website, see https://gitlab.com/patdavid/rawtherapee-web/-/blob/master/README.md<br />
<br />
When ready for a final release (5.9, not 5.9-rc1), do as above, merge <code>release-5.9</code> into <code>releases</code>, tag <code>5.9</code>, finally deleted branch <code>release-5.9</code>. Never delete branch <code>releases</code>.<br />
<br />
Once done with the release, you may need to merge <code>releases</code> back into <code>dev</code> if new commits were made exclusively to the <code>release-5.9</code> branch. To do that,<br />
# <code>git checkout releases</code>,<br />
# Edit <code>RELEASE_NOTES.txt</code> and revert the contents to describe the development build (<code>git show dev:RELEASE_NOTES.txt</code>).<br />
# Edit the splash screen in Inkscape to revert it to the dev one.<br />
# <code>git commit -a -m "Preparing to merge back to dev"</code><br />
# <code>git checkout dev</code><br />
# <code>git checkout merge releases</code><br />
# <code>git push</code></div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=MacOS&diff=9844MacOS2022-11-27T17:35:55Z<p>DrSlony: </p>
<hr />
<div><div class="pagetitle">MacOS</div><br />
<br />
This page details instructions for compiling RawTherapee on '''macOS''' systems. There are also separate pages with instructions for compiling on [[Linux]] and [[Windows]]. This guide details the '''what''' and '''how''' parts of compilation. For the '''why''' and explanations of these commands, for a list of dependencies, CMake options and other information, please refer to the detailed [[Linux]] article.<br />
<br />
When in doubt, [[IRC | join us on IRC]] and ask a human!<br />
<br />
For instructions on cloning the source, choosing branches, configuring CMake and doing the actual compilation, see these sections in the [[Linux]] guide. The information below is in addition to that.<br />
<br />
== Dependencies ==<br />
<br />
See the list of dependencies in the [[Linux#Dependencies|Compiling in Linux]] article.<br />
<br />
=== Homebrew ===<br />
<br />
The following command installs dependencies for RawTherapee:<br />
<code><br />
brew install gtk+3 gtkmm3 gtk-mac-integration adwaita-icon-theme libsigc++ little-cms2 libiptcdata fftw lensfun wget llvm cmake expat pkgconfig shared-mime-info<br />
</code><br />
<br />
<div class="row small-uncollapse large-uncollapse"><br />
{{warning|1=<br />
<span class="langsavail">OpenMP</span><br />
<br><br />
Libomp v.12.0 has a bug. Use the following command to install the previous version 11.1.0: <br />
<div style="margin-left: 2em;"><code>curl -L https://github.com/Homebrew/homebrew-core/raw/679923b4eb48a8dc7ecc1f05d06063cd79b3fc00/Formula/libomp.rb -o libomp.rb && brew install libomp.rb</code><br />
}}</div><br />
<br />
* '''Configuring the homebrew build environment for Apple Silicon "M1"'''<br />
: To your <code>cmake</code> command add the following flags:<br />
:: <code>-DLOCAL_PREFIX:STRING="/opt/homebrew"</code><br />
:: <code>-DCMAKE_OSX_ARCHITECTURES=arm64</code><br />
<br />
=== MacPorts ===<br />
<br />
{{warning|1=If you want to use Homebrew to manage prerequisite libraries, do not use MacPorts or issue any <code>sudo port</code> commands.}} <br />
<br />
Tested on OS X 10.9 and newer.<br />
* '''Prerequisites'''<br />
** Xcode Developer Tools & Command Line Tools<br />
** MacPorts<br />
*** Detailed instructions on setting up MacPorts and the developer tools are available on the [https://www.macports.org MacPorts website].<br />
* '''Configure MacPorts:''' <br />
: Add the following line to /opt/local/etc/macports/variants.conf<br />
:: <code>+quartz -x11 -gnome +openmp</code><br />
<br />
* '''Dependencies'''<br />
: To install the dependencies, run from the terminal:<br />
:: <code>sudo port install git cmake clang-11 libomp gtk3 gtkmm3 gtk-osx-application-gtk3 adwaita-icon-theme libsigcxx2 lcms2 libiptcdata fftw-3-single lensfun</code><br />
: If compiling on Xcode 9.2 you will also need to do:<br />
:: <code>sudo port install ld64 +ld64_xcode</code><br />
<br />
* '''Configuring compile system for MacPorts'''<br />
: To your <code>cmake</code> command add the following flag:<br />
:: <code>-DLOCAL_PREFIX:STRING="/opt/local"</code><br />
<br />
== Compiling ==<br />
<br />
See the [[Linux#Compiling:_The_Manual_Way|Compiling in Linux]] article for instructions on how to '''clone''' the source code, choose a '''branch''' and how to configure '''CMake'''. Ignore the '''''Now you are ready to compile''''' code on that page and follow the code on this page.<br />
<br />
RawTherapee is compiled by the '''clang''' compiler. It may come with XCode or be installed as a part of '''llvm'''. Be advised that Apple uses a versioning scheme for '''Apple clang''' which is inconsistent with '''llvm clang'''. To figure out which compiler to use, check your system compiler first:<br />
<br />
<div style="margin-left: 2em;"><pre><br />
-> which clang<br />
/usr/bin/clang<br />
<br />
-> /usr/bin/clang --version<br />
Apple clang version 11.0.0 (clang-1100.0.33.17)<br />
Target: x86_64-apple-darwin18.7.0<br />
Thread model: posix<br />
InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin<br />
</pre><br />
</div><br />
<br />
If you see '''Apple clang''' mentioned in the top line of the '''clang''' version output, note the version number it specifies and refer to [https://en.wikipedia.org/wiki/Xcode#Xcode_7.0_-_12.x_(since_Free_On-Device_Development) this Wikipeda table] for the mapping between '''Apple clang''' and '''llvm clang''' versions. This knowledge may be useful when tracing any compilation errors.<br />
<br />
If you want to upload a generic `x86_64` build or otherwise share it with others, you must use<br />
: <code>-DPROC_TARGET_NUMBER="1"</code><br />
and set the processor label manually by setting<br />
: <code>-DPROC_LABEL="generic processor"</code><br />
<br />
If you want to compile a CPU-optimized for yourself only, or build for the Apple `M1`, then use<br />
: <code>-DPROC_TARGET_NUMBER="2"</code><br />
and then the processor label would be irrelevant, you could skip it.<br />
<br />
If you wish to [https://developer.apple.com/support/code-signing/ codesign] your build, add your details to the CMake command:<br />
: <code>-DCODESIGNID="Developer ID Application: Firstname Lastname (XXXXXXXXXX)"</code><br />
The app and the generated dmg (Apple Disk Image) will be codesigned.<br />
<br />
To [https://developer.apple.com/documentation/security/notarizing_your_app_before_distribution/customizing_the_notarization_workflow?language=objc notarize] your codesigned build, include your app-specific notarial credential in the CMake command:<br />
: <code>-DNOTARY="--username user@mail.com --password abcd-efgh-ijkl-mnop"</code><br />
The app and dmg will be notarized (scanned for malware) and stapled (have the notarization ticket attached).<br />
<br />
=== Compile RawTherapee ===<br />
<br />
Now you are ready to compile:<br />
<pre style="white-space: pre-wrap">cd ~/repo-rt<br />
rm -rf build<br />
mkdir build && cd build<br />
cmake -DCMAKE_BUILD_TYPE="release" \<br />
-DPROC_TARGET_NUMBER="1" \<br />
-DPROC_LABEL="generic processor" \<br />
-DCACHE_NAME_SUFFIX="5-dev" \<br />
-DCMAKE_C_COMPILER="clang" \<br />
-DCMAKE_CXX_COMPILER="clang++" \<br />
-DWITH_LTO="OFF" \<br />
-DLENSFUNDBDIR="share/lensfun" \<br />
-DCMAKE_OSX_DEPLOYMENT_TARGET=10.15 \<br />
..<br />
make -j$(sysctl -n hw.ncpu) install<br />
sudo make macosx_bundle<br />
</pre><br />
<br />
To compile RawTherapee with a specific llvm '''clang''' version (e.g. installed via homebrew), use the following '''cmake''' command. When doing so, make sure these settings point to the appropriate paths:<br />
<br />
* Using llvm 10 from homebrew:<br />
<br />
<div style="margin-left: 2em;"><pre><br />
-DCMAKE_C_COMPILER="/usr/local/Cellar/llvm/10.0.1_1/bin/clang"<br />
-DCMAKE_CXX_COMPILER="/usr/local/Cellar/llvm/10.0.1_1/bin/clang++"<br />
-DCMAKE_AR="/usr/local/Cellar/llvm/10.0.1_1/bin/llvm-ar"<br />
-DCMAKE_RANLIB="/usr/local/Cellar/llvm/10.0.1_1/bin/llvm-ranlib"<br />
</pre></div><br />
<br />
* The '''cmake''' command:<br />
<br />
<div style="margin-left: 2em;"><pre><br />
export PKG_CONFIG_PATH=/usr/local/opt/libffi/lib/pkgconfig:/usr/local/opt/expat/lib/pkgconfig && \<br />
cmake .. -DCMAKE_BUILD_TYPE="release" \<br />
-DPROC_TARGET_NUMBER="2" \<br />
-DCACHE_NAME_SUFFIX="5.8-dev" \<br />
-DCMAKE_C_COMPILER="/usr/local/Cellar/llvm/10.0.1_1/bin/clang" \<br />
-DCMAKE_CXX_COMPILER="/usr/local/Cellar/llvm/10.0.1_1/bin/clang++" \<br />
-DWITH_LTO="ON" \<br />
-DLENSFUNDBDIR="/Applications/RawTherapee.app/Contents/Resources/share/lensfun" \<br />
-DCMAKE_BUILD_TYPE=Release \<br />
-DOpenMP_C_FLAGS=-fopenmp=libomp \<br />
-DOpenMP_CXX_FLAGS=-fopenmp=libomp \<br />
-DOpenMP_C_LIB_NAMES="libomp" \<br />
-DOpenMP_CXX_LIB_NAMES="libomp" \<br />
-DOpenMP_libomp_LIBRARY="/usr/local/lib/libomp.dylib" \<br />
-DOpenMP_CXX_FLAGS="-Wno-pass-failed -Wno-deprecated-register -Xpreprocessor -fopenmp /usr/local/lib/libomp.dylib -I/usr/local/include" \<br />
-DOpenMP_CXX_LIB_NAMES="libomp" \<br />
-DOpenMP_C_FLAGS="-Wno-pass-failed -Wno-deprecated-register -Xpreprocessor -fopenmp /usr/local/lib/libomp.dylib -I/usr/local/include" \<br />
-DCMAKE_VERBOSE_MAKEFILE:BOOL=ON \<br />
-DCMAKE_EXE_LINKER_FLAGS="-L/usr/local/opt/libffi/lib -L/usr/local/lib" \<br />
-DCMAKE_AR="/usr/local/Cellar/llvm/10.0.1_1/bin/llvm-ar" \<br />
-DCMAKE_RANLIB="/usr/local/Cellar/llvm/10.0.1_1/bin/llvm-ranlib" \<br />
-DCMAKE_OSX_DEPLOYMENT_TARGET=10.15<br />
</pre></div><br />
<br />
=== From-Scratch Method ===<br />
<br />
* This [https://raw.githubusercontent.com/Benitoite/RTdeps/master/macbuildRT.sh] complete list of commands may optionally be used to perform a from-scratch build of RawTherapee and its dependencies on macOS 10.15.3 / Xcode 11.<br />
* A JDK[https://www.oracle.com/technetwork/java/javase/downloads/jdk13-downloads-5672538.html] must be installed.<br />
* Xcode 11.1+ [https://developer.apple.com/xcode] must be installed<br />
<br />
=== Run and Share RawTherapee ===<br />
<br />
You will find a disk image in the build directory; this is the distribution release and can be run on any machine which meets the architecture requirements you specified in variants.conf earlier.<br />
<br />
The generated zip file is named according to this template:<br />
: RawTherapee_OSX_'''<minimum supported macOS version>'''_64_'''<RawTherapee version>'''.dmg.zip <br />
: RawTherapee_OSX_10.9_64_5.8-94-g4dbbc4053.dmg.zip<br />
<br />
Upload the zip archive to http://filebin.net/ and [https://github.com/Beep6581/RawTherapee/issues/new open a new issue on our GitHub page] with the link so that we can upload it to the website.<br />
<br />
== macOS installation ==<br />
<br />
To install the RawTherapee application, open the .dmg and drag the RawTherapee app onto the <code>/Applications</code> folder.<br />
<br />
To use the optional rawtherapee-cli command line interface, move rawtherapee-cli into a folder in your $PATH and install the RawTherapee app as above.<br />
<br />
If the workspace is too small to read, you must change the HiDPI settings in RawTherapee: <br />
Preferences > General, then enable pseudo HiDPI mode. [https://rawpedia.rawtherapee.com/Preferences#Appearance]</div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=Editor&diff=9839Editor2022-11-22T19:42:52Z<p>DrSlony: </p>
<hr />
<div><div class="pagetitle">The Editor</div><br />
<br />
[[File:Rt 55 trains.png|none|frame|link=|class=heroed|The Image Editor tab in RawTherapee 5.5.]]<br />
<br />
== Introduction ==<br />
<br />
The Image Editor tab is where you tweak your photos. By default RawTherapee is in "Single Editor Tab Mode, Vertical Tabs" (SETM/VT) which is more memory-efficient and lets you use the [[Editor#The_Filmstrip|Filmstrip]] (described below). You can switch to "Multiple Editor Tabs Mode" (METM) by going to "[[Preferences#Layout|Preferences > General > Layout]]", however each Editor tab will require a specific amount of RAM relative to the image size and the tools you use, and also the Filmstrip is hidden in this mode, so we recommend you first give SETM a try.<br />
<br />
== The Preview Panel ==<br />
<br />
The central panel shows a preview of the image being edited. This preview is generated from raw data if such is available. It reflects the adjustments made by the tools in the [[Editor#Toolbox|Toolbox]]. Note that the effects of some tools are only accurately visible when you are zoomed in to 1:1 (100%) or more; these tools are marked in the interface with a "1:1" icon [[File:One-to-one-small.png|Zoom 1:1]] alongside the tool's name.<br />
<br />
When opening an image, RawTherapee loads the tool settings from the sidecar file if one exists, else it applies a default sidecar file as specified in "[[Preferences#Default_Processing_Profile|Preferences > Image Processing > Default Processing Profile]]". When you close the image (which happens automatically if you open a different image or if you close RawTherapee) the current tool settings are automatically saved to a sidecar file as specified in "[[Preferences#Processing_Profile_Handling|Preferences > Image Processing > Processing Profile Handling]]".<br />
<br />
=== Eek! My Raw Photo Looks Different than the Camera JPEG ===<br />
<br />
When opening a raw photo you may notice that it looks different from your camera's JPEG, or from what other software show when viewing the same raw photo. In some cases this difference is minute, but in other cases it could be significant - the image could be darker, lack contrast, be less sharp and more noisy. What gives?<br />
<br />
There are three things you must know first to understand what is happening here:<br />
# Your camera does not show you the real raw data when you shoot raw photos. It processes the raw image in many ways before presenting you with the histogram and the preview on your camera's display. Even if you set all the processing features which your camera's firmware allows you to tweak to their neutral, "0" positions, what you see is still not an unprocessed image. Exactly what gets applied depends on the choices made by your camera's engineers and company management, but usually this includes a custom tone curve, saturation boost, sharpening and noise reduction. Some cameras, particularly low-end ones and [http://en.wikipedia.org/wiki/Micro_Four_Thirds_system Micro Four-Thirds system], may also apply lens distortion correction to not only fix [http://en.wikipedia.org/wiki/Distortion_(optics)#Radial_distortion barrel and pincushion distortion] but also to hide dark corners caused by severe [http://en.wikipedia.org/wiki/Vignetting vignetting] or by the [https://en.wikipedia.org/wiki/Lens_hood lens hood]. Most cameras also underexpose every photo you take by anywhere from -0.3EV to -1.3EV or more, in order to gain headroom in the highlights. When your camera (or other raw editing software) processes the raw file it compensates for this by increasing exposure compensation by the same amount.<br />
# When shooting a raw photo, most cameras embed within the raw file a full-resolution JPEG image with tone curves and other adjustments applied. Some raw files contain as many as three JPEG images differing only in resolution. Most cameras offer storing photos in one of three modes: "RAW", "JPEG", or "RAW+JPEG". The embedded JPEG image discussed here is stored within the raw file even in just "RAW" mode! When you open raw files in other software, what you are usually seeing is '''not''' the raw data, but the embedded, processed JPEG image! Examples of software which are either incapable of or which in their default settings do not show you the real raw data: [http://en.wikipedia.org/wiki/IrfanView IrfanView], [http://en.wikipedia.org/wiki/XnView XnView], [http://en.wikipedia.org/wiki/Gwenview Gwenview], [http://en.wikipedia.org/wiki/Geeqie Geeqie], [http://en.wikipedia.org/wiki/Eye_of_GNOME Eye of GNOME], [http://en.wikipedia.org/wiki/F-Spot F-Spot], [http://en.wikipedia.org/wiki/Shotwell_(software) Shotwell], [http://en.wikipedia.org/wiki/GThumb gThumb], etc. It is worth mentioning at this point that if you shoot in "RAW+JPEG" mode then you could in fact be wasting space on your memory card and gaining nothing for it, as your raw files most likely already contain an embedded JPEG identical to the external one saved in "RAW+JPEG" mode.<br />
# Most raw development programs (programs which do read the real raw data instead of just reading the embedded JPEG) apply some processing to it, such as a base tone curve, even at their most neutral settings, thereby making it impossible for users to see the real, untouched contents of their raw photos. Adobe Lightroom is an example. Comparing RawTherapee's real [[Neutral|neutral]] image to a pseudo-neutral one from these other programs will expose the differences.<br />
<br />
RawTherapee, on the other hand, is capable of showing you the real raw image in the main preview, leaving the way you want this data processed up to you. When you use the "[[Neutral]]" processing profile you will see the demosaiced image with camera white balance in your working color space with no other modifications. You can even see the non-demosaiced image by setting the [[Demosaicing#Method|demosaicing method]] to "None".<br />
<br />
To provide you with a more aesthetically pleasing starting point, RawTherapee by default uses the [[Auto-Matched_Curve|Auto-Matched Curve]] processing profile, which automatically generates a tone curve to make the tones of the raw image match those of the embedded JPEG, if one exists. If one does not exist, you can use the [[Standard_Film_Curve|Standard Film Curve]] processing profile, which applies a curve which looks good in most cases. Choose the sub-type (ISO Low/Medium/High) depending on how noisy your image is.<br />
<br />
=== Scrollable Toolbars ===<br />
<br />
The toolbars above and below the main preview hold a certain number of buttons and other widgets which might not fit on lower resolution screens. {{:Scrollable Toolbar}}<br />
<br />
=== Preview Background Color ===<br />
<br />
[[File:Rt59 preview background all.png|none]]<br />
<br />
The background color of the preview panel may be changed to allow you to better judge how the image tones will appear when the saved image is viewed on a website (or image viewer, or print) of a similar background color.<br />
<br />
This choice also applies to the cropped-off area, if the image is cropped. See "[[Preferences#Appearance|Preferences > General > Appearance > Crop mask color]]".<br />
<br />
Available options:<br />
* theme-based (see [[Preferences#Appearance|Preferences > General > Appearance]]),<br />
* black,<br />
* [https://en.wikipedia.org/wiki/Middle_gray L* middle grey],<br />
* white.<br />
<br />
=== Preview Channel ===<br />
<br />
[[File:Rt59_preview_channel_all.png|none]]<br />
<br />
The preview can be toggled to show one of the following channels:<br />
* red,<br />
* green,<br />
* blue,<br />
* luminosity, which is calculated as 0.299*R + 0.587*G + 0.114*B.<br />
<br />
Preview of individual channels may be helpful when editing RGB curves, planning black/white conversion using the channel mixer, evaluating image noise, etc. Luminosity preview is helpful to instantly view the image in black and white without altering development parameters, to see which channel might be clipping or for aesthetic reasons.<br />
<br />
=== Preview Mask ===<br />
<br />
[[File:Rt59_preview_mask_all.png|none]]<br />
<br />
Available options:<br />
* Focus mask, which shows which areas are in focus (based on how sharp they appear),<br />
* Sharpening contrast mask, which visualizes the mask which decides which areas are affected by sharpening. See [[Sharpening#Contrast_Mask|Sharpening > Contrast Mask]].<br />
* Clipped shadow indication.<br />
* Clipped highlight indication.<br />
<br />
{{:Clipping_Indication}}<br />
<br />
[[Image:Preview_6_focus_2.jpg|Focus mask indicating the focusing plane|thumb]]<br />
<br />
The focus mask is designed to highlight areas of the image which are in focus. Naturally, focused areas are sharper, so the sharp areas are highlighted. The focus mask is more accurate on images with a shallow depth of field, low noise and at higher zoom levels. To improve detection accuracy for noisy images, evaluate at smaller zoom, around the 10-30% range. The current implementation analyzes the preview image, which is rescaled from the original captured size down to what you see on screen. When zoomed less than 100%, the preview image is downscaled, a side-effect of which is the apparent reduction of noise. You can take advantage of this to help identify truly sharp details, rather than noise itself which may introduce a false micro texture. At the same time, downscaling compresses larger scale details into a smaller size, and it may introduce aliasing artifacts, both of which could lead to false positives. You can increase your confidence by viewing the mask at various zoom levels. It is not always fault proof, but can be helpful in many cases. Due to these caveats, be sure to double-check your images if you decide to delete them based on the focus mask.<br />
<br />
=== Detail Window ===<br />
<br />
The "New detail window" button [[File:Window-add.png]], situated below the main preview next to the zoom buttons, opens a new viewport over the main preview of an adjustable size and of adjustable zoom. This lets you work on the photo zoomed-to-fit while examining several areas of interest at a 100% zoom (or even more). The benefit of using this feature is particularly important to users with slower machines, though not only them, as the zoomed-out main preview takes a shorter amount of time to update than if you were to zoom it to 100% because working at a zoom level less than 100% excludes certain slow tools, such as Noise Reduction, while the little detail windows zoomed to 100% do include all tools and are fast to update because of their small size. This allows you can use the main preview for your general exposure tweaks where it is necessary to see the whole image, and one or more detail windows to get sharpening and/or noise reduction just right.<br />
<br />
=== Preview Refresh Delay ===<br />
<br />
Changing any tool's parameters sends a signal for the preview image to be updated accordingly. Imagine what would happen if there was no "delay period", and you dragged, for example, the exposure compensation slider from 0.00 to +0.60. A signal would be sent to update the preview for every single change of that value - for +0.01, +0.02, ... +0.59, +0.60. Updating the preview 60 times would be completely unnecessary and actually take longer than it takes you to move the slider. This is especially true for more complicated tools, such as noise reduction, where a preview update can take even a second (depending on your CPU and preview size). The solution is for RawTherapee to wait for a very short period from the moment you stop moving a slider (you don't have to let go of it, pausing movement is enough) until the moment it sends a signal for the preview to be refreshed.<br />
<br />
We have introduced two parameters which control the length of this waiting period:<br />
; AdjusterMinDelay<br />
: Default value = 100ms.<br />
: This is used for tools with a very fast response time, for example the exposure compensation slider.<br />
; AdjusterMaxDelay<br />
: Default value = 200ms.<br />
: This is used for tools with a slow response time, for example the CIECAM02 sliders.<br />
<br />
You can adjust both of these values in the options file in the [[File_Paths|config folder]].<br />
<br />
== The Left Panel ==<br />
<br />
To the left is a panel which optionally shows the main histogram ("''Preferences > General > Layout > Histogram in left panel''"), and always shows the ''Navigator'', ''History'' and ''Snapshots''.<br />
You can hide this panel using the [[Image:panel-to-left.png|Hide left panel icon]] hide icon, or its [[Keyboard Shortcuts|keyboard shortcut]].<br />
<br />
=== Main Histogram ===<br />
<br />
[[File:Rt57 histogram wide labeled.png|none|frame|class=heroed|Histogram showing all 3 channels and luminosity.]]<br />
<br />
[[File:RT57 histogram ani.gif|frame|The histogram in RawTherapee 5.7, showing a histogram of the raw data in all three modes - linear-linear, linear-log and log-log. We can see that the raw file is not clipped.]]<br />
<br />
[[File:Rt histogram rgbindicator.png|frame|The RGB indicator shows the position in the histogram of the R, G, B and L values of the pixel your cursor is hovering over.]]<br />
<br />
A histogram in photography is a graphical representation of the number of pixels of a given value. Typically the horizontal axis represents the range of possible values while the vertical axis represents the count of pixels with that value. The axes need not be linear - RawTherapee can also scale the histogram logarithmically.<br />
<br />
Regardless of the photo's bit depth, the histogram itself has a precision of 256 sampling bins. To understand this, let us look at the example of a 16-bit image using integer precision. Its range of possible values spans from 0 to 65535 (2^16 = 65536 possible values, and since 0 is a possible minimum value then the maximum value is 65535). Drawing a histogram using 16-bit precision would mean that it would need to be 65535 pixels wide to faithfully represent the data, and no screen today is anywhere near that wide. Instead, all pixels with values from 0 to 255 (65535/256*1) are grouped into the first "bin". The second bin consists of a count of all pixels with values from 256 to 511 (65535/256*2). The third bin represents values 512 to 767 (65535/256*3). And so on until bin 256. This happens regardless of the input image's bit depth - and RawTherapee's engine uses 32-bit floating-point precision anyway.<br />
<br />
The main histogram can simultaneously show one or more of the following:<br />
* [[File:Histogram-red-on-small.svg]] the red channel,<br />
* [[File:Histogram-green-on-small.svg]] the green channel,<br />
* [[File:Histogram-blue-on-small.svg]] the blue channel,<br />
* [[File:Histogram-silver-on-small.svg]] CIELab luminance,<br />
* [[File:Histogram-gold-on-small.svg]] [http://en.wikipedia.org/wiki/Chromaticity chromaticity].<br />
* [[File:Histogram-bayer-on-small.svg]] red, green and blue channels of the source raw image before demosaicing.<br />
<br />
The histogram shows the channels listed above using the gamma-corrected output profile when the gamut button [[File:Gamut-hist.png]] is disabled (default), or using the working profile when the button is enabled. The status of this button also affects the values shown in the Navigator panel, as well as the clipped shadow [[File:Warning-shadows.png]] and [[File:Warning-highlights.png]] highlight indicators. It does not affect the raw histogram.<br />
<br />
Like water in a pipeline, image data flows through RawTherapee from the input file through various stages, most of which the user can control, to the output. The output could be the image saved in a file, or the image displayed on your screen. Each stage affects the color data. The histogram allows you to visualize this data at several stages. By default, the histogram shows color data as it will appear if you save the output image, including processing done at all intermediate stages. By enabling the gamut button [[File:Gamut-hist.png]] you can peak at the data at the early stage where it gets converted into the working space. You can even look at the raw data before any transformations or demosaicing are applied.<br />
<br />
Let's examine the large histogram example above. Though it actually shows four histograms (red, green, blue and luminance), focus on one histogram at a time. The horizontal axis represents the possible values of the histogram, where "A" are the darkest values possible, "C" the mid-tones, and "E" the brightest possible values. The position of the histogram line on the vertical axis represents how many pixels have that value. We can see that there are zero pixels in the red channel with values around "A" (from zero to very dark), because the histogram line lies right along the bottom. There is a significant number of pixels where the red channel is dark (between A and B), and a significant number where it is light (around D). Then, importantly, there is a spike at the right end of the histogram, at E - it tells us that a large number of pixels have maximal red values - they are clipped.<br />
<br />
Generally speaking, you should care when clipping occurs on skin, and not care when it's due to [https://en.wikipedia.org/wiki/Specular_highlight specular highlights]. If a histogram shows clipping, and if you care about the clipped regions, you should start by establishing where the clipping occurs. Check the raw histogram - are any channels clipped? If yes, then maybe [[Exposure#Highlight_Reconstruction|highlight reconstruction]] can help. If the raw histograms are not clipped, then all the required information is intact, and it is some stage downstream in the pipeline which causes clipping. Ensure your working profile's gamut is large enough by enabling the gamut button [[File:Gamut-hist.png]] to see histograms at the working profile stage of the pipeline. You might want to temporarily apply the [[Neutral]] profile to disable all the tools while checking, then revert. If your working space is not causing clipping (the default working space is ProPhoto and it's huge), then it's likely your adjustments which are causing clipping. Reduce exposure, go easy on the curves, use dynamic range compression if necessary.<br />
<br />
Knowing how to read a histogram is a basic and very useful skill, as it can point out issues with your image regardless of how dim or miscalibrated your monitor may be.<br />
<br />
To help you visualize the data, the histogram (as of RawTherapee 5.5) has three modes which scale the data in the x and y axes differently:<br />
* [[File:Histogram-mode-linear-small.png]] Linear-linear mode. You find gridlines at halves, quarters, eighths and sixteenths, depending on the size of the histogram.<br />
* [[File:Histogram-mode-logx-small.png]] Linear-log mode. The x-axis is linear, the y-axis and the horizontal gridlines are scaled logarithmically. The position of the gridlines still corresponds to the halves, quarters, etc.<br />
* [[File:Histogram-mode-logxy-small.png]] Log-log mode. Both the x- and y-axes are scaled logarithmically. The gridlines are not scaled logarithmically, but correspond to [https://en.wikipedia.org/wiki/Exposure_value stops] - with every gridline the value doubles, so there are lines for the values 1, 3, 7, 15, 31, 63, and 127 (<code>pow(2.0,i) - 1)</code>).<br />
<br />
When there is a disproportionately bright area relative to the rest of the image, it will show up as a spike in the histogram. If you want to show this on a histogram with a linear y axis, the spike may push the lesser values down the y-axis, making them difficult to see. Switch to one of the log modes to scale the data and help you get a better overview of all values.<br />
<br />
The histogram can be moved to the left/right panel from "''Preferences > General > Layout > Histogram in left panel''".<br />
<br />
==== Raw Histograms ====<br />
<br />
Raw files contain a dump of data captured by the sensor and quantified by the analog-to-digital converter. The raw file as a container has a bit depth of its own, typically 16-bit, while the data it contains could have a lower bit depth - typically it is 12-bit (0-4096) or 14-bit (0-16384). To display the data from a raw file as an image, one of the several key bits of information required to process the data correctly are the black and white levels. The black level is not necessarily 0, as the sensor and camera electronics produce digital noise, so the noise floor may lie for instance at 512. The white level is also not necessarily 16384; it depends on various things, and may lie for instance at 16300. For more information, see the articles [[Demosaicing]] and [[Adding Support for New Raw Formats]] (especially the header of the <code>camconst.json</code> file). The black and white level values used by RawTherapee are hierarchically set by looking in several places: in <code>dcraw.c</code>, inside the raw file's metadata, and in <code>camconst.json</code> (latter takes precedence). Furthermore, the user can tweak the raw [[Raw Black Points|black]] and [[Raw White Points|white]] levels from within RawTherapee.<br />
<br />
The raw histograms show data after black level subtraction. The right end of the histogram is anchored on the white level. The raw histograms are affected by the detected black and white levels as well as by the black and white level adjustments made by the user in RawTherapee.<br />
<br />
When examining the raw histogram, you may also want to set the demosaicing method to "none". This will reveal the sensor pattern in the preview, and also cause the [[Editor#Navigator|Navigator]] panel to show the raw RGB values of the pixel currently being hovered over. These values are affected by the detected black and white levels as well as by the black level adjustments made by the user in RawTherapee, but they are not affected by the white level adjustments ("white-point correction") made by the user in RawTherapee.<br />
<br />
=== Navigator ===<br />
<br />
The ''Navigator'' panel shows a thumbnail of the currently opened image, and RGB, HSV and Lab values of the pixel your cursor is currently hovering over.<br />
<br />
The values shown in the main histogram and Navigator panel are either those of the working profile or of the gamma-corrected output profile, depending on the state of the gamut button [[File:Gamut-hist.png]] located in the toolbar above the main preview. When the gamut button is enabled the working profile is used, otherwise the gamma-corrected output profile is used.<br />
<br />
By clicking on the values in the Navigator you can cycle between these three formats:<br />
* [0-255]<br />
* [0-1]<br />
* [%]<br />
<br />
RawTherapee 5.1 onward can show the real raw photosite values. To see them, set the Navigator to use the [0-255] range, apply the [[Neutral]] [[Sidecar_Files_-_Processing_Profiles|processing profile]], then set the [[Demosaicing]] method to "None". The Navigator will show the real raw photosite values after black level subtraction within the range of the original raw data.<br />
<br />
=== History ===<br />
<br />
The History panel contains a stack of entries which reflect each of your image editing actions. By clicking on the entries you can step back and forth through the different stages of your work.<br />
<br />
An entry is added each time you adjust a ''different'' widget - multiple edits to the same widget are stored as one entry. For example, adjusting the exposure compensation slider from "0" to "0.3" and then to "0.6" will result in one entry being stored with a final value of "0.6". Likewise, when adjusting a curve, all individual control point adjustments are grouped into one history entry. Should you wish to store the adjustments as two (or more) history entries, you will have to split them by adjusting some other widget. For example, assuming a curve is in "Film-like" mode and you want to keep to that way: adjust several control points on the curve, then toggle the curve mode from "Film-like" to "Standard" and then back to "Film-like" to create a new history entry, and then continue adjusting the curve.<br />
<br />
The history stack is not saved - it is lost as soon as you close the Editor tab. None of your adjustments are lost though, as the final state of all tools is saved in the [[Sidecar Files - Processing Profiles|sidecar file]], ready to be used the next time you open that image.<br />
<br />
=== Snapshots ===<br />
<br />
Under the ''History'' panel is a panel called ''Snapshots''. Its use is in that you can save a snapshot of the photo with all the adjustments up to that point in time, and then proceed to further modify your photo to give it a different appearance, saving new snapshots at every moment you feel you might have reached a version of your photo worth saving. Once you have two or more snapshots, you can just click on them to flip through the different versions and stick with whichever one you like best. In the future, the snapshots will be saved to the PP3 sidecar file. For now, the history and snapshots are lost when you load a new photo in the ''Image Editor'' or close RawTherapee.<br />
<br />
== The Right Panel ==<br />
<br />
To the right is a panel which optionally shows the main histogram and ''Processing Profiles'' selector ("''Preferences > General > Layout > Histogram in left panel''"), and always shows the [[Toolbox]].<br />
You can hide this panel using the [[Image:panel-to-right.png|Hide right panel icon]] hide icon, or its [[Keyboard Shortcuts|keyboard shortcut]].<br />
<br />
=== Processing Profile Selector ===<br />
<br />
The Processing Profiles panel allows you to apply, save, load, copy and paste processing profiles, partially or in full.<br />
<br />
[[File:Processing-profiles-selector.png|center|frame]]<br />
<br />
Read the [[Sidecar_Files_-_Processing_Profiles | Sidecar Files / Processing Profiles]] page for more information.<br />
<br />
=== Toolbox ===<br />
<br />
The ''Toolbox'', in the right panel, contains all the tools you use to tweak your photos. Each tool has its own RawPedia article.<br />
<br />
== Editor Tab Modes ==<br />
<br />
RawTherapee allows you to work on photos in two modes:<br />
* ''Single Editor Tab Mode'' (SETM), where you work only on one photo at a time, and each photo is opened in the same ''Editor'' tab. There is a horizontal panel called the ''[[The_Image_Editor_Tab#The_Filmstrip | Filmstrip]]'' at the top of the ''[[The_Image_Editor_Tab#The_Filmstrip | Editor]]'' tab showing the rest of the photos in that folder for easy access. There are ''Previous Image'' and ''Next Image'' [[File:Nav-prev.png]] [[File:Nav-next.png]] buttons in the bottom toolbar (and [[Keyboard Shortcuts | keyboard shortcuts]] for them) to switch to the previous/next image.<br />
* ''Multiple Editor Tabs Mode'' (METM), where each photo is opened in its own ''[[The_Image_Editor_Tab#The_Filmstrip | Editor]]'' tab. The ''[[The_Image_Editor_Tab#The_Filmstrip | Filmstrip]]'' is hidden in this mode and there are no previous/next buttons. Having multiple photos opened at the same time requires more RAM.<br />
<br />
Try both modes and see which one suits you best. To do that, click on the ''Preferences'' icon [[image:preferences.png|Preferences icon]] in the bottom-left or top-right corner of the RT window, choose "''General > Layout''" and set ''Editor Layout'' to your preferred choice.<br />
<br />
Use this ''Preferences'' window to select a different language for the user interface, to choose a different color theme, change the font size, etc.<br />
<br />
It is also possible to start RawTherapee in no-File-Browser-mode (without the ''File Browser'' tab) by specifying RawTherapee to open an image from your operating system's file browser (in other words, right-click on a photo and select "''Open With > RawTherapee''"), or by using the image filename as an argument when starting RawTherapee from the command line (<code>rawtherapee /path/to/some/photo.raw</code>). This mode was introduced for people with little RAM as not having a ''File Browser'' tab means RawTherapee uses a little less memory, however in practice the amount of memory saved is little and the usability cost outweighs the little benefit, so it is likely to be removed in the future (see [https://code.google.com/p/rawtherapee/issues/detail?id=2254 issue 2254]).<br />
<br />
== The Filmstrip ==<br />
<br />
[[File:Rt filmstrip 21 toolbar-visible.jpg|none|frame|class=heroed|RawTherapee-4.2 showing the Filmstrip with the toolbar visible, which takes up more screen space but lets you easily label, rate and filter the visible thumbnails.]]<br />
[[File:Rt filmstrip 21 toolbar-hidden.jpg|none|frame|class=heroed|RawTherapee-4.2 showing the Filmstrip with the toolbar hidden, which makes it less high and provides more screen space for the main preview (partially visible at the bottom).]]<br />
<br />
If you use ''Single Editor Tab Mode'' ("''Preferences > General > Layout''") you can display a horizontal panel above the preview, this is called the ''Filmstrip''. It contains thumbnails of all images in the currently opened album, and is synchronized with the currently opened image so that you can use [[Keyboard Shortcuts|keyboard shortcuts]] or the previous [[Image:nav-prev.png|Open previous image icon]] and next [[Image:nav-next.png|Open next image icon]] image buttons to open the previous/next image without needing to go back to the ''[[The File Browser Tab|File Browser]]'' tab.<br />
<br />
As of RawTherapee version 4.2.10, you can hide the Filmstrip's toolbar to save screen space. There are two ways of doing this: one way just toggles the toolbar on/off without resizing the filmstrip to the new height, and the other way does the same but also automatically resizes the filmstrip's height. Both are invoked via [[Keyboard Shortcuts|keyboard shortcuts]] only. As resizing the filmstrip's height will trigger a refresh of the image preview and this might take a while if using CPU-hungry tools like noise reduction while zoomed in at 100%, the mode that doesn't resize has been implemented for users with slow machines. Users with fast machines will find the auto-resizing mode more helpful.<br />
<br />
== Monitor Profile and Soft-Proofing ==<br />
<br />
The widgets under the main preview in RawTherapee 5 allow you to apply a monitor color profile to the preview image. This enables users who have calibrated and profiled their monitors to get an instant and accurate preview of their work, whether you're staying in sRGB or working in a wide gamut. Note: OS X users are limited to sRGB and will not get an accurate preview otherwise ([https://discuss.pixls.us/t/wide-gamut-preview-in-os-x/2481 see discussion]), while users of Linux and Windows will get a correct wide-gamut preview.<br />
<br />
Go to Preferences > [[Preferences#Color_Management_Tab|Color Management]] and point the "Directory containing color profiles" to the folder into which you saved your monitor and printer ICC profile. Restart RawTherapee for the changes to take effect. Now you will be able to select your monitor's color profile in the combo-box under the preview. Use the "Relative Colorimetric" rendering intent unless you have a good reason otherwise.<br />
<br />
One can also enable soft-proofing of the preview. This will show you what your image will look like once it gets transformed by the printer profile set in Preferences > [[Preferences#Color_Management_Tab|Color Management]]. If you want to adjust an image for printing and you have an ICC profile for your printer-paper combination you could set that as your output profile, enable "Black point compensation" in Preferences so that the blackest black in your image will match the blackest black your printer-paper combination is capable of reproducing, then enable soft-proofing. You will see what your image will look like if you print it. This allows you to make adjustments and get an instant preview of the result, saving you time and ink on test prints.<br />
<br />
The icon with exclamation mark next to the soft-proofing button will gray out areas that cannot be reproduced by your printer, i.e. areas where you will loose details.<br />
<br />
You should have a calibrated and profiled monitor in order for the soft-proofing preview to be accurate.<br />
<br />
The items you see in the monitor profile combo-box (under the main preview) and in the printer profile combobox (in Preferences > [[Preferences#Color_Management_Tab|Color Management]]) are ICC files located in a folder which you can point RawTherapee to by going to "[[Preferences]] > [[Preferences#Color_Management_Tab|Color Management]] > Directory containing color profiles".</div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=Editor&diff=9838Editor2022-11-22T19:39:44Z<p>DrSlony: </p>
<hr />
<div><div class="pagetitle">The Editor</div><br />
<br />
[[File:Rt 55 trains.png|none|frame|link=|class=heroed|The Image Editor tab in RawTherapee 5.5.]]<br />
<br />
== Introduction ==<br />
<br />
The Image Editor tab is where you tweak your photos. By default RawTherapee is in "Single Editor Tab Mode, Vertical Tabs" (SETM/VT) which is more memory-efficient and lets you use the [[Editor#The_Filmstrip|Filmstrip]] (described below). You can switch to "Multiple Editor Tabs Mode" (METM) by going to "[[Preferences#Layout|Preferences > General > Layout]]", however each Editor tab will require a specific amount of RAM relative to the image size and the tools you use, and also the Filmstrip is hidden in this mode, so we recommend you first give SETM a try.<br />
<br />
== The Preview Panel ==<br />
<br />
The central panel shows a preview of the image being edited. This preview is generated from raw data if such is available. It reflects the adjustments made by the tools in the [[Editor#Toolbox|Toolbox]]. Note that the effects of some tools are only accurately visible when you are zoomed in to 1:1 (100%) or more; these tools are marked in the interface with a "1:1" icon [[File:One-to-one-small.png|Zoom 1:1]] alongside the tool's name.<br />
<br />
When opening an image, RawTherapee loads the tool settings from the sidecar file if one exists, else it applies a default sidecar file as specified in "[[Preferences#Default_Processing_Profile|Preferences > Image Processing > Default Processing Profile]]". When you close the image (which happens automatically if you open a different image or if you close RawTherapee) the current tool settings are automatically saved to a sidecar file as specified in "[[Preferences#Processing_Profile_Handling|Preferences > Image Processing > Processing Profile Handling]]".<br />
<br />
=== Eek! My Raw Photo Looks Different than the Camera JPEG ===<br />
<br />
When opening a raw photo you may notice that it looks different from your camera's JPEG, or from what other software show when viewing the same raw photo. In some cases this difference is minute, but in other cases it could be significant - the image could be darker, lack contrast, be less sharp and more noisy. What gives?<br />
<br />
There are three things you must know first to understand what is happening here:<br />
# Your camera does not show you the real raw data when you shoot raw photos. It processes the raw image in many ways before presenting you with the histogram and the preview on your camera's display. Even if you set all the processing features which your camera's firmware allows you to tweak to their neutral, "0" positions, what you see is still not an unprocessed image. Exactly what gets applied depends on the choices made by your camera's engineers and company management, but usually this includes a custom tone curve, saturation boost, sharpening and noise reduction. Some cameras, particularly low-end ones and [http://en.wikipedia.org/wiki/Micro_Four_Thirds_system Micro Four-Thirds system], may also apply lens distortion correction to not only fix [http://en.wikipedia.org/wiki/Distortion_(optics)#Radial_distortion barrel and pincushion distortion] but also to hide dark corners caused by severe [http://en.wikipedia.org/wiki/Vignetting vignetting] or by the [https://en.wikipedia.org/wiki/Lens_hood lens hood]. Most cameras also underexpose every photo you take by anywhere from -0.3EV to -1.3EV or more, in order to gain headroom in the highlights. When your camera (or other raw editing software) processes the raw file it compensates for this by increasing exposure compensation by the same amount.<br />
# When shooting a raw photo, most cameras embed within the raw file a full-resolution JPEG image with tone curves and other adjustments applied. Some raw files contain as many as three JPEG images differing only in resolution. Most cameras offer storing photos in one of three modes: "RAW", "JPEG", or "RAW+JPEG". The embedded JPEG image discussed here is stored within the raw file even in just "RAW" mode! When you open raw files in other software, what you are usually seeing is '''not''' the raw data, but the embedded, processed JPEG image! Examples of software which are either incapable of or which in their default settings do not show you the real raw data: [http://en.wikipedia.org/wiki/IrfanView IrfanView], [http://en.wikipedia.org/wiki/XnView XnView], [http://en.wikipedia.org/wiki/Gwenview Gwenview], [http://en.wikipedia.org/wiki/Geeqie Geeqie], [http://en.wikipedia.org/wiki/Eye_of_GNOME Eye of GNOME], [http://en.wikipedia.org/wiki/F-Spot F-Spot], [http://en.wikipedia.org/wiki/Shotwell_(software) Shotwell], [http://en.wikipedia.org/wiki/GThumb gThumb], etc. It is worth mentioning at this point that if you shoot in "RAW+JPEG" mode then you could in fact be wasting space on your memory card and gaining nothing for it, as your raw files most likely already contain an embedded JPEG identical to the external one saved in "RAW+JPEG" mode.<br />
# Most raw development programs (programs which do read the real raw data instead of just reading the embedded JPEG) apply some processing to it, such as a base tone curve, even at their most neutral settings, thereby making it impossible for users to see the real, untouched contents of their raw photos. Adobe Lightroom is an example. Comparing RawTherapee's real [[Neutral]] image to a pseudo-neutral one from these other programs will expose the differences.<br />
<br />
RawTherapee, on the other hand, is capable of showing you the real raw image in the main preview, leaving the way you want this data processed up to you. When you use the "[[Neutral]]" processing profile you will see the demosaiced image with camera white balance in your working color space with no other modifications. You can even see the non-demosaiced image by setting the [[Demosaicing#Method|demosaicing method]] to "None".<br />
<br />
To provide you with a more aesthetically pleasing starting point, RawTherapee by default uses the [[Auto-Matched_Curve]] processing profile, which automatically generates a tone curve to make the tones of the raw image match those of the embedded JPEG, if one exists. If one does not exist, you can use the [[Standard_Film_Curve]] processing profile, which applies a curve which looks good in most cases. Choose the sub-type (ISO Low/Medium/High) depending on how noisy your image is.<br />
<br />
=== Scrollable Toolbars ===<br />
<br />
The toolbars above and below the main preview hold a certain number of buttons and other widgets which might not fit on lower resolution screens. {{:Scrollable Toolbar}}<br />
<br />
=== Preview Background Color ===<br />
<br />
[[File:Rt59 preview background all.png|none]]<br />
<br />
The background color of the preview panel may be changed to allow you to better judge how the image tones will appear when the saved image is viewed on a website (or image viewer, or print) of a similar background color.<br />
<br />
This choice also applies to the cropped-off area, if the image is cropped. See "[[Preferences#Appearance|Preferences > General > Appearance > Crop mask color]]".<br />
<br />
Available options:<br />
* theme-based (see [[Preferences#Appearance|Preferences > General > Appearance]]),<br />
* black,<br />
* [https://en.wikipedia.org/wiki/Middle_gray L* middle grey],<br />
* white.<br />
<br />
=== Preview Channel ===<br />
<br />
[[File:Rt59_preview_channel_all.png|none]]<br />
<br />
The preview can be toggled to show one of the following channels:<br />
* red,<br />
* green,<br />
* blue,<br />
* luminosity, which is calculated as 0.299*R + 0.587*G + 0.114*B.<br />
<br />
Preview of individual channels may be helpful when editing RGB curves, planning black/white conversion using the channel mixer, evaluating image noise, etc. Luminosity preview is helpful to instantly view the image in black and white without altering development parameters, to see which channel might be clipping or for aesthetic reasons.<br />
<br />
=== Preview Mask ===<br />
<br />
[[File:Rt59_preview_mask_all.png|none]]<br />
<br />
Available options:<br />
* Focus mask, which shows which areas are in focus (based on how sharp they appear),<br />
* Sharpening contrast mask, which visualizes the mask which decides which areas are affected by sharpening. See [[Sharpening#Contrast_Mask|Sharpening > Contrast Mask]].<br />
* Clipped shadow indication.<br />
* Clipped highlight indication.<br />
<br />
{{:Clipping_Indication}}<br />
<br />
[[Image:Preview_6_focus_2.jpg|Focus mask indicating the focusing plane|thumb]]<br />
<br />
The focus mask is designed to highlight areas of the image which are in focus. Naturally, focused areas are sharper, so the sharp areas are highlighted. The focus mask is more accurate on images with a shallow depth of field, low noise and at higher zoom levels. To improve detection accuracy for noisy images, evaluate at smaller zoom, around the 10-30% range. The current implementation analyzes the preview image, which is rescaled from the original captured size down to what you see on screen. When zoomed less than 100%, the preview image is downscaled, a side-effect of which is the apparent reduction of noise. You can take advantage of this to help identify truly sharp details, rather than noise itself which may introduce a false micro texture. At the same time, downscaling compresses larger scale details into a smaller size, and it may introduce aliasing artifacts, both of which could lead to false positives. You can increase your confidence by viewing the mask at various zoom levels. It is not always fault proof, but can be helpful in many cases. Due to these caveats, be sure to double-check your images if you decide to delete them based on the focus mask.<br />
<br />
=== Detail Window ===<br />
<br />
The "New detail window" button [[File:Window-add.png]], situated below the main preview next to the zoom buttons, opens a new viewport over the main preview of an adjustable size and of adjustable zoom. This lets you work on the photo zoomed-to-fit while examining several areas of interest at a 100% zoom (or even more). The benefit of using this feature is particularly important to users with slower machines, though not only them, as the zoomed-out main preview takes a shorter amount of time to update than if you were to zoom it to 100% because working at a zoom level less than 100% excludes certain slow tools, such as Noise Reduction, while the little detail windows zoomed to 100% do include all tools and are fast to update because of their small size. This allows you can use the main preview for your general exposure tweaks where it is necessary to see the whole image, and one or more detail windows to get sharpening and/or noise reduction just right.<br />
<br />
=== Preview Refresh Delay ===<br />
<br />
Changing any tool's parameters sends a signal for the preview image to be updated accordingly. Imagine what would happen if there was no "delay period", and you dragged, for example, the exposure compensation slider from 0.00 to +0.60. A signal would be sent to update the preview for every single change of that value - for +0.01, +0.02, ... +0.59, +0.60. Updating the preview 60 times would be completely unnecessary and actually take longer than it takes you to move the slider. This is especially true for more complicated tools, such as noise reduction, where a preview update can take even a second (depending on your CPU and preview size). The solution is for RawTherapee to wait for a very short period from the moment you stop moving a slider (you don't have to let go of it, pausing movement is enough) until the moment it sends a signal for the preview to be refreshed.<br />
<br />
We have introduced two parameters which control the length of this waiting period:<br />
; AdjusterMinDelay<br />
: Default value = 100ms.<br />
: This is used for tools with a very fast response time, for example the exposure compensation slider.<br />
; AdjusterMaxDelay<br />
: Default value = 200ms.<br />
: This is used for tools with a slow response time, for example the CIECAM02 sliders.<br />
<br />
You can adjust both of these values in the options file in the [[File_Paths|config folder]].<br />
<br />
== The Left Panel ==<br />
<br />
To the left is a panel which optionally shows the main histogram ("''Preferences > General > Layout > Histogram in left panel''"), and always shows the ''Navigator'', ''History'' and ''Snapshots''.<br />
You can hide this panel using the [[Image:panel-to-left.png|Hide left panel icon]] hide icon, or its [[Keyboard Shortcuts|keyboard shortcut]].<br />
<br />
=== Main Histogram ===<br />
<br />
[[File:Rt57 histogram wide labeled.png|none|frame|class=heroed|Histogram showing all 3 channels and luminosity.]]<br />
<br />
[[File:RT57 histogram ani.gif|frame|The histogram in RawTherapee 5.7, showing a histogram of the raw data in all three modes - linear-linear, linear-log and log-log. We can see that the raw file is not clipped.]]<br />
<br />
[[File:Rt histogram rgbindicator.png|frame|The RGB indicator shows the position in the histogram of the R, G, B and L values of the pixel your cursor is hovering over.]]<br />
<br />
A histogram in photography is a graphical representation of the number of pixels of a given value. Typically the horizontal axis represents the range of possible values while the vertical axis represents the count of pixels with that value. The axes need not be linear - RawTherapee can also scale the histogram logarithmically.<br />
<br />
Regardless of the photo's bit depth, the histogram itself has a precision of 256 sampling bins. To understand this, let us look at the example of a 16-bit image using integer precision. Its range of possible values spans from 0 to 65535 (2^16 = 65536 possible values, and since 0 is a possible minimum value then the maximum value is 65535). Drawing a histogram using 16-bit precision would mean that it would need to be 65535 pixels wide to faithfully represent the data, and no screen today is anywhere near that wide. Instead, all pixels with values from 0 to 255 (65535/256*1) are grouped into the first "bin". The second bin consists of a count of all pixels with values from 256 to 511 (65535/256*2). The third bin represents values 512 to 767 (65535/256*3). And so on until bin 256. This happens regardless of the input image's bit depth - and RawTherapee's engine uses 32-bit floating-point precision anyway.<br />
<br />
The main histogram can simultaneously show one or more of the following:<br />
* [[File:Histogram-red-on-small.svg]] the red channel,<br />
* [[File:Histogram-green-on-small.svg]] the green channel,<br />
* [[File:Histogram-blue-on-small.svg]] the blue channel,<br />
* [[File:Histogram-silver-on-small.svg]] CIELab luminance,<br />
* [[File:Histogram-gold-on-small.svg]] [http://en.wikipedia.org/wiki/Chromaticity chromaticity].<br />
* [[File:Histogram-bayer-on-small.svg]] red, green and blue channels of the source raw image before demosaicing.<br />
<br />
The histogram shows the channels listed above using the gamma-corrected output profile when the gamut button [[File:Gamut-hist.png]] is disabled (default), or using the working profile when the button is enabled. The status of this button also affects the values shown in the Navigator panel, as well as the clipped shadow [[File:Warning-shadows.png]] and [[File:Warning-highlights.png]] highlight indicators. It does not affect the raw histogram.<br />
<br />
Like water in a pipeline, image data flows through RawTherapee from the input file through various stages, most of which the user can control, to the output. The output could be the image saved in a file, or the image displayed on your screen. Each stage affects the color data. The histogram allows you to visualize this data at several stages. By default, the histogram shows color data as it will appear if you save the output image, including processing done at all intermediate stages. By enabling the gamut button [[File:Gamut-hist.png]] you can peak at the data at the early stage where it gets converted into the working space. You can even look at the raw data before any transformations or demosaicing are applied.<br />
<br />
Let's examine the large histogram example above. Though it actually shows four histograms (red, green, blue and luminance), focus on one histogram at a time. The horizontal axis represents the possible values of the histogram, where "A" are the darkest values possible, "C" the mid-tones, and "E" the brightest possible values. The position of the histogram line on the vertical axis represents how many pixels have that value. We can see that there are zero pixels in the red channel with values around "A" (from zero to very dark), because the histogram line lies right along the bottom. There is a significant number of pixels where the red channel is dark (between A and B), and a significant number where it is light (around D). Then, importantly, there is a spike at the right end of the histogram, at E - it tells us that a large number of pixels have maximal red values - they are clipped.<br />
<br />
Generally speaking, you should care when clipping occurs on skin, and not care when it's due to [https://en.wikipedia.org/wiki/Specular_highlight specular highlights]. If a histogram shows clipping, and if you care about the clipped regions, you should start by establishing where the clipping occurs. Check the raw histogram - are any channels clipped? If yes, then maybe [[Exposure#Highlight_Reconstruction|highlight reconstruction]] can help. If the raw histograms are not clipped, then all the required information is intact, and it is some stage downstream in the pipeline which causes clipping. Ensure your working profile's gamut is large enough by enabling the gamut button [[File:Gamut-hist.png]] to see histograms at the working profile stage of the pipeline. You might want to temporarily apply the [[Neutral]] profile to disable all the tools while checking, then revert. If your working space is not causing clipping (the default working space is ProPhoto and it's huge), then it's likely your adjustments which are causing clipping. Reduce exposure, go easy on the curves, use dynamic range compression if necessary.<br />
<br />
Knowing how to read a histogram is a basic and very useful skill, as it can point out issues with your image regardless of how dim or miscalibrated your monitor may be.<br />
<br />
To help you visualize the data, the histogram (as of RawTherapee 5.5) has three modes which scale the data in the x and y axes differently:<br />
* [[File:Histogram-mode-linear-small.png]] Linear-linear mode. You find gridlines at halves, quarters, eighths and sixteenths, depending on the size of the histogram.<br />
* [[File:Histogram-mode-logx-small.png]] Linear-log mode. The x-axis is linear, the y-axis and the horizontal gridlines are scaled logarithmically. The position of the gridlines still corresponds to the halves, quarters, etc.<br />
* [[File:Histogram-mode-logxy-small.png]] Log-log mode. Both the x- and y-axes are scaled logarithmically. The gridlines are not scaled logarithmically, but correspond to [https://en.wikipedia.org/wiki/Exposure_value stops] - with every gridline the value doubles, so there are lines for the values 1, 3, 7, 15, 31, 63, and 127 (<code>pow(2.0,i) - 1)</code>).<br />
<br />
When there is a disproportionately bright area relative to the rest of the image, it will show up as a spike in the histogram. If you want to show this on a histogram with a linear y axis, the spike may push the lesser values down the y-axis, making them difficult to see. Switch to one of the log modes to scale the data and help you get a better overview of all values.<br />
<br />
The histogram can be moved to the left/right panel from "''Preferences > General > Layout > Histogram in left panel''".<br />
<br />
==== Raw Histograms ====<br />
<br />
Raw files contain a dump of data captured by the sensor and quantified by the analog-to-digital converter. The raw file as a container has a bit depth of its own, typically 16-bit, while the data it contains could have a lower bit depth - typically it is 12-bit (0-4096) or 14-bit (0-16384). To display the data from a raw file as an image, one of the several key bits of information required to process the data correctly are the black and white levels. The black level is not necessarily 0, as the sensor and camera electronics produce digital noise, so the noise floor may lie for instance at 512. The white level is also not necessarily 16384; it depends on various things, and may lie for instance at 16300. For more information, see the articles [[Demosaicing]] and [[Adding Support for New Raw Formats]] (especially the header of the <code>camconst.json</code> file). The black and white level values used by RawTherapee are hierarchically set by looking in several places: in <code>dcraw.c</code>, inside the raw file's metadata, and in <code>camconst.json</code> (latter takes precedence). Furthermore, the user can tweak the raw [[Raw Black Points|black]] and [[Raw White Points|white]] levels from within RawTherapee.<br />
<br />
The raw histograms show data after black level subtraction. The right end of the histogram is anchored on the white level. The raw histograms are affected by the detected black and white levels as well as by the black and white level adjustments made by the user in RawTherapee.<br />
<br />
When examining the raw histogram, you may also want to set the demosaicing method to "none". This will reveal the sensor pattern in the preview, and also cause the [[Editor#Navigator|Navigator]] panel to show the raw RGB values of the pixel currently being hovered over. These values are affected by the detected black and white levels as well as by the black level adjustments made by the user in RawTherapee, but they are not affected by the white level adjustments ("white-point correction") made by the user in RawTherapee.<br />
<br />
=== Navigator ===<br />
<br />
The ''Navigator'' panel shows a thumbnail of the currently opened image, and RGB, HSV and Lab values of the pixel your cursor is currently hovering over.<br />
<br />
The values shown in the main histogram and Navigator panel are either those of the working profile or of the gamma-corrected output profile, depending on the state of the gamut button [[File:Gamut-hist.png]] located in the toolbar above the main preview. When the gamut button is enabled the working profile is used, otherwise the gamma-corrected output profile is used.<br />
<br />
By clicking on the values in the Navigator you can cycle between these three formats:<br />
* [0-255]<br />
* [0-1]<br />
* [%]<br />
<br />
RawTherapee 5.1 onward can show the real raw photosite values. To see them, set the Navigator to use the [0-255] range, apply the [[Neutral]] [[Sidecar_Files_-_Processing_Profiles|processing profile]], then set the [[Demosaicing]] method to "None". The Navigator will show the real raw photosite values after black level subtraction within the range of the original raw data.<br />
<br />
=== History ===<br />
<br />
The History panel contains a stack of entries which reflect each of your image editing actions. By clicking on the entries you can step back and forth through the different stages of your work.<br />
<br />
An entry is added each time you adjust a ''different'' widget - multiple edits to the same widget are stored as one entry. For example, adjusting the exposure compensation slider from "0" to "0.3" and then to "0.6" will result in one entry being stored with a final value of "0.6". Likewise, when adjusting a curve, all individual control point adjustments are grouped into one history entry. Should you wish to store the adjustments as two (or more) history entries, you will have to split them by adjusting some other widget. For example, assuming a curve is in "Film-like" mode and you want to keep to that way: adjust several control points on the curve, then toggle the curve mode from "Film-like" to "Standard" and then back to "Film-like" to create a new history entry, and then continue adjusting the curve.<br />
<br />
The history stack is not saved - it is lost as soon as you close the Editor tab. None of your adjustments are lost though, as the final state of all tools is saved in the [[Sidecar Files - Processing Profiles|sidecar file]], ready to be used the next time you open that image.<br />
<br />
=== Snapshots ===<br />
<br />
Under the ''History'' panel is a panel called ''Snapshots''. Its use is in that you can save a snapshot of the photo with all the adjustments up to that point in time, and then proceed to further modify your photo to give it a different appearance, saving new snapshots at every moment you feel you might have reached a version of your photo worth saving. Once you have two or more snapshots, you can just click on them to flip through the different versions and stick with whichever one you like best. In the future, the snapshots will be saved to the PP3 sidecar file. For now, the history and snapshots are lost when you load a new photo in the ''Image Editor'' or close RawTherapee.<br />
<br />
== The Right Panel ==<br />
<br />
To the right is a panel which optionally shows the main histogram and ''Processing Profiles'' selector ("''Preferences > General > Layout > Histogram in left panel''"), and always shows the [[Toolbox]].<br />
You can hide this panel using the [[Image:panel-to-right.png|Hide right panel icon]] hide icon, or its [[Keyboard Shortcuts|keyboard shortcut]].<br />
<br />
=== Processing Profile Selector ===<br />
<br />
The Processing Profiles panel allows you to apply, save, load, copy and paste processing profiles, partially or in full.<br />
<br />
[[File:Processing-profiles-selector.png|center|frame]]<br />
<br />
Read the [[Sidecar_Files_-_Processing_Profiles | Sidecar Files / Processing Profiles]] page for more information.<br />
<br />
=== Toolbox ===<br />
<br />
The ''Toolbox'', in the right panel, contains all the tools you use to tweak your photos. Each tool has its own RawPedia article.<br />
<br />
== Editor Tab Modes ==<br />
<br />
RawTherapee allows you to work on photos in two modes:<br />
* ''Single Editor Tab Mode'' (SETM), where you work only on one photo at a time, and each photo is opened in the same ''Editor'' tab. There is a horizontal panel called the ''[[The_Image_Editor_Tab#The_Filmstrip | Filmstrip]]'' at the top of the ''[[The_Image_Editor_Tab#The_Filmstrip | Editor]]'' tab showing the rest of the photos in that folder for easy access. There are ''Previous Image'' and ''Next Image'' [[File:Nav-prev.png]] [[File:Nav-next.png]] buttons in the bottom toolbar (and [[Keyboard Shortcuts | keyboard shortcuts]] for them) to switch to the previous/next image.<br />
* ''Multiple Editor Tabs Mode'' (METM), where each photo is opened in its own ''[[The_Image_Editor_Tab#The_Filmstrip | Editor]]'' tab. The ''[[The_Image_Editor_Tab#The_Filmstrip | Filmstrip]]'' is hidden in this mode and there are no previous/next buttons. Having multiple photos opened at the same time requires more RAM.<br />
<br />
Try both modes and see which one suits you best. To do that, click on the ''Preferences'' icon [[image:preferences.png|Preferences icon]] in the bottom-left or top-right corner of the RT window, choose "''General > Layout''" and set ''Editor Layout'' to your preferred choice.<br />
<br />
Use this ''Preferences'' window to select a different language for the user interface, to choose a different color theme, change the font size, etc.<br />
<br />
It is also possible to start RawTherapee in no-File-Browser-mode (without the ''File Browser'' tab) by specifying RawTherapee to open an image from your operating system's file browser (in other words, right-click on a photo and select "''Open With > RawTherapee''"), or by using the image filename as an argument when starting RawTherapee from the command line (<code>rawtherapee /path/to/some/photo.raw</code>). This mode was introduced for people with little RAM as not having a ''File Browser'' tab means RawTherapee uses a little less memory, however in practice the amount of memory saved is little and the usability cost outweighs the little benefit, so it is likely to be removed in the future (see [https://code.google.com/p/rawtherapee/issues/detail?id=2254 issue 2254]).<br />
<br />
== The Filmstrip ==<br />
<br />
[[File:Rt filmstrip 21 toolbar-visible.jpg|none|frame|class=heroed|RawTherapee-4.2 showing the Filmstrip with the toolbar visible, which takes up more screen space but lets you easily label, rate and filter the visible thumbnails.]]<br />
[[File:Rt filmstrip 21 toolbar-hidden.jpg|none|frame|class=heroed|RawTherapee-4.2 showing the Filmstrip with the toolbar hidden, which makes it less high and provides more screen space for the main preview (partially visible at the bottom).]]<br />
<br />
If you use ''Single Editor Tab Mode'' ("''Preferences > General > Layout''") you can display a horizontal panel above the preview, this is called the ''Filmstrip''. It contains thumbnails of all images in the currently opened album, and is synchronized with the currently opened image so that you can use [[Keyboard Shortcuts|keyboard shortcuts]] or the previous [[Image:nav-prev.png|Open previous image icon]] and next [[Image:nav-next.png|Open next image icon]] image buttons to open the previous/next image without needing to go back to the ''[[The File Browser Tab|File Browser]]'' tab.<br />
<br />
As of RawTherapee version 4.2.10, you can hide the Filmstrip's toolbar to save screen space. There are two ways of doing this: one way just toggles the toolbar on/off without resizing the filmstrip to the new height, and the other way does the same but also automatically resizes the filmstrip's height. Both are invoked via [[Keyboard Shortcuts|keyboard shortcuts]] only. As resizing the filmstrip's height will trigger a refresh of the image preview and this might take a while if using CPU-hungry tools like noise reduction while zoomed in at 100%, the mode that doesn't resize has been implemented for users with slow machines. Users with fast machines will find the auto-resizing mode more helpful.<br />
<br />
== Monitor Profile and Soft-Proofing ==<br />
<br />
The widgets under the main preview in RawTherapee 5 allow you to apply a monitor color profile to the preview image. This enables users who have calibrated and profiled their monitors to get an instant and accurate preview of their work, whether you're staying in sRGB or working in a wide gamut. Note: OS X users are limited to sRGB and will not get an accurate preview otherwise ([https://discuss.pixls.us/t/wide-gamut-preview-in-os-x/2481 see discussion]), while users of Linux and Windows will get a correct wide-gamut preview.<br />
<br />
Go to Preferences > [[Preferences#Color_Management_Tab|Color Management]] and point the "Directory containing color profiles" to the folder into which you saved your monitor and printer ICC profile. Restart RawTherapee for the changes to take effect. Now you will be able to select your monitor's color profile in the combo-box under the preview. Use the "Relative Colorimetric" rendering intent unless you have a good reason otherwise.<br />
<br />
One can also enable soft-proofing of the preview. This will show you what your image will look like once it gets transformed by the printer profile set in Preferences > [[Preferences#Color_Management_Tab|Color Management]]. If you want to adjust an image for printing and you have an ICC profile for your printer-paper combination you could set that as your output profile, enable "Black point compensation" in Preferences so that the blackest black in your image will match the blackest black your printer-paper combination is capable of reproducing, then enable soft-proofing. You will see what your image will look like if you print it. This allows you to make adjustments and get an instant preview of the result, saving you time and ink on test prints.<br />
<br />
The icon with exclamation mark next to the soft-proofing button will gray out areas that cannot be reproduced by your printer, i.e. areas where you will loose details.<br />
<br />
You should have a calibrated and profiled monitor in order for the soft-proofing preview to be accurate.<br />
<br />
The items you see in the monitor profile combo-box (under the main preview) and in the printer profile combobox (in Preferences > [[Preferences#Color_Management_Tab|Color Management]]) are ICC files located in a folder which you can point RawTherapee to by going to "[[Preferences]] > [[Preferences#Color_Management_Tab|Color Management]] > Directory containing color profiles".</div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=Sharpening&diff=9837Sharpening2022-11-22T19:25:49Z<p>DrSlony: </p>
<hr />
<div><div class="pagetitle">Sharpening</div><br />
<br />
{{1:1}}<br />
<br />
{{Sharpening_gallery}}<br />
<br />
This article describes the tool called "Sharpening", however RawTherapee contains other tools which can be used to perform various types of sharpening - see [[Edges and Microcontrast]] and the [[Wavelets]] tools.<br />
<br />
The Sharpening tool is applied to the full image, '''before''' the [[Resize]] tool. If you would like to apply sharpening '''after''' resizing, use the [[Resize#Post-Resize Sharpening|Post-Resize Sharpening]] tool which you will find inside the Resize tool.<br />
<br />
== Contrast Mask ==<br />
<br />
The "contrast threshold" and "blur radius" sliders allow you to control a mask that decides which areas are affected by sharpening and which are left untouched. Activate the "preview the sharpening contrast mask" button [[File:Contrastmask-off.png]] (in the toolbar above the main preview) to see this mask.<br />
<br />
== Methods ==<br />
<br />
=== Unsharp Mask ===<br />
<br />
[https://en.wikipedia.org/wiki/Unsharp_mask Unsharp masking] (USM) is a technique used to increase the apparent [https://en.wikipedia.org/wiki/Acutance acutance] (edge contrast) of an image, making it appear clearer, even though it technically does not really sharpen the image. It makes use of several phenomena of the human visual system in order to accomplish this effect, such as the [https://en.wikipedia.org/wiki/Cornsweet_illusion Cornsweet illusion] and [https://en.wikipedia.org/wiki/Mach_bands Mach bands]. Though unsharp masking in other software is easily prone to causing [https://en.wikipedia.org/wiki/Haloing halos], RawTherapee has a unique threshold slider which allows you to achieve a superb sharpening effect with a minimal risk of halos.<br />
<br />
==== Radius ====<br />
<br />
The Radius determines the size of the details being amplified and, consequently, relates to the width of the sharpening halo. In general the quality of sharpening is best if the sharpening radius is smaller. For low ISO images that are in focus and without motion blur a value of 0.5-0.7 is satisfactory.<br />
<br />
==== Threshold ====<br />
<br />
[[image:Usm_threshold.png]]<br />
<br />
The ''Threshold'' tool helps to suppress noise amplification and haloing and to confine sharpening to a desired tonal range. The Threshold tool allows one to create a curve via which the sharpening is applied. The vertical axis corresponds to opacity: 0% at the bottom (transparent, sharpening not visible), 100% at the top (opaque, sharpening visible). The horizontal axis corresponds to luminosity: select the tonal range that will get sharpened - the darkest tones are on the left, progressing to white tones on the right. As mentioned in the tooltip, to move each of the points in the threshold tool individually, hold the Shift key before clicking on a point with your mouse. Holding the Ctrl key while moving a point with the mouse allows for very fine movements.<br />
<br />
When moving the right pair of sliders to the left side, sharpening is reduced in the highlights. When moving the left pair of sliders to the right side, sharpening is reduced in the shadows and minimizes amplification of dark noise.<br />
<br />
The default threshold values will protect from over-sharpening and haloing in most cases and limit the sharpening effect to mid-tones. In the example screenshot, the blackest tones have no USM applied, then USM is applied to a broad range of tones from dark to light, and the strength of USM gradually drops off from maximal at the mid-tones to none at the whitest tones, so as to prevent noise amplification and haloing.<br />
<br />
==== Amount ====<br />
<br />
The ''Amount'' parameter controls the strength of the sharpening.<br />
<br />
==== Sharpen Only Edges ====<br />
<br />
If you activate "''Sharpen only edges''" then uniform areas will not be sharpened. This is useful when sharpening noisy photos.<br />
<br />
Two new sliders appear as well:<br />
* Radius, used for noise detection. If the noise is low, a lower radius can be used, and vice-versa. A higher radius slows down the image processing.<br />
* Edge Tolerance, determines how much a pixel has to differ from its neighbor to be considered as an edge and not as noise. It is very similar to the USM ''Threshold'' parameter and has a high impact on the visual quality. For low ISO (low noise) images use 1000 or less, for high ISO images use 2500-3000 or even more.<br />
<br />
==== Halo Control ====<br />
<br />
"Halo Control" is used to avoid halo effects around light objects when sharpening too aggressively. When activated, a new slider appears:<br />
* Amount. At 100 it works at maximum, reducing the visual impact of the USM filter.<br />
<br />
=== RL Deconvolution ===<br />
<br />
[https://en.wikipedia.org/wiki/Richardson%E2%80%93Lucy_deconvolution RL deconvolution] is named after the makers of this algorithm, Richardson and Lucy. It uses the [https://en.wikipedia.org/wiki/Point_spread_function point spread function] (PSF) to deconvolve (reverse) the effects of Gaussian-like blur. In reality, the blur produced by the lens and by motion may differ from Gaussian blur significantly, therefore some artifacts, such as halos, may appear when the radius diverges too far from the type of blur in the actual image, and when then effect is too strong.<br />
<br />
==== Radius ====<br />
<br />
The radius defines the [https://en.wikipedia.org/wiki/Standard_deviation standard deviation] (sigma) of the [https://en.wikipedia.org/wiki/Gaussian_blur Gaussian blur] in the image. Find the right value through trial and error.<br />
<br />
==== Amount ====<br />
<br />
Controls the blend factor between the unsharpened image and the sharpened one.<br />
<br />
==== Damping ====<br />
<br />
Damping reduces the effect of the deconvolution at each iteration. It has the effect of preventing sharpening of the finest details. Use it if the sharpened image has too much "bite" at the finest level.<br />
<br />
==== Iterations ====<br />
<br />
RL Deconvolution is an iterative algorithm; it requires being repeated in order to achieve the intended results. Each repetition of the process is called an "iteration", and the result of one iteration is used as the starting point of the next iteration. While each iteration removes blur, it also increases processing time and the likelihood that halo artifacts will appear, so you need to find the perfect balance through trial and error - the default value should be fine for most cases.</div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=Editor&diff=9836Editor2022-11-22T19:09:25Z<p>DrSlony: /* Background Color of the Preview */</p>
<hr />
<div><div class="pagetitle">The Editor</div><br />
<br />
[[File:Rt 55 trains.png|none|frame|link=|class=heroed|The Image Editor tab in RawTherapee 5.5.]]<br />
<br />
== Introduction ==<br />
<br />
The Image Editor tab is where you tweak your photos. By default RawTherapee is in "Single Editor Tab Mode, Vertical Tabs" (SETM/VT) which is more memory-efficient and lets you use the [[Editor#The_Filmstrip|Filmstrip]] (described below). You can switch to "Multiple Editor Tabs Mode" (METM) by going to "[[Preferences#Layout|Preferences > General > Layout]]", however each Editor tab will require a specific amount of RAM relative to the image size and the tools you use, and also the Filmstrip is hidden in this mode, so we recommend you first give SETM a try.<br />
<br />
== The Preview Panel ==<br />
<br />
The central panel shows a preview of the image being edited. This preview is generated from raw data if such is available. It reflects the adjustments made by the tools in the [[Editor#Toolbox|Toolbox]]. Note that the effects of some tools are only accurately visible when you are zoomed in to 1:1 (100%) or more; these tools are marked in the interface with a "1:1" icon [[File:One-to-one-small.png|Zoom 1:1]] alongside the tool's name.<br />
<br />
When opening an image, RawTherapee loads the tool settings from the sidecar file if one exists, else it applies a default sidecar file as specified in "[[Preferences#Default_Processing_Profile|Preferences > Image Processing > Default Processing Profile]]". When you close the image (which happens automatically if you open a different image or if you close RawTherapee) the current tool settings are automatically saved to a sidecar file as specified in "[[Preferences#Processing_Profile_Handling|Preferences > Image Processing > Processing Profile Handling]]".<br />
<br />
=== Eek! My Raw Photo Looks Different than the Camera JPEG ===<br />
<br />
When opening a raw photo you may notice that it looks different from your camera's JPEG, or from what other software show when viewing the same raw photo. In some cases this difference is minute, but in other cases it could be significant - the image could be darker, lack contrast, be less sharp and more noisy. What gives?<br />
<br />
There are three things you must know first to understand what is happening here:<br />
# Your camera does not show you the real raw data when you shoot raw photos. It processes the raw image in many ways before presenting you with the histogram and the preview on your camera's display. Even if you set all the processing features which your camera's firmware allows you to tweak to their neutral, "0" positions, what you see is still not an unprocessed image. Exactly what gets applied depends on the choices made by your camera's engineers and company management, but usually this includes a custom tone curve, saturation boost, sharpening and noise reduction. Some cameras, particularly low-end ones and [http://en.wikipedia.org/wiki/Micro_Four_Thirds_system Micro Four-Thirds system], may also apply lens distortion correction to not only fix [http://en.wikipedia.org/wiki/Distortion_(optics)#Radial_distortion barrel and pincushion distortion] but also to hide dark corners caused by severe [http://en.wikipedia.org/wiki/Vignetting vignetting] or by the [https://en.wikipedia.org/wiki/Lens_hood lens hood]. Most cameras also underexpose every photo you take by anywhere from -0.3EV to -1.3EV or more, in order to gain headroom in the highlights. When your camera (or other raw editing software) processes the raw file it compensates for this by increasing exposure compensation by the same amount.<br />
# When shooting a raw photo, most cameras embed within the raw file a full-resolution JPEG image with tone curves and other adjustments applied. Some raw files contain as many as three JPEG images differing only in resolution. Most cameras offer storing photos in one of three modes: "RAW", "JPEG", or "RAW+JPEG". The embedded JPEG image discussed here is stored within the raw file even in just "RAW" mode! When you open raw files in other software, what you are usually seeing is '''not''' the raw data, but the embedded, processed JPEG image! Examples of software which are either incapable of or which in their default settings do not show you the real raw data: [http://en.wikipedia.org/wiki/IrfanView IrfanView], [http://en.wikipedia.org/wiki/XnView XnView], [http://en.wikipedia.org/wiki/Gwenview Gwenview], [http://en.wikipedia.org/wiki/Geeqie Geeqie], [http://en.wikipedia.org/wiki/Eye_of_GNOME Eye of GNOME], [http://en.wikipedia.org/wiki/F-Spot F-Spot], [http://en.wikipedia.org/wiki/Shotwell_(software) Shotwell], [http://en.wikipedia.org/wiki/GThumb gThumb], etc. It is worth mentioning at this point that if you shoot in "RAW+JPEG" mode then you could in fact be wasting space on your memory card and gaining nothing for it, as your raw files most likely already contain an embedded JPEG identical to the external one saved in "RAW+JPEG" mode.<br />
# Most raw development programs (programs which do read the real raw data instead of just reading the embedded JPEG) apply some processing to it, such as a base tone curve, even at their most neutral settings, thereby making it impossible for users to see the real, untouched contents of their raw photos. Adobe Lightroom is an example. Comparing RawTherapee's real [[Neutral]] image to a pseudo-neutral one from these other programs will expose the differences.<br />
<br />
RawTherapee, on the other hand, is capable of showing you the real raw image in the main preview, leaving the way you want this data processed up to you. When you use the "[[Neutral]]" processing profile you will see the demosaiced image with camera white balance in your working color space with no other modifications. You can even see the non-demosaiced image by setting the [[Demosaicing#Method|demosaicing method]] to "None".<br />
<br />
To provide you with a more aesthetically pleasing starting point, RawTherapee by default uses the [[Auto-Matched_Curve]] processing profile, which automatically generates a tone curve to make the tones of the raw image match those of the embedded JPEG, if one exists. If one does not exist, you can use the [[Standard_Film_Curve]] processing profile, which applies a curve which looks good in most cases. Choose the sub-type (ISO Low/Medium/High) depending on how noisy your image is.<br />
<br />
=== Scrollable Toolbars ===<br />
<br />
The toolbars above and below the main preview hold a certain number of buttons and other widgets which might not fit on lower resolution screens. {{:Scrollable Toolbar}}<br />
<br />
=== Background Color of the Preview ===<br />
<br />
[[File:Rt59 preview background all.png|none]]<br />
<br />
The background color of the preview panel may be changed to allow you to better judge how the image tones will appear when the saved image is viewed on a website (or image viewer, or print) of a similar background color.<br />
<br />
This choice also applies to the cropped-off area, if the image is cropped. See "[[Preferences#Appearance|Preferences > General > Appearance > Crop mask color]]".<br />
<br />
Available options:<br />
* theme-based (see [[Preferences#Appearance|Preferences > General > Appearance]]),<br />
* black,<br />
* [https://en.wikipedia.org/wiki/Middle_gray L* middle grey],<br />
* white.<br />
<br />
=== Preview Channel ===<br />
<br />
[[File:Rt59_preview_channel_all.png|none]]<br />
<br />
The preview can be toggled to show one of the following channels:<br />
* red,<br />
* green,<br />
* blue,<br />
* luminosity, which is calculated as 0.299*R + 0.587*G + 0.114*B.<br />
<br />
==== Red, Green, Blue and Luminosity Preview Modes ====<br />
<br />
{{:Clipping_Indication}}<br />
<br />
Preview of individual channels may be helpful when editing RGB curves, planning black/white conversion using the channel mixer, evaluating image noise, etc. Luminosity preview is helpful to instantly view the image in black and white without altering development parameters, to see which channel might be clipping or for aesthetic reasons.<br />
<br />
==== Focus Mask ====<br />
<br />
[[Image:Preview_6_focus_2.jpg|Focus mask indicating the focusing plane|thumb]]<br />
The focus mask is designed to highlight areas of the image which are in focus. Naturally, focused areas are sharper, so the sharp areas are being highlighted. The focus mask is more accurate on images with a shallow depth of field, low noise and at higher zoom levels.To improve detection accuracy for noisy images evaluate at smaller zoom, around the 10-30% range. Note that the preview is rendered more slowly when the focus mask is enabled.<br />
<br />
The current implementation analyzes the preview image which is rescaled from the original captured size. This process of rescaling reduces the noise and is helpful to identify truly sharper details rather than noise itself which may also contain micro texture. At the same time, rescaling of the original image to the preview size compresses larger scale details into a smaller size, and it may introduce aliasing artifacts, both of which could lead to false positives. You can increase your confidence by viewing the mask at various zoom levels. It is not always fault proof, but can be helpful in many cases.<br />
<br />
'''Warning''': Be sure to double-check your images if you decide to delete them based on the focus mask.<br />
<br />
=== Detail Window ===<br />
<br />
The "New detail window" button [[File:Window-add.png]], situated below the main preview next to the zoom buttons, opens a new viewport over the main preview of an adjustable size and of adjustable zoom. This lets you work on the photo zoomed-to-fit while examining several areas of interest at a 100% zoom (or even more). The benefit of using this feature is particularly important to users with slower machines, though not only them, as the zoomed-out main preview takes a shorter amount of time to update than if you were to zoom it to 100% because working at a zoom level less than 100% excludes certain slow tools, such as Noise Reduction, while the little detail windows zoomed to 100% do include all tools and are fast to update because of their small size. This allows you can use the main preview for your general exposure tweaks where it is necessary to see the whole image, and one or more detail windows to get sharpening and/or noise reduction just right.<br />
<br />
=== Preview refresh delay ===<br />
<br />
Changing any tool's parameters sends a signal for the preview image to be updated accordingly. Imagine what would happen if there was no "delay period", and you dragged, for example, the exposure compensation slider from 0.00 to +0.60. A signal would be sent to update the preview for every single change of that value - for +0.01, +0.02, ... +0.59, +0.60. Updating the preview 60 times would be completely unnecessary and actually take longer than it takes you to move the slider. This is especially true for more complicated tools, such as noise reduction, where a preview update can take even a second (depending on your CPU and preview size). The solution is for RawTherapee to wait for a very short period from the moment you stop moving a slider (you don't have to let go of it, pausing movement is enough) until the moment it sends a signal for the preview to be refreshed.<br />
<br />
We have introduced two parameters which control the length of this waiting period:<br />
; AdjusterMinDelay<br />
: Default value = 100ms.<br />
: This is used for tools with a very fast response time, for example the exposure compensation slider.<br />
; AdjusterMaxDelay<br />
: Default value = 200ms.<br />
: This is used for tools with a slow response time, for example the CIECAM02 sliders.<br />
<br />
You can adjust both of these values in the options file in the [[File_Paths|config folder]].<br />
<br />
== The Left Panel ==<br />
<br />
To the left is a panel which optionally shows the main histogram ("''Preferences > General > Layout > Histogram in left panel''"), and always shows the ''Navigator'', ''History'' and ''Snapshots''.<br />
You can hide this panel using the [[Image:panel-to-left.png|Hide left panel icon]] hide icon, or its [[Keyboard Shortcuts|keyboard shortcut]].<br />
<br />
=== Main Histogram ===<br />
<br />
[[File:Rt57 histogram wide labeled.png|none|frame|class=heroed|Histogram showing all 3 channels and luminosity.]]<br />
<br />
[[File:RT57 histogram ani.gif|frame|The histogram in RawTherapee 5.7, showing a histogram of the raw data in all three modes - linear-linear, linear-log and log-log. We can see that the raw file is not clipped.]]<br />
<br />
[[File:Rt histogram rgbindicator.png|frame|The RGB indicator shows the position in the histogram of the R, G, B and L values of the pixel your cursor is hovering over.]]<br />
<br />
A histogram in photography is a graphical representation of the number of pixels of a given value. Typically the horizontal axis represents the range of possible values while the vertical axis represents the count of pixels with that value. The axes need not be linear - RawTherapee can also scale the histogram logarithmically.<br />
<br />
Regardless of the photo's bit depth, the histogram itself has a precision of 256 sampling bins. To understand this, let us look at the example of a 16-bit image using integer precision. Its range of possible values spans from 0 to 65535 (2^16 = 65536 possible values, and since 0 is a possible minimum value then the maximum value is 65535). Drawing a histogram using 16-bit precision would mean that it would need to be 65535 pixels wide to faithfully represent the data, and no screen today is anywhere near that wide. Instead, all pixels with values from 0 to 255 (65535/256*1) are grouped into the first "bin". The second bin consists of a count of all pixels with values from 256 to 511 (65535/256*2). The third bin represents values 512 to 767 (65535/256*3). And so on until bin 256. This happens regardless of the input image's bit depth - and RawTherapee's engine uses 32-bit floating-point precision anyway.<br />
<br />
The main histogram can simultaneously show one or more of the following:<br />
* [[File:Histogram-red-on-small.svg]] the red channel,<br />
* [[File:Histogram-green-on-small.svg]] the green channel,<br />
* [[File:Histogram-blue-on-small.svg]] the blue channel,<br />
* [[File:Histogram-silver-on-small.svg]] CIELab luminance,<br />
* [[File:Histogram-gold-on-small.svg]] [http://en.wikipedia.org/wiki/Chromaticity chromaticity].<br />
* [[File:Histogram-bayer-on-small.svg]] red, green and blue channels of the source raw image before demosaicing.<br />
<br />
The histogram shows the channels listed above using the gamma-corrected output profile when the gamut button [[File:Gamut-hist.png]] is disabled (default), or using the working profile when the button is enabled. The status of this button also affects the values shown in the Navigator panel, as well as the clipped shadow [[File:Warning-shadows.png]] and [[File:Warning-highlights.png]] highlight indicators. It does not affect the raw histogram.<br />
<br />
Like water in a pipeline, image data flows through RawTherapee from the input file through various stages, most of which the user can control, to the output. The output could be the image saved in a file, or the image displayed on your screen. Each stage affects the color data. The histogram allows you to visualize this data at several stages. By default, the histogram shows color data as it will appear if you save the output image, including processing done at all intermediate stages. By enabling the gamut button [[File:Gamut-hist.png]] you can peak at the data at the early stage where it gets converted into the working space. You can even look at the raw data before any transformations or demosaicing are applied.<br />
<br />
Let's examine the large histogram example above. Though it actually shows four histograms (red, green, blue and luminance), focus on one histogram at a time. The horizontal axis represents the possible values of the histogram, where "A" are the darkest values possible, "C" the mid-tones, and "E" the brightest possible values. The position of the histogram line on the vertical axis represents how many pixels have that value. We can see that there are zero pixels in the red channel with values around "A" (from zero to very dark), because the histogram line lies right along the bottom. There is a significant number of pixels where the red channel is dark (between A and B), and a significant number where it is light (around D). Then, importantly, there is a spike at the right end of the histogram, at E - it tells us that a large number of pixels have maximal red values - they are clipped.<br />
<br />
Generally speaking, you should care when clipping occurs on skin, and not care when it's due to [https://en.wikipedia.org/wiki/Specular_highlight specular highlights]. If a histogram shows clipping, and if you care about the clipped regions, you should start by establishing where the clipping occurs. Check the raw histogram - are any channels clipped? If yes, then maybe [[Exposure#Highlight_Reconstruction|highlight reconstruction]] can help. If the raw histograms are not clipped, then all the required information is intact, and it is some stage downstream in the pipeline which causes clipping. Ensure your working profile's gamut is large enough by enabling the gamut button [[File:Gamut-hist.png]] to see histograms at the working profile stage of the pipeline. You might want to temporarily apply the [[Neutral]] profile to disable all the tools while checking, then revert. If your working space is not causing clipping (the default working space is ProPhoto and it's huge), then it's likely your adjustments which are causing clipping. Reduce exposure, go easy on the curves, use dynamic range compression if necessary.<br />
<br />
Knowing how to read a histogram is a basic and very useful skill, as it can point out issues with your image regardless of how dim or miscalibrated your monitor may be.<br />
<br />
To help you visualize the data, the histogram (as of RawTherapee 5.5) has three modes which scale the data in the x and y axes differently:<br />
* [[File:Histogram-mode-linear-small.png]] Linear-linear mode. You find gridlines at halves, quarters, eighths and sixteenths, depending on the size of the histogram.<br />
* [[File:Histogram-mode-logx-small.png]] Linear-log mode. The x-axis is linear, the y-axis and the horizontal gridlines are scaled logarithmically. The position of the gridlines still corresponds to the halves, quarters, etc.<br />
* [[File:Histogram-mode-logxy-small.png]] Log-log mode. Both the x- and y-axes are scaled logarithmically. The gridlines are not scaled logarithmically, but correspond to [https://en.wikipedia.org/wiki/Exposure_value stops] - with every gridline the value doubles, so there are lines for the values 1, 3, 7, 15, 31, 63, and 127 (<code>pow(2.0,i) - 1)</code>).<br />
<br />
When there is a disproportionately bright area relative to the rest of the image, it will show up as a spike in the histogram. If you want to show this on a histogram with a linear y axis, the spike may push the lesser values down the y-axis, making them difficult to see. Switch to one of the log modes to scale the data and help you get a better overview of all values.<br />
<br />
The histogram can be moved to the left/right panel from "''Preferences > General > Layout > Histogram in left panel''".<br />
<br />
==== Raw Histograms ====<br />
<br />
Raw files contain a dump of data captured by the sensor and quantified by the analog-to-digital converter. The raw file as a container has a bit depth of its own, typically 16-bit, while the data it contains could have a lower bit depth - typically it is 12-bit (0-4096) or 14-bit (0-16384). To display the data from a raw file as an image, one of the several key bits of information required to process the data correctly are the black and white levels. The black level is not necessarily 0, as the sensor and camera electronics produce digital noise, so the noise floor may lie for instance at 512. The white level is also not necessarily 16384; it depends on various things, and may lie for instance at 16300. For more information, see the articles [[Demosaicing]] and [[Adding Support for New Raw Formats]] (especially the header of the <code>camconst.json</code> file). The black and white level values used by RawTherapee are hierarchically set by looking in several places: in <code>dcraw.c</code>, inside the raw file's metadata, and in <code>camconst.json</code> (latter takes precedence). Furthermore, the user can tweak the raw [[Raw Black Points|black]] and [[Raw White Points|white]] levels from within RawTherapee.<br />
<br />
The raw histograms show data after black level subtraction. The right end of the histogram is anchored on the white level. The raw histograms are affected by the detected black and white levels as well as by the black and white level adjustments made by the user in RawTherapee.<br />
<br />
When examining the raw histogram, you may also want to set the demosaicing method to "none". This will reveal the sensor pattern in the preview, and also cause the [[Editor#Navigator|Navigator]] panel to show the raw RGB values of the pixel currently being hovered over. These values are affected by the detected black and white levels as well as by the black level adjustments made by the user in RawTherapee, but they are not affected by the white level adjustments ("white-point correction") made by the user in RawTherapee.<br />
<br />
=== Navigator ===<br />
<br />
The ''Navigator'' panel shows a thumbnail of the currently opened image, and RGB, HSV and Lab values of the pixel your cursor is currently hovering over.<br />
<br />
The values shown in the main histogram and Navigator panel are either those of the working profile or of the gamma-corrected output profile, depending on the state of the gamut button [[File:Gamut-hist.png]] located in the toolbar above the main preview. When the gamut button is enabled the working profile is used, otherwise the gamma-corrected output profile is used.<br />
<br />
By clicking on the values in the Navigator you can cycle between these three formats:<br />
* [0-255]<br />
* [0-1]<br />
* [%]<br />
<br />
RawTherapee 5.1 onward can show the real raw photosite values. To see them, set the Navigator to use the [0-255] range, apply the [[Neutral]] [[Sidecar_Files_-_Processing_Profiles|processing profile]], then set the [[Demosaicing]] method to "None". The Navigator will show the real raw photosite values after black level subtraction within the range of the original raw data.<br />
<br />
=== History ===<br />
<br />
The History panel contains a stack of entries which reflect each of your image editing actions. By clicking on the entries you can step back and forth through the different stages of your work.<br />
<br />
An entry is added each time you adjust a ''different'' widget - multiple edits to the same widget are stored as one entry. For example, adjusting the exposure compensation slider from "0" to "0.3" and then to "0.6" will result in one entry being stored with a final value of "0.6". Likewise, when adjusting a curve, all individual control point adjustments are grouped into one history entry. Should you wish to store the adjustments as two (or more) history entries, you will have to split them by adjusting some other widget. For example, assuming a curve is in "Film-like" mode and you want to keep to that way: adjust several control points on the curve, then toggle the curve mode from "Film-like" to "Standard" and then back to "Film-like" to create a new history entry, and then continue adjusting the curve.<br />
<br />
The history stack is not saved - it is lost as soon as you close the Editor tab. None of your adjustments are lost though, as the final state of all tools is saved in the [[Sidecar Files - Processing Profiles|sidecar file]], ready to be used the next time you open that image.<br />
<br />
=== Snapshots ===<br />
<br />
Under the ''History'' panel is a panel called ''Snapshots''. Its use is in that you can save a snapshot of the photo with all the adjustments up to that point in time, and then proceed to further modify your photo to give it a different appearance, saving new snapshots at every moment you feel you might have reached a version of your photo worth saving. Once you have two or more snapshots, you can just click on them to flip through the different versions and stick with whichever one you like best. In the future, the snapshots will be saved to the PP3 sidecar file. For now, the history and snapshots are lost when you load a new photo in the ''Image Editor'' or close RawTherapee.<br />
<br />
== The Right Panel ==<br />
<br />
To the right is a panel which optionally shows the main histogram and ''Processing Profiles'' selector ("''Preferences > General > Layout > Histogram in left panel''"), and always shows the [[Toolbox]].<br />
You can hide this panel using the [[Image:panel-to-right.png|Hide right panel icon]] hide icon, or its [[Keyboard Shortcuts|keyboard shortcut]].<br />
<br />
=== Processing Profile Selector ===<br />
<br />
The Processing Profiles panel allows you to apply, save, load, copy and paste processing profiles, partially or in full.<br />
<br />
[[File:Processing-profiles-selector.png|center|frame]]<br />
<br />
Read the [[Sidecar_Files_-_Processing_Profiles | Sidecar Files / Processing Profiles]] page for more information.<br />
<br />
=== Toolbox ===<br />
<br />
The ''Toolbox'', in the right panel, contains all the tools you use to tweak your photos. Each tool has its own RawPedia article.<br />
<br />
== Editor Tab Modes ==<br />
<br />
RawTherapee allows you to work on photos in two modes:<br />
* ''Single Editor Tab Mode'' (SETM), where you work only on one photo at a time, and each photo is opened in the same ''Editor'' tab. There is a horizontal panel called the ''[[The_Image_Editor_Tab#The_Filmstrip | Filmstrip]]'' at the top of the ''[[The_Image_Editor_Tab#The_Filmstrip | Editor]]'' tab showing the rest of the photos in that folder for easy access. There are ''Previous Image'' and ''Next Image'' [[File:Nav-prev.png]] [[File:Nav-next.png]] buttons in the bottom toolbar (and [[Keyboard Shortcuts | keyboard shortcuts]] for them) to switch to the previous/next image.<br />
* ''Multiple Editor Tabs Mode'' (METM), where each photo is opened in its own ''[[The_Image_Editor_Tab#The_Filmstrip | Editor]]'' tab. The ''[[The_Image_Editor_Tab#The_Filmstrip | Filmstrip]]'' is hidden in this mode and there are no previous/next buttons. Having multiple photos opened at the same time requires more RAM.<br />
<br />
Try both modes and see which one suits you best. To do that, click on the ''Preferences'' icon [[image:preferences.png|Preferences icon]] in the bottom-left or top-right corner of the RT window, choose "''General > Layout''" and set ''Editor Layout'' to your preferred choice.<br />
<br />
Use this ''Preferences'' window to select a different language for the user interface, to choose a different color theme, change the font size, etc.<br />
<br />
It is also possible to start RawTherapee in no-File-Browser-mode (without the ''File Browser'' tab) by specifying RawTherapee to open an image from your operating system's file browser (in other words, right-click on a photo and select "''Open With > RawTherapee''"), or by using the image filename as an argument when starting RawTherapee from the command line (<code>rawtherapee /path/to/some/photo.raw</code>). This mode was introduced for people with little RAM as not having a ''File Browser'' tab means RawTherapee uses a little less memory, however in practice the amount of memory saved is little and the usability cost outweighs the little benefit, so it is likely to be removed in the future (see [https://code.google.com/p/rawtherapee/issues/detail?id=2254 issue 2254]).<br />
<br />
== The Filmstrip ==<br />
<br />
[[File:Rt filmstrip 21 toolbar-visible.jpg|none|frame|class=heroed|RawTherapee-4.2 showing the Filmstrip with the toolbar visible, which takes up more screen space but lets you easily label, rate and filter the visible thumbnails.]]<br />
[[File:Rt filmstrip 21 toolbar-hidden.jpg|none|frame|class=heroed|RawTherapee-4.2 showing the Filmstrip with the toolbar hidden, which makes it less high and provides more screen space for the main preview (partially visible at the bottom).]]<br />
<br />
If you use ''Single Editor Tab Mode'' ("''Preferences > General > Layout''") you can display a horizontal panel above the preview, this is called the ''Filmstrip''. It contains thumbnails of all images in the currently opened album, and is synchronized with the currently opened image so that you can use [[Keyboard Shortcuts|keyboard shortcuts]] or the previous [[Image:nav-prev.png|Open previous image icon]] and next [[Image:nav-next.png|Open next image icon]] image buttons to open the previous/next image without needing to go back to the ''[[The File Browser Tab|File Browser]]'' tab.<br />
<br />
As of RawTherapee version 4.2.10, you can hide the Filmstrip's toolbar to save screen space. There are two ways of doing this: one way just toggles the toolbar on/off without resizing the filmstrip to the new height, and the other way does the same but also automatically resizes the filmstrip's height. Both are invoked via [[Keyboard Shortcuts|keyboard shortcuts]] only. As resizing the filmstrip's height will trigger a refresh of the image preview and this might take a while if using CPU-hungry tools like noise reduction while zoomed in at 100%, the mode that doesn't resize has been implemented for users with slow machines. Users with fast machines will find the auto-resizing mode more helpful.<br />
<br />
== Monitor Profile and Soft-Proofing ==<br />
<br />
The widgets under the main preview in RawTherapee 5 allow you to apply a monitor color profile to the preview image. This enables users who have calibrated and profiled their monitors to get an instant and accurate preview of their work, whether you're staying in sRGB or working in a wide gamut. Note: OS X users are limited to sRGB and will not get an accurate preview otherwise ([https://discuss.pixls.us/t/wide-gamut-preview-in-os-x/2481 see discussion]), while users of Linux and Windows will get a correct wide-gamut preview.<br />
<br />
Go to Preferences > [[Preferences#Color_Management_Tab|Color Management]] and point the "Directory containing color profiles" to the folder into which you saved your monitor and printer ICC profile. Restart RawTherapee for the changes to take effect. Now you will be able to select your monitor's color profile in the combo-box under the preview. Use the "Relative Colorimetric" rendering intent unless you have a good reason otherwise.<br />
<br />
One can also enable soft-proofing of the preview. This will show you what your image will look like once it gets transformed by the printer profile set in Preferences > [[Preferences#Color_Management_Tab|Color Management]]. If you want to adjust an image for printing and you have an ICC profile for your printer-paper combination you could set that as your output profile, enable "Black point compensation" in Preferences so that the blackest black in your image will match the blackest black your printer-paper combination is capable of reproducing, then enable soft-proofing. You will see what your image will look like if you print it. This allows you to make adjustments and get an instant preview of the result, saving you time and ink on test prints.<br />
<br />
The icon with exclamation mark next to the soft-proofing button will gray out areas that cannot be reproduced by your printer, i.e. areas where you will loose details.<br />
<br />
You should have a calibrated and profiled monitor in order for the soft-proofing preview to be accurate.<br />
<br />
The items you see in the monitor profile combo-box (under the main preview) and in the printer profile combobox (in Preferences > [[Preferences#Color_Management_Tab|Color Management]]) are ICC files located in a folder which you can point RawTherapee to by going to "[[Preferences]] > [[Preferences#Color_Management_Tab|Color Management]] > Directory containing color profiles".</div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=Editor&diff=9835Editor2022-11-22T19:09:01Z<p>DrSlony: /* Preview Modes */ preview channel</p>
<hr />
<div><div class="pagetitle">The Editor</div><br />
<br />
[[File:Rt 55 trains.png|none|frame|link=|class=heroed|The Image Editor tab in RawTherapee 5.5.]]<br />
<br />
== Introduction ==<br />
<br />
The Image Editor tab is where you tweak your photos. By default RawTherapee is in "Single Editor Tab Mode, Vertical Tabs" (SETM/VT) which is more memory-efficient and lets you use the [[Editor#The_Filmstrip|Filmstrip]] (described below). You can switch to "Multiple Editor Tabs Mode" (METM) by going to "[[Preferences#Layout|Preferences > General > Layout]]", however each Editor tab will require a specific amount of RAM relative to the image size and the tools you use, and also the Filmstrip is hidden in this mode, so we recommend you first give SETM a try.<br />
<br />
== The Preview Panel ==<br />
<br />
The central panel shows a preview of the image being edited. This preview is generated from raw data if such is available. It reflects the adjustments made by the tools in the [[Editor#Toolbox|Toolbox]]. Note that the effects of some tools are only accurately visible when you are zoomed in to 1:1 (100%) or more; these tools are marked in the interface with a "1:1" icon [[File:One-to-one-small.png|Zoom 1:1]] alongside the tool's name.<br />
<br />
When opening an image, RawTherapee loads the tool settings from the sidecar file if one exists, else it applies a default sidecar file as specified in "[[Preferences#Default_Processing_Profile|Preferences > Image Processing > Default Processing Profile]]". When you close the image (which happens automatically if you open a different image or if you close RawTherapee) the current tool settings are automatically saved to a sidecar file as specified in "[[Preferences#Processing_Profile_Handling|Preferences > Image Processing > Processing Profile Handling]]".<br />
<br />
=== Eek! My Raw Photo Looks Different than the Camera JPEG ===<br />
<br />
When opening a raw photo you may notice that it looks different from your camera's JPEG, or from what other software show when viewing the same raw photo. In some cases this difference is minute, but in other cases it could be significant - the image could be darker, lack contrast, be less sharp and more noisy. What gives?<br />
<br />
There are three things you must know first to understand what is happening here:<br />
# Your camera does not show you the real raw data when you shoot raw photos. It processes the raw image in many ways before presenting you with the histogram and the preview on your camera's display. Even if you set all the processing features which your camera's firmware allows you to tweak to their neutral, "0" positions, what you see is still not an unprocessed image. Exactly what gets applied depends on the choices made by your camera's engineers and company management, but usually this includes a custom tone curve, saturation boost, sharpening and noise reduction. Some cameras, particularly low-end ones and [http://en.wikipedia.org/wiki/Micro_Four_Thirds_system Micro Four-Thirds system], may also apply lens distortion correction to not only fix [http://en.wikipedia.org/wiki/Distortion_(optics)#Radial_distortion barrel and pincushion distortion] but also to hide dark corners caused by severe [http://en.wikipedia.org/wiki/Vignetting vignetting] or by the [https://en.wikipedia.org/wiki/Lens_hood lens hood]. Most cameras also underexpose every photo you take by anywhere from -0.3EV to -1.3EV or more, in order to gain headroom in the highlights. When your camera (or other raw editing software) processes the raw file it compensates for this by increasing exposure compensation by the same amount.<br />
# When shooting a raw photo, most cameras embed within the raw file a full-resolution JPEG image with tone curves and other adjustments applied. Some raw files contain as many as three JPEG images differing only in resolution. Most cameras offer storing photos in one of three modes: "RAW", "JPEG", or "RAW+JPEG". The embedded JPEG image discussed here is stored within the raw file even in just "RAW" mode! When you open raw files in other software, what you are usually seeing is '''not''' the raw data, but the embedded, processed JPEG image! Examples of software which are either incapable of or which in their default settings do not show you the real raw data: [http://en.wikipedia.org/wiki/IrfanView IrfanView], [http://en.wikipedia.org/wiki/XnView XnView], [http://en.wikipedia.org/wiki/Gwenview Gwenview], [http://en.wikipedia.org/wiki/Geeqie Geeqie], [http://en.wikipedia.org/wiki/Eye_of_GNOME Eye of GNOME], [http://en.wikipedia.org/wiki/F-Spot F-Spot], [http://en.wikipedia.org/wiki/Shotwell_(software) Shotwell], [http://en.wikipedia.org/wiki/GThumb gThumb], etc. It is worth mentioning at this point that if you shoot in "RAW+JPEG" mode then you could in fact be wasting space on your memory card and gaining nothing for it, as your raw files most likely already contain an embedded JPEG identical to the external one saved in "RAW+JPEG" mode.<br />
# Most raw development programs (programs which do read the real raw data instead of just reading the embedded JPEG) apply some processing to it, such as a base tone curve, even at their most neutral settings, thereby making it impossible for users to see the real, untouched contents of their raw photos. Adobe Lightroom is an example. Comparing RawTherapee's real [[Neutral]] image to a pseudo-neutral one from these other programs will expose the differences.<br />
<br />
RawTherapee, on the other hand, is capable of showing you the real raw image in the main preview, leaving the way you want this data processed up to you. When you use the "[[Neutral]]" processing profile you will see the demosaiced image with camera white balance in your working color space with no other modifications. You can even see the non-demosaiced image by setting the [[Demosaicing#Method|demosaicing method]] to "None".<br />
<br />
To provide you with a more aesthetically pleasing starting point, RawTherapee by default uses the [[Auto-Matched_Curve]] processing profile, which automatically generates a tone curve to make the tones of the raw image match those of the embedded JPEG, if one exists. If one does not exist, you can use the [[Standard_Film_Curve]] processing profile, which applies a curve which looks good in most cases. Choose the sub-type (ISO Low/Medium/High) depending on how noisy your image is.<br />
<br />
=== Scrollable Toolbars ===<br />
<br />
The toolbars above and below the main preview hold a certain number of buttons and other widgets which might not fit on lower resolution screens. {{:Scrollable Toolbar}}<br />
<br />
=== Background Color of the Preview ===<br />
<br />
[[File:Rt59 preview background all.png|left|frame]]<br />
<br />
The background color of the preview panel may be changed to allow you to better judge how the image tones will appear when the saved image is viewed on a website (or image viewer, or print) of a similar background color.<br />
<br />
This choice also applies to the cropped-off area, if the image is cropped. See "[[Preferences#Appearance|Preferences > General > Appearance > Crop mask color]]".<br />
<br />
Available options:<br />
* theme-based (see [[Preferences#Appearance|Preferences > General > Appearance]]),<br />
* black,<br />
* [https://en.wikipedia.org/wiki/Middle_gray L* middle grey],<br />
* white.<br />
<br />
=== Preview Channel ===<br />
<br />
[[File:Rt59_preview_channel_all.png|none]]<br />
<br />
The preview can be toggled to show one of the following channels:<br />
* red,<br />
* green,<br />
* blue,<br />
* luminosity, which is calculated as 0.299*R + 0.587*G + 0.114*B.<br />
<br />
==== Red, Green, Blue and Luminosity Preview Modes ====<br />
<br />
{{:Clipping_Indication}}<br />
<br />
Preview of individual channels may be helpful when editing RGB curves, planning black/white conversion using the channel mixer, evaluating image noise, etc. Luminosity preview is helpful to instantly view the image in black and white without altering development parameters, to see which channel might be clipping or for aesthetic reasons.<br />
<br />
==== Focus Mask ====<br />
<br />
[[Image:Preview_6_focus_2.jpg|Focus mask indicating the focusing plane|thumb]]<br />
The focus mask is designed to highlight areas of the image which are in focus. Naturally, focused areas are sharper, so the sharp areas are being highlighted. The focus mask is more accurate on images with a shallow depth of field, low noise and at higher zoom levels.To improve detection accuracy for noisy images evaluate at smaller zoom, around the 10-30% range. Note that the preview is rendered more slowly when the focus mask is enabled.<br />
<br />
The current implementation analyzes the preview image which is rescaled from the original captured size. This process of rescaling reduces the noise and is helpful to identify truly sharper details rather than noise itself which may also contain micro texture. At the same time, rescaling of the original image to the preview size compresses larger scale details into a smaller size, and it may introduce aliasing artifacts, both of which could lead to false positives. You can increase your confidence by viewing the mask at various zoom levels. It is not always fault proof, but can be helpful in many cases.<br />
<br />
'''Warning''': Be sure to double-check your images if you decide to delete them based on the focus mask.<br />
<br />
=== Detail Window ===<br />
<br />
The "New detail window" button [[File:Window-add.png]], situated below the main preview next to the zoom buttons, opens a new viewport over the main preview of an adjustable size and of adjustable zoom. This lets you work on the photo zoomed-to-fit while examining several areas of interest at a 100% zoom (or even more). The benefit of using this feature is particularly important to users with slower machines, though not only them, as the zoomed-out main preview takes a shorter amount of time to update than if you were to zoom it to 100% because working at a zoom level less than 100% excludes certain slow tools, such as Noise Reduction, while the little detail windows zoomed to 100% do include all tools and are fast to update because of their small size. This allows you can use the main preview for your general exposure tweaks where it is necessary to see the whole image, and one or more detail windows to get sharpening and/or noise reduction just right.<br />
<br />
=== Preview refresh delay ===<br />
<br />
Changing any tool's parameters sends a signal for the preview image to be updated accordingly. Imagine what would happen if there was no "delay period", and you dragged, for example, the exposure compensation slider from 0.00 to +0.60. A signal would be sent to update the preview for every single change of that value - for +0.01, +0.02, ... +0.59, +0.60. Updating the preview 60 times would be completely unnecessary and actually take longer than it takes you to move the slider. This is especially true for more complicated tools, such as noise reduction, where a preview update can take even a second (depending on your CPU and preview size). The solution is for RawTherapee to wait for a very short period from the moment you stop moving a slider (you don't have to let go of it, pausing movement is enough) until the moment it sends a signal for the preview to be refreshed.<br />
<br />
We have introduced two parameters which control the length of this waiting period:<br />
; AdjusterMinDelay<br />
: Default value = 100ms.<br />
: This is used for tools with a very fast response time, for example the exposure compensation slider.<br />
; AdjusterMaxDelay<br />
: Default value = 200ms.<br />
: This is used for tools with a slow response time, for example the CIECAM02 sliders.<br />
<br />
You can adjust both of these values in the options file in the [[File_Paths|config folder]].<br />
<br />
== The Left Panel ==<br />
<br />
To the left is a panel which optionally shows the main histogram ("''Preferences > General > Layout > Histogram in left panel''"), and always shows the ''Navigator'', ''History'' and ''Snapshots''.<br />
You can hide this panel using the [[Image:panel-to-left.png|Hide left panel icon]] hide icon, or its [[Keyboard Shortcuts|keyboard shortcut]].<br />
<br />
=== Main Histogram ===<br />
<br />
[[File:Rt57 histogram wide labeled.png|none|frame|class=heroed|Histogram showing all 3 channels and luminosity.]]<br />
<br />
[[File:RT57 histogram ani.gif|frame|The histogram in RawTherapee 5.7, showing a histogram of the raw data in all three modes - linear-linear, linear-log and log-log. We can see that the raw file is not clipped.]]<br />
<br />
[[File:Rt histogram rgbindicator.png|frame|The RGB indicator shows the position in the histogram of the R, G, B and L values of the pixel your cursor is hovering over.]]<br />
<br />
A histogram in photography is a graphical representation of the number of pixels of a given value. Typically the horizontal axis represents the range of possible values while the vertical axis represents the count of pixels with that value. The axes need not be linear - RawTherapee can also scale the histogram logarithmically.<br />
<br />
Regardless of the photo's bit depth, the histogram itself has a precision of 256 sampling bins. To understand this, let us look at the example of a 16-bit image using integer precision. Its range of possible values spans from 0 to 65535 (2^16 = 65536 possible values, and since 0 is a possible minimum value then the maximum value is 65535). Drawing a histogram using 16-bit precision would mean that it would need to be 65535 pixels wide to faithfully represent the data, and no screen today is anywhere near that wide. Instead, all pixels with values from 0 to 255 (65535/256*1) are grouped into the first "bin". The second bin consists of a count of all pixels with values from 256 to 511 (65535/256*2). The third bin represents values 512 to 767 (65535/256*3). And so on until bin 256. This happens regardless of the input image's bit depth - and RawTherapee's engine uses 32-bit floating-point precision anyway.<br />
<br />
The main histogram can simultaneously show one or more of the following:<br />
* [[File:Histogram-red-on-small.svg]] the red channel,<br />
* [[File:Histogram-green-on-small.svg]] the green channel,<br />
* [[File:Histogram-blue-on-small.svg]] the blue channel,<br />
* [[File:Histogram-silver-on-small.svg]] CIELab luminance,<br />
* [[File:Histogram-gold-on-small.svg]] [http://en.wikipedia.org/wiki/Chromaticity chromaticity].<br />
* [[File:Histogram-bayer-on-small.svg]] red, green and blue channels of the source raw image before demosaicing.<br />
<br />
The histogram shows the channels listed above using the gamma-corrected output profile when the gamut button [[File:Gamut-hist.png]] is disabled (default), or using the working profile when the button is enabled. The status of this button also affects the values shown in the Navigator panel, as well as the clipped shadow [[File:Warning-shadows.png]] and [[File:Warning-highlights.png]] highlight indicators. It does not affect the raw histogram.<br />
<br />
Like water in a pipeline, image data flows through RawTherapee from the input file through various stages, most of which the user can control, to the output. The output could be the image saved in a file, or the image displayed on your screen. Each stage affects the color data. The histogram allows you to visualize this data at several stages. By default, the histogram shows color data as it will appear if you save the output image, including processing done at all intermediate stages. By enabling the gamut button [[File:Gamut-hist.png]] you can peak at the data at the early stage where it gets converted into the working space. You can even look at the raw data before any transformations or demosaicing are applied.<br />
<br />
Let's examine the large histogram example above. Though it actually shows four histograms (red, green, blue and luminance), focus on one histogram at a time. The horizontal axis represents the possible values of the histogram, where "A" are the darkest values possible, "C" the mid-tones, and "E" the brightest possible values. The position of the histogram line on the vertical axis represents how many pixels have that value. We can see that there are zero pixels in the red channel with values around "A" (from zero to very dark), because the histogram line lies right along the bottom. There is a significant number of pixels where the red channel is dark (between A and B), and a significant number where it is light (around D). Then, importantly, there is a spike at the right end of the histogram, at E - it tells us that a large number of pixels have maximal red values - they are clipped.<br />
<br />
Generally speaking, you should care when clipping occurs on skin, and not care when it's due to [https://en.wikipedia.org/wiki/Specular_highlight specular highlights]. If a histogram shows clipping, and if you care about the clipped regions, you should start by establishing where the clipping occurs. Check the raw histogram - are any channels clipped? If yes, then maybe [[Exposure#Highlight_Reconstruction|highlight reconstruction]] can help. If the raw histograms are not clipped, then all the required information is intact, and it is some stage downstream in the pipeline which causes clipping. Ensure your working profile's gamut is large enough by enabling the gamut button [[File:Gamut-hist.png]] to see histograms at the working profile stage of the pipeline. You might want to temporarily apply the [[Neutral]] profile to disable all the tools while checking, then revert. If your working space is not causing clipping (the default working space is ProPhoto and it's huge), then it's likely your adjustments which are causing clipping. Reduce exposure, go easy on the curves, use dynamic range compression if necessary.<br />
<br />
Knowing how to read a histogram is a basic and very useful skill, as it can point out issues with your image regardless of how dim or miscalibrated your monitor may be.<br />
<br />
To help you visualize the data, the histogram (as of RawTherapee 5.5) has three modes which scale the data in the x and y axes differently:<br />
* [[File:Histogram-mode-linear-small.png]] Linear-linear mode. You find gridlines at halves, quarters, eighths and sixteenths, depending on the size of the histogram.<br />
* [[File:Histogram-mode-logx-small.png]] Linear-log mode. The x-axis is linear, the y-axis and the horizontal gridlines are scaled logarithmically. The position of the gridlines still corresponds to the halves, quarters, etc.<br />
* [[File:Histogram-mode-logxy-small.png]] Log-log mode. Both the x- and y-axes are scaled logarithmically. The gridlines are not scaled logarithmically, but correspond to [https://en.wikipedia.org/wiki/Exposure_value stops] - with every gridline the value doubles, so there are lines for the values 1, 3, 7, 15, 31, 63, and 127 (<code>pow(2.0,i) - 1)</code>).<br />
<br />
When there is a disproportionately bright area relative to the rest of the image, it will show up as a spike in the histogram. If you want to show this on a histogram with a linear y axis, the spike may push the lesser values down the y-axis, making them difficult to see. Switch to one of the log modes to scale the data and help you get a better overview of all values.<br />
<br />
The histogram can be moved to the left/right panel from "''Preferences > General > Layout > Histogram in left panel''".<br />
<br />
==== Raw Histograms ====<br />
<br />
Raw files contain a dump of data captured by the sensor and quantified by the analog-to-digital converter. The raw file as a container has a bit depth of its own, typically 16-bit, while the data it contains could have a lower bit depth - typically it is 12-bit (0-4096) or 14-bit (0-16384). To display the data from a raw file as an image, one of the several key bits of information required to process the data correctly are the black and white levels. The black level is not necessarily 0, as the sensor and camera electronics produce digital noise, so the noise floor may lie for instance at 512. The white level is also not necessarily 16384; it depends on various things, and may lie for instance at 16300. For more information, see the articles [[Demosaicing]] and [[Adding Support for New Raw Formats]] (especially the header of the <code>camconst.json</code> file). The black and white level values used by RawTherapee are hierarchically set by looking in several places: in <code>dcraw.c</code>, inside the raw file's metadata, and in <code>camconst.json</code> (latter takes precedence). Furthermore, the user can tweak the raw [[Raw Black Points|black]] and [[Raw White Points|white]] levels from within RawTherapee.<br />
<br />
The raw histograms show data after black level subtraction. The right end of the histogram is anchored on the white level. The raw histograms are affected by the detected black and white levels as well as by the black and white level adjustments made by the user in RawTherapee.<br />
<br />
When examining the raw histogram, you may also want to set the demosaicing method to "none". This will reveal the sensor pattern in the preview, and also cause the [[Editor#Navigator|Navigator]] panel to show the raw RGB values of the pixel currently being hovered over. These values are affected by the detected black and white levels as well as by the black level adjustments made by the user in RawTherapee, but they are not affected by the white level adjustments ("white-point correction") made by the user in RawTherapee.<br />
<br />
=== Navigator ===<br />
<br />
The ''Navigator'' panel shows a thumbnail of the currently opened image, and RGB, HSV and Lab values of the pixel your cursor is currently hovering over.<br />
<br />
The values shown in the main histogram and Navigator panel are either those of the working profile or of the gamma-corrected output profile, depending on the state of the gamut button [[File:Gamut-hist.png]] located in the toolbar above the main preview. When the gamut button is enabled the working profile is used, otherwise the gamma-corrected output profile is used.<br />
<br />
By clicking on the values in the Navigator you can cycle between these three formats:<br />
* [0-255]<br />
* [0-1]<br />
* [%]<br />
<br />
RawTherapee 5.1 onward can show the real raw photosite values. To see them, set the Navigator to use the [0-255] range, apply the [[Neutral]] [[Sidecar_Files_-_Processing_Profiles|processing profile]], then set the [[Demosaicing]] method to "None". The Navigator will show the real raw photosite values after black level subtraction within the range of the original raw data.<br />
<br />
=== History ===<br />
<br />
The History panel contains a stack of entries which reflect each of your image editing actions. By clicking on the entries you can step back and forth through the different stages of your work.<br />
<br />
An entry is added each time you adjust a ''different'' widget - multiple edits to the same widget are stored as one entry. For example, adjusting the exposure compensation slider from "0" to "0.3" and then to "0.6" will result in one entry being stored with a final value of "0.6". Likewise, when adjusting a curve, all individual control point adjustments are grouped into one history entry. Should you wish to store the adjustments as two (or more) history entries, you will have to split them by adjusting some other widget. For example, assuming a curve is in "Film-like" mode and you want to keep to that way: adjust several control points on the curve, then toggle the curve mode from "Film-like" to "Standard" and then back to "Film-like" to create a new history entry, and then continue adjusting the curve.<br />
<br />
The history stack is not saved - it is lost as soon as you close the Editor tab. None of your adjustments are lost though, as the final state of all tools is saved in the [[Sidecar Files - Processing Profiles|sidecar file]], ready to be used the next time you open that image.<br />
<br />
=== Snapshots ===<br />
<br />
Under the ''History'' panel is a panel called ''Snapshots''. Its use is in that you can save a snapshot of the photo with all the adjustments up to that point in time, and then proceed to further modify your photo to give it a different appearance, saving new snapshots at every moment you feel you might have reached a version of your photo worth saving. Once you have two or more snapshots, you can just click on them to flip through the different versions and stick with whichever one you like best. In the future, the snapshots will be saved to the PP3 sidecar file. For now, the history and snapshots are lost when you load a new photo in the ''Image Editor'' or close RawTherapee.<br />
<br />
== The Right Panel ==<br />
<br />
To the right is a panel which optionally shows the main histogram and ''Processing Profiles'' selector ("''Preferences > General > Layout > Histogram in left panel''"), and always shows the [[Toolbox]].<br />
You can hide this panel using the [[Image:panel-to-right.png|Hide right panel icon]] hide icon, or its [[Keyboard Shortcuts|keyboard shortcut]].<br />
<br />
=== Processing Profile Selector ===<br />
<br />
The Processing Profiles panel allows you to apply, save, load, copy and paste processing profiles, partially or in full.<br />
<br />
[[File:Processing-profiles-selector.png|center|frame]]<br />
<br />
Read the [[Sidecar_Files_-_Processing_Profiles | Sidecar Files / Processing Profiles]] page for more information.<br />
<br />
=== Toolbox ===<br />
<br />
The ''Toolbox'', in the right panel, contains all the tools you use to tweak your photos. Each tool has its own RawPedia article.<br />
<br />
== Editor Tab Modes ==<br />
<br />
RawTherapee allows you to work on photos in two modes:<br />
* ''Single Editor Tab Mode'' (SETM), where you work only on one photo at a time, and each photo is opened in the same ''Editor'' tab. There is a horizontal panel called the ''[[The_Image_Editor_Tab#The_Filmstrip | Filmstrip]]'' at the top of the ''[[The_Image_Editor_Tab#The_Filmstrip | Editor]]'' tab showing the rest of the photos in that folder for easy access. There are ''Previous Image'' and ''Next Image'' [[File:Nav-prev.png]] [[File:Nav-next.png]] buttons in the bottom toolbar (and [[Keyboard Shortcuts | keyboard shortcuts]] for them) to switch to the previous/next image.<br />
* ''Multiple Editor Tabs Mode'' (METM), where each photo is opened in its own ''[[The_Image_Editor_Tab#The_Filmstrip | Editor]]'' tab. The ''[[The_Image_Editor_Tab#The_Filmstrip | Filmstrip]]'' is hidden in this mode and there are no previous/next buttons. Having multiple photos opened at the same time requires more RAM.<br />
<br />
Try both modes and see which one suits you best. To do that, click on the ''Preferences'' icon [[image:preferences.png|Preferences icon]] in the bottom-left or top-right corner of the RT window, choose "''General > Layout''" and set ''Editor Layout'' to your preferred choice.<br />
<br />
Use this ''Preferences'' window to select a different language for the user interface, to choose a different color theme, change the font size, etc.<br />
<br />
It is also possible to start RawTherapee in no-File-Browser-mode (without the ''File Browser'' tab) by specifying RawTherapee to open an image from your operating system's file browser (in other words, right-click on a photo and select "''Open With > RawTherapee''"), or by using the image filename as an argument when starting RawTherapee from the command line (<code>rawtherapee /path/to/some/photo.raw</code>). This mode was introduced for people with little RAM as not having a ''File Browser'' tab means RawTherapee uses a little less memory, however in practice the amount of memory saved is little and the usability cost outweighs the little benefit, so it is likely to be removed in the future (see [https://code.google.com/p/rawtherapee/issues/detail?id=2254 issue 2254]).<br />
<br />
== The Filmstrip ==<br />
<br />
[[File:Rt filmstrip 21 toolbar-visible.jpg|none|frame|class=heroed|RawTherapee-4.2 showing the Filmstrip with the toolbar visible, which takes up more screen space but lets you easily label, rate and filter the visible thumbnails.]]<br />
[[File:Rt filmstrip 21 toolbar-hidden.jpg|none|frame|class=heroed|RawTherapee-4.2 showing the Filmstrip with the toolbar hidden, which makes it less high and provides more screen space for the main preview (partially visible at the bottom).]]<br />
<br />
If you use ''Single Editor Tab Mode'' ("''Preferences > General > Layout''") you can display a horizontal panel above the preview, this is called the ''Filmstrip''. It contains thumbnails of all images in the currently opened album, and is synchronized with the currently opened image so that you can use [[Keyboard Shortcuts|keyboard shortcuts]] or the previous [[Image:nav-prev.png|Open previous image icon]] and next [[Image:nav-next.png|Open next image icon]] image buttons to open the previous/next image without needing to go back to the ''[[The File Browser Tab|File Browser]]'' tab.<br />
<br />
As of RawTherapee version 4.2.10, you can hide the Filmstrip's toolbar to save screen space. There are two ways of doing this: one way just toggles the toolbar on/off without resizing the filmstrip to the new height, and the other way does the same but also automatically resizes the filmstrip's height. Both are invoked via [[Keyboard Shortcuts|keyboard shortcuts]] only. As resizing the filmstrip's height will trigger a refresh of the image preview and this might take a while if using CPU-hungry tools like noise reduction while zoomed in at 100%, the mode that doesn't resize has been implemented for users with slow machines. Users with fast machines will find the auto-resizing mode more helpful.<br />
<br />
== Monitor Profile and Soft-Proofing ==<br />
<br />
The widgets under the main preview in RawTherapee 5 allow you to apply a monitor color profile to the preview image. This enables users who have calibrated and profiled their monitors to get an instant and accurate preview of their work, whether you're staying in sRGB or working in a wide gamut. Note: OS X users are limited to sRGB and will not get an accurate preview otherwise ([https://discuss.pixls.us/t/wide-gamut-preview-in-os-x/2481 see discussion]), while users of Linux and Windows will get a correct wide-gamut preview.<br />
<br />
Go to Preferences > [[Preferences#Color_Management_Tab|Color Management]] and point the "Directory containing color profiles" to the folder into which you saved your monitor and printer ICC profile. Restart RawTherapee for the changes to take effect. Now you will be able to select your monitor's color profile in the combo-box under the preview. Use the "Relative Colorimetric" rendering intent unless you have a good reason otherwise.<br />
<br />
One can also enable soft-proofing of the preview. This will show you what your image will look like once it gets transformed by the printer profile set in Preferences > [[Preferences#Color_Management_Tab|Color Management]]. If you want to adjust an image for printing and you have an ICC profile for your printer-paper combination you could set that as your output profile, enable "Black point compensation" in Preferences so that the blackest black in your image will match the blackest black your printer-paper combination is capable of reproducing, then enable soft-proofing. You will see what your image will look like if you print it. This allows you to make adjustments and get an instant preview of the result, saving you time and ink on test prints.<br />
<br />
The icon with exclamation mark next to the soft-proofing button will gray out areas that cannot be reproduced by your printer, i.e. areas where you will loose details.<br />
<br />
You should have a calibrated and profiled monitor in order for the soft-proofing preview to be accurate.<br />
<br />
The items you see in the monitor profile combo-box (under the main preview) and in the printer profile combobox (in Preferences > [[Preferences#Color_Management_Tab|Color Management]]) are ICC files located in a folder which you can point RawTherapee to by going to "[[Preferences]] > [[Preferences#Color_Management_Tab|Color Management]] > Directory containing color profiles".</div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=Editor&diff=9834Editor2022-11-22T18:54:28Z<p>DrSlony: Background Color of the Preview</p>
<hr />
<div><div class="pagetitle">The Editor</div><br />
<br />
[[File:Rt 55 trains.png|none|frame|link=|class=heroed|The Image Editor tab in RawTherapee 5.5.]]<br />
<br />
== Introduction ==<br />
<br />
The Image Editor tab is where you tweak your photos. By default RawTherapee is in "Single Editor Tab Mode, Vertical Tabs" (SETM/VT) which is more memory-efficient and lets you use the [[Editor#The_Filmstrip|Filmstrip]] (described below). You can switch to "Multiple Editor Tabs Mode" (METM) by going to "[[Preferences#Layout|Preferences > General > Layout]]", however each Editor tab will require a specific amount of RAM relative to the image size and the tools you use, and also the Filmstrip is hidden in this mode, so we recommend you first give SETM a try.<br />
<br />
== The Preview Panel ==<br />
<br />
The central panel shows a preview of the image being edited. This preview is generated from raw data if such is available. It reflects the adjustments made by the tools in the [[Editor#Toolbox|Toolbox]]. Note that the effects of some tools are only accurately visible when you are zoomed in to 1:1 (100%) or more; these tools are marked in the interface with a "1:1" icon [[File:One-to-one-small.png|Zoom 1:1]] alongside the tool's name.<br />
<br />
When opening an image, RawTherapee loads the tool settings from the sidecar file if one exists, else it applies a default sidecar file as specified in "[[Preferences#Default_Processing_Profile|Preferences > Image Processing > Default Processing Profile]]". When you close the image (which happens automatically if you open a different image or if you close RawTherapee) the current tool settings are automatically saved to a sidecar file as specified in "[[Preferences#Processing_Profile_Handling|Preferences > Image Processing > Processing Profile Handling]]".<br />
<br />
=== Eek! My Raw Photo Looks Different than the Camera JPEG ===<br />
<br />
When opening a raw photo you may notice that it looks different from your camera's JPEG, or from what other software show when viewing the same raw photo. In some cases this difference is minute, but in other cases it could be significant - the image could be darker, lack contrast, be less sharp and more noisy. What gives?<br />
<br />
There are three things you must know first to understand what is happening here:<br />
# Your camera does not show you the real raw data when you shoot raw photos. It processes the raw image in many ways before presenting you with the histogram and the preview on your camera's display. Even if you set all the processing features which your camera's firmware allows you to tweak to their neutral, "0" positions, what you see is still not an unprocessed image. Exactly what gets applied depends on the choices made by your camera's engineers and company management, but usually this includes a custom tone curve, saturation boost, sharpening and noise reduction. Some cameras, particularly low-end ones and [http://en.wikipedia.org/wiki/Micro_Four_Thirds_system Micro Four-Thirds system], may also apply lens distortion correction to not only fix [http://en.wikipedia.org/wiki/Distortion_(optics)#Radial_distortion barrel and pincushion distortion] but also to hide dark corners caused by severe [http://en.wikipedia.org/wiki/Vignetting vignetting] or by the [https://en.wikipedia.org/wiki/Lens_hood lens hood]. Most cameras also underexpose every photo you take by anywhere from -0.3EV to -1.3EV or more, in order to gain headroom in the highlights. When your camera (or other raw editing software) processes the raw file it compensates for this by increasing exposure compensation by the same amount.<br />
# When shooting a raw photo, most cameras embed within the raw file a full-resolution JPEG image with tone curves and other adjustments applied. Some raw files contain as many as three JPEG images differing only in resolution. Most cameras offer storing photos in one of three modes: "RAW", "JPEG", or "RAW+JPEG". The embedded JPEG image discussed here is stored within the raw file even in just "RAW" mode! When you open raw files in other software, what you are usually seeing is '''not''' the raw data, but the embedded, processed JPEG image! Examples of software which are either incapable of or which in their default settings do not show you the real raw data: [http://en.wikipedia.org/wiki/IrfanView IrfanView], [http://en.wikipedia.org/wiki/XnView XnView], [http://en.wikipedia.org/wiki/Gwenview Gwenview], [http://en.wikipedia.org/wiki/Geeqie Geeqie], [http://en.wikipedia.org/wiki/Eye_of_GNOME Eye of GNOME], [http://en.wikipedia.org/wiki/F-Spot F-Spot], [http://en.wikipedia.org/wiki/Shotwell_(software) Shotwell], [http://en.wikipedia.org/wiki/GThumb gThumb], etc. It is worth mentioning at this point that if you shoot in "RAW+JPEG" mode then you could in fact be wasting space on your memory card and gaining nothing for it, as your raw files most likely already contain an embedded JPEG identical to the external one saved in "RAW+JPEG" mode.<br />
# Most raw development programs (programs which do read the real raw data instead of just reading the embedded JPEG) apply some processing to it, such as a base tone curve, even at their most neutral settings, thereby making it impossible for users to see the real, untouched contents of their raw photos. Adobe Lightroom is an example. Comparing RawTherapee's real [[Neutral]] image to a pseudo-neutral one from these other programs will expose the differences.<br />
<br />
RawTherapee, on the other hand, is capable of showing you the real raw image in the main preview, leaving the way you want this data processed up to you. When you use the "[[Neutral]]" processing profile you will see the demosaiced image with camera white balance in your working color space with no other modifications. You can even see the non-demosaiced image by setting the [[Demosaicing#Method|demosaicing method]] to "None".<br />
<br />
To provide you with a more aesthetically pleasing starting point, RawTherapee by default uses the [[Auto-Matched_Curve]] processing profile, which automatically generates a tone curve to make the tones of the raw image match those of the embedded JPEG, if one exists. If one does not exist, you can use the [[Standard_Film_Curve]] processing profile, which applies a curve which looks good in most cases. Choose the sub-type (ISO Low/Medium/High) depending on how noisy your image is.<br />
<br />
=== Scrollable Toolbars ===<br />
<br />
The toolbars above and below the main preview hold a certain number of buttons and other widgets which might not fit on lower resolution screens. {{:Scrollable Toolbar}}<br />
<br />
=== Background Color of the Preview ===<br />
<br />
[[File:Rt59 preview background all.png|left|frame]]<br />
<br />
The background color of the preview panel may be changed to allow you to better judge how the image tones will appear when the saved image is viewed on a website (or image viewer, or print) of a similar background color.<br />
<br />
This choice also applies to the cropped-off area, if the image is cropped. See "[[Preferences#Appearance|Preferences > General > Appearance > Crop mask color]]".<br />
<br />
Available options:<br />
* theme-based (see [[Preferences#Appearance|Preferences > General > Appearance]]),<br />
* black,<br />
* [https://en.wikipedia.org/wiki/Middle_gray L* middle grey],<br />
* white.<br />
<br />
=== Preview Modes ===<br />
<br />
In addition to the normal preview, RawTherapee supports a number of other preview modes to help you tweak your photos. Preview modes are controlled via buttons in the ''Editor'' toolbar or via [[Keyboard_Shortcuts | keyboard shortcuts]]. Only one preview mode can be engaged at a time.<br />
<br />
<div style="margin-left: 16px; margin-top: -1em;"><br />
{| class="RPwt-table"<br />
|+ align="bottom" | <nowiki>*</nowiki> The preview is returned to normal by deselecting any other mode.<br />
! Preview Mode<br />
! Shortcut<br />
! Button<br />
|-<br />
| style="padding:10px;" | Regular* || || [[Image:preview mode 1 regular.png]]<br />
|-<br />
| style="padding:10px;" | Red channel || align="center" | r || [[Image:preview mode 2 red.png]]<br />
|-<br />
| style="padding:10px;" | Green channel || align="center" | g || [[Image:preview mode 3 green.png]]<br />
|-<br />
| style="padding:10px;" | Blue channel || align="center" | b || [[Image:preview mode 4 blue.png]]<br />
|-<br />
| style="padding:10px;" | Luminance channel || align="center" | v || [[Image:preview mode 5 luminance.png]]<br />
|-<br />
| style="padding:10px;" | Focus Mask || align="center" | Shift+f || [[Image:preview mode 6 focus.png]]<br />
|}<br />
</div><br />
The following preview modes are currently supported:<br />
* Red channel,<br />
* Green channel,<br />
* Blue channel,<br />
* Luminosity, which is calculated as 0.299*R + 0.587*G + 0.114*B,<br />
* Focus mask, to see which areas are in focus<br />
<br />
<gallery mode="packed" caption="Preview modes" style="clear: both"><br />
Image:Preview_1_regular.jpg|Regular<br />
Image:Preview_2_red.jpg|Red<br />
Image:Preview_3_green.jpg|Green<br />
Image:Preview_4_blue.jpg|Blue<br />
Image:Preview_5_luminosity.jpg|Luminosity<br />
Image:Preview_6_focus.jpg|Focus Mask<br />
</gallery><br />
<br />
==== Red, Green, Blue and Luminosity Preview Modes ====<br />
<br />
{{:Clipping_Indication}}<br />
<br />
Preview of individual channels may be helpful when editing RGB curves, planning black/white conversion using the channel mixer, evaluating image noise, etc. Luminosity preview is helpful to instantly view the image in black and white without altering development parameters, to see which channel might be clipping or for aesthetic reasons.<br />
<br />
==== Focus Mask ====<br />
<br />
[[Image:Preview_6_focus_2.jpg|Focus mask indicating the focusing plane|thumb]]<br />
The focus mask is designed to highlight areas of the image which are in focus. Naturally, focused areas are sharper, so the sharp areas are being highlighted. The focus mask is more accurate on images with a shallow depth of field, low noise and at higher zoom levels.To improve detection accuracy for noisy images evaluate at smaller zoom, around the 10-30% range. Note that the preview is rendered more slowly when the focus mask is enabled.<br />
<br />
The current implementation analyzes the preview image which is rescaled from the original captured size. This process of rescaling reduces the noise and is helpful to identify truly sharper details rather than noise itself which may also contain micro texture. At the same time, rescaling of the original image to the preview size compresses larger scale details into a smaller size, and it may introduce aliasing artifacts, both of which could lead to false positives. You can increase your confidence by viewing the mask at various zoom levels. It is not always fault proof, but can be helpful in many cases.<br />
<br />
'''Warning''': Be sure to double-check your images if you decide to delete them based on the focus mask.<br />
<br />
=== Detail Window ===<br />
<br />
The "New detail window" button [[File:Window-add.png]], situated below the main preview next to the zoom buttons, opens a new viewport over the main preview of an adjustable size and of adjustable zoom. This lets you work on the photo zoomed-to-fit while examining several areas of interest at a 100% zoom (or even more). The benefit of using this feature is particularly important to users with slower machines, though not only them, as the zoomed-out main preview takes a shorter amount of time to update than if you were to zoom it to 100% because working at a zoom level less than 100% excludes certain slow tools, such as Noise Reduction, while the little detail windows zoomed to 100% do include all tools and are fast to update because of their small size. This allows you can use the main preview for your general exposure tweaks where it is necessary to see the whole image, and one or more detail windows to get sharpening and/or noise reduction just right.<br />
<br />
=== Preview refresh delay ===<br />
<br />
Changing any tool's parameters sends a signal for the preview image to be updated accordingly. Imagine what would happen if there was no "delay period", and you dragged, for example, the exposure compensation slider from 0.00 to +0.60. A signal would be sent to update the preview for every single change of that value - for +0.01, +0.02, ... +0.59, +0.60. Updating the preview 60 times would be completely unnecessary and actually take longer than it takes you to move the slider. This is especially true for more complicated tools, such as noise reduction, where a preview update can take even a second (depending on your CPU and preview size). The solution is for RawTherapee to wait for a very short period from the moment you stop moving a slider (you don't have to let go of it, pausing movement is enough) until the moment it sends a signal for the preview to be refreshed.<br />
<br />
We have introduced two parameters which control the length of this waiting period:<br />
; AdjusterMinDelay<br />
: Default value = 100ms.<br />
: This is used for tools with a very fast response time, for example the exposure compensation slider.<br />
; AdjusterMaxDelay<br />
: Default value = 200ms.<br />
: This is used for tools with a slow response time, for example the CIECAM02 sliders.<br />
<br />
You can adjust both of these values in the options file in the [[File_Paths|config folder]].<br />
<br />
== The Left Panel ==<br />
<br />
To the left is a panel which optionally shows the main histogram ("''Preferences > General > Layout > Histogram in left panel''"), and always shows the ''Navigator'', ''History'' and ''Snapshots''.<br />
You can hide this panel using the [[Image:panel-to-left.png|Hide left panel icon]] hide icon, or its [[Keyboard Shortcuts|keyboard shortcut]].<br />
<br />
=== Main Histogram ===<br />
<br />
[[File:Rt57 histogram wide labeled.png|none|frame|class=heroed|Histogram showing all 3 channels and luminosity.]]<br />
<br />
[[File:RT57 histogram ani.gif|frame|The histogram in RawTherapee 5.7, showing a histogram of the raw data in all three modes - linear-linear, linear-log and log-log. We can see that the raw file is not clipped.]]<br />
<br />
[[File:Rt histogram rgbindicator.png|frame|The RGB indicator shows the position in the histogram of the R, G, B and L values of the pixel your cursor is hovering over.]]<br />
<br />
A histogram in photography is a graphical representation of the number of pixels of a given value. Typically the horizontal axis represents the range of possible values while the vertical axis represents the count of pixels with that value. The axes need not be linear - RawTherapee can also scale the histogram logarithmically.<br />
<br />
Regardless of the photo's bit depth, the histogram itself has a precision of 256 sampling bins. To understand this, let us look at the example of a 16-bit image using integer precision. Its range of possible values spans from 0 to 65535 (2^16 = 65536 possible values, and since 0 is a possible minimum value then the maximum value is 65535). Drawing a histogram using 16-bit precision would mean that it would need to be 65535 pixels wide to faithfully represent the data, and no screen today is anywhere near that wide. Instead, all pixels with values from 0 to 255 (65535/256*1) are grouped into the first "bin". The second bin consists of a count of all pixels with values from 256 to 511 (65535/256*2). The third bin represents values 512 to 767 (65535/256*3). And so on until bin 256. This happens regardless of the input image's bit depth - and RawTherapee's engine uses 32-bit floating-point precision anyway.<br />
<br />
The main histogram can simultaneously show one or more of the following:<br />
* [[File:Histogram-red-on-small.svg]] the red channel,<br />
* [[File:Histogram-green-on-small.svg]] the green channel,<br />
* [[File:Histogram-blue-on-small.svg]] the blue channel,<br />
* [[File:Histogram-silver-on-small.svg]] CIELab luminance,<br />
* [[File:Histogram-gold-on-small.svg]] [http://en.wikipedia.org/wiki/Chromaticity chromaticity].<br />
* [[File:Histogram-bayer-on-small.svg]] red, green and blue channels of the source raw image before demosaicing.<br />
<br />
The histogram shows the channels listed above using the gamma-corrected output profile when the gamut button [[File:Gamut-hist.png]] is disabled (default), or using the working profile when the button is enabled. The status of this button also affects the values shown in the Navigator panel, as well as the clipped shadow [[File:Warning-shadows.png]] and [[File:Warning-highlights.png]] highlight indicators. It does not affect the raw histogram.<br />
<br />
Like water in a pipeline, image data flows through RawTherapee from the input file through various stages, most of which the user can control, to the output. The output could be the image saved in a file, or the image displayed on your screen. Each stage affects the color data. The histogram allows you to visualize this data at several stages. By default, the histogram shows color data as it will appear if you save the output image, including processing done at all intermediate stages. By enabling the gamut button [[File:Gamut-hist.png]] you can peak at the data at the early stage where it gets converted into the working space. You can even look at the raw data before any transformations or demosaicing are applied.<br />
<br />
Let's examine the large histogram example above. Though it actually shows four histograms (red, green, blue and luminance), focus on one histogram at a time. The horizontal axis represents the possible values of the histogram, where "A" are the darkest values possible, "C" the mid-tones, and "E" the brightest possible values. The position of the histogram line on the vertical axis represents how many pixels have that value. We can see that there are zero pixels in the red channel with values around "A" (from zero to very dark), because the histogram line lies right along the bottom. There is a significant number of pixels where the red channel is dark (between A and B), and a significant number where it is light (around D). Then, importantly, there is a spike at the right end of the histogram, at E - it tells us that a large number of pixels have maximal red values - they are clipped.<br />
<br />
Generally speaking, you should care when clipping occurs on skin, and not care when it's due to [https://en.wikipedia.org/wiki/Specular_highlight specular highlights]. If a histogram shows clipping, and if you care about the clipped regions, you should start by establishing where the clipping occurs. Check the raw histogram - are any channels clipped? If yes, then maybe [[Exposure#Highlight_Reconstruction|highlight reconstruction]] can help. If the raw histograms are not clipped, then all the required information is intact, and it is some stage downstream in the pipeline which causes clipping. Ensure your working profile's gamut is large enough by enabling the gamut button [[File:Gamut-hist.png]] to see histograms at the working profile stage of the pipeline. You might want to temporarily apply the [[Neutral]] profile to disable all the tools while checking, then revert. If your working space is not causing clipping (the default working space is ProPhoto and it's huge), then it's likely your adjustments which are causing clipping. Reduce exposure, go easy on the curves, use dynamic range compression if necessary.<br />
<br />
Knowing how to read a histogram is a basic and very useful skill, as it can point out issues with your image regardless of how dim or miscalibrated your monitor may be.<br />
<br />
To help you visualize the data, the histogram (as of RawTherapee 5.5) has three modes which scale the data in the x and y axes differently:<br />
* [[File:Histogram-mode-linear-small.png]] Linear-linear mode. You find gridlines at halves, quarters, eighths and sixteenths, depending on the size of the histogram.<br />
* [[File:Histogram-mode-logx-small.png]] Linear-log mode. The x-axis is linear, the y-axis and the horizontal gridlines are scaled logarithmically. The position of the gridlines still corresponds to the halves, quarters, etc.<br />
* [[File:Histogram-mode-logxy-small.png]] Log-log mode. Both the x- and y-axes are scaled logarithmically. The gridlines are not scaled logarithmically, but correspond to [https://en.wikipedia.org/wiki/Exposure_value stops] - with every gridline the value doubles, so there are lines for the values 1, 3, 7, 15, 31, 63, and 127 (<code>pow(2.0,i) - 1)</code>).<br />
<br />
When there is a disproportionately bright area relative to the rest of the image, it will show up as a spike in the histogram. If you want to show this on a histogram with a linear y axis, the spike may push the lesser values down the y-axis, making them difficult to see. Switch to one of the log modes to scale the data and help you get a better overview of all values.<br />
<br />
The histogram can be moved to the left/right panel from "''Preferences > General > Layout > Histogram in left panel''".<br />
<br />
==== Raw Histograms ====<br />
<br />
Raw files contain a dump of data captured by the sensor and quantified by the analog-to-digital converter. The raw file as a container has a bit depth of its own, typically 16-bit, while the data it contains could have a lower bit depth - typically it is 12-bit (0-4096) or 14-bit (0-16384). To display the data from a raw file as an image, one of the several key bits of information required to process the data correctly are the black and white levels. The black level is not necessarily 0, as the sensor and camera electronics produce digital noise, so the noise floor may lie for instance at 512. The white level is also not necessarily 16384; it depends on various things, and may lie for instance at 16300. For more information, see the articles [[Demosaicing]] and [[Adding Support for New Raw Formats]] (especially the header of the <code>camconst.json</code> file). The black and white level values used by RawTherapee are hierarchically set by looking in several places: in <code>dcraw.c</code>, inside the raw file's metadata, and in <code>camconst.json</code> (latter takes precedence). Furthermore, the user can tweak the raw [[Raw Black Points|black]] and [[Raw White Points|white]] levels from within RawTherapee.<br />
<br />
The raw histograms show data after black level subtraction. The right end of the histogram is anchored on the white level. The raw histograms are affected by the detected black and white levels as well as by the black and white level adjustments made by the user in RawTherapee.<br />
<br />
When examining the raw histogram, you may also want to set the demosaicing method to "none". This will reveal the sensor pattern in the preview, and also cause the [[Editor#Navigator|Navigator]] panel to show the raw RGB values of the pixel currently being hovered over. These values are affected by the detected black and white levels as well as by the black level adjustments made by the user in RawTherapee, but they are not affected by the white level adjustments ("white-point correction") made by the user in RawTherapee.<br />
<br />
=== Navigator ===<br />
<br />
The ''Navigator'' panel shows a thumbnail of the currently opened image, and RGB, HSV and Lab values of the pixel your cursor is currently hovering over.<br />
<br />
The values shown in the main histogram and Navigator panel are either those of the working profile or of the gamma-corrected output profile, depending on the state of the gamut button [[File:Gamut-hist.png]] located in the toolbar above the main preview. When the gamut button is enabled the working profile is used, otherwise the gamma-corrected output profile is used.<br />
<br />
By clicking on the values in the Navigator you can cycle between these three formats:<br />
* [0-255]<br />
* [0-1]<br />
* [%]<br />
<br />
RawTherapee 5.1 onward can show the real raw photosite values. To see them, set the Navigator to use the [0-255] range, apply the [[Neutral]] [[Sidecar_Files_-_Processing_Profiles|processing profile]], then set the [[Demosaicing]] method to "None". The Navigator will show the real raw photosite values after black level subtraction within the range of the original raw data.<br />
<br />
=== History ===<br />
<br />
The History panel contains a stack of entries which reflect each of your image editing actions. By clicking on the entries you can step back and forth through the different stages of your work.<br />
<br />
An entry is added each time you adjust a ''different'' widget - multiple edits to the same widget are stored as one entry. For example, adjusting the exposure compensation slider from "0" to "0.3" and then to "0.6" will result in one entry being stored with a final value of "0.6". Likewise, when adjusting a curve, all individual control point adjustments are grouped into one history entry. Should you wish to store the adjustments as two (or more) history entries, you will have to split them by adjusting some other widget. For example, assuming a curve is in "Film-like" mode and you want to keep to that way: adjust several control points on the curve, then toggle the curve mode from "Film-like" to "Standard" and then back to "Film-like" to create a new history entry, and then continue adjusting the curve.<br />
<br />
The history stack is not saved - it is lost as soon as you close the Editor tab. None of your adjustments are lost though, as the final state of all tools is saved in the [[Sidecar Files - Processing Profiles|sidecar file]], ready to be used the next time you open that image.<br />
<br />
=== Snapshots ===<br />
<br />
Under the ''History'' panel is a panel called ''Snapshots''. Its use is in that you can save a snapshot of the photo with all the adjustments up to that point in time, and then proceed to further modify your photo to give it a different appearance, saving new snapshots at every moment you feel you might have reached a version of your photo worth saving. Once you have two or more snapshots, you can just click on them to flip through the different versions and stick with whichever one you like best. In the future, the snapshots will be saved to the PP3 sidecar file. For now, the history and snapshots are lost when you load a new photo in the ''Image Editor'' or close RawTherapee.<br />
<br />
== The Right Panel ==<br />
<br />
To the right is a panel which optionally shows the main histogram and ''Processing Profiles'' selector ("''Preferences > General > Layout > Histogram in left panel''"), and always shows the [[Toolbox]].<br />
You can hide this panel using the [[Image:panel-to-right.png|Hide right panel icon]] hide icon, or its [[Keyboard Shortcuts|keyboard shortcut]].<br />
<br />
=== Processing Profile Selector ===<br />
<br />
The Processing Profiles panel allows you to apply, save, load, copy and paste processing profiles, partially or in full.<br />
<br />
[[File:Processing-profiles-selector.png|center|frame]]<br />
<br />
Read the [[Sidecar_Files_-_Processing_Profiles | Sidecar Files / Processing Profiles]] page for more information.<br />
<br />
=== Toolbox ===<br />
<br />
The ''Toolbox'', in the right panel, contains all the tools you use to tweak your photos. Each tool has its own RawPedia article.<br />
<br />
== Editor Tab Modes ==<br />
<br />
RawTherapee allows you to work on photos in two modes:<br />
* ''Single Editor Tab Mode'' (SETM), where you work only on one photo at a time, and each photo is opened in the same ''Editor'' tab. There is a horizontal panel called the ''[[The_Image_Editor_Tab#The_Filmstrip | Filmstrip]]'' at the top of the ''[[The_Image_Editor_Tab#The_Filmstrip | Editor]]'' tab showing the rest of the photos in that folder for easy access. There are ''Previous Image'' and ''Next Image'' [[File:Nav-prev.png]] [[File:Nav-next.png]] buttons in the bottom toolbar (and [[Keyboard Shortcuts | keyboard shortcuts]] for them) to switch to the previous/next image.<br />
* ''Multiple Editor Tabs Mode'' (METM), where each photo is opened in its own ''[[The_Image_Editor_Tab#The_Filmstrip | Editor]]'' tab. The ''[[The_Image_Editor_Tab#The_Filmstrip | Filmstrip]]'' is hidden in this mode and there are no previous/next buttons. Having multiple photos opened at the same time requires more RAM.<br />
<br />
Try both modes and see which one suits you best. To do that, click on the ''Preferences'' icon [[image:preferences.png|Preferences icon]] in the bottom-left or top-right corner of the RT window, choose "''General > Layout''" and set ''Editor Layout'' to your preferred choice.<br />
<br />
Use this ''Preferences'' window to select a different language for the user interface, to choose a different color theme, change the font size, etc.<br />
<br />
It is also possible to start RawTherapee in no-File-Browser-mode (without the ''File Browser'' tab) by specifying RawTherapee to open an image from your operating system's file browser (in other words, right-click on a photo and select "''Open With > RawTherapee''"), or by using the image filename as an argument when starting RawTherapee from the command line (<code>rawtherapee /path/to/some/photo.raw</code>). This mode was introduced for people with little RAM as not having a ''File Browser'' tab means RawTherapee uses a little less memory, however in practice the amount of memory saved is little and the usability cost outweighs the little benefit, so it is likely to be removed in the future (see [https://code.google.com/p/rawtherapee/issues/detail?id=2254 issue 2254]).<br />
<br />
== The Filmstrip ==<br />
<br />
[[File:Rt filmstrip 21 toolbar-visible.jpg|none|frame|class=heroed|RawTherapee-4.2 showing the Filmstrip with the toolbar visible, which takes up more screen space but lets you easily label, rate and filter the visible thumbnails.]]<br />
[[File:Rt filmstrip 21 toolbar-hidden.jpg|none|frame|class=heroed|RawTherapee-4.2 showing the Filmstrip with the toolbar hidden, which makes it less high and provides more screen space for the main preview (partially visible at the bottom).]]<br />
<br />
If you use ''Single Editor Tab Mode'' ("''Preferences > General > Layout''") you can display a horizontal panel above the preview, this is called the ''Filmstrip''. It contains thumbnails of all images in the currently opened album, and is synchronized with the currently opened image so that you can use [[Keyboard Shortcuts|keyboard shortcuts]] or the previous [[Image:nav-prev.png|Open previous image icon]] and next [[Image:nav-next.png|Open next image icon]] image buttons to open the previous/next image without needing to go back to the ''[[The File Browser Tab|File Browser]]'' tab.<br />
<br />
As of RawTherapee version 4.2.10, you can hide the Filmstrip's toolbar to save screen space. There are two ways of doing this: one way just toggles the toolbar on/off without resizing the filmstrip to the new height, and the other way does the same but also automatically resizes the filmstrip's height. Both are invoked via [[Keyboard Shortcuts|keyboard shortcuts]] only. As resizing the filmstrip's height will trigger a refresh of the image preview and this might take a while if using CPU-hungry tools like noise reduction while zoomed in at 100%, the mode that doesn't resize has been implemented for users with slow machines. Users with fast machines will find the auto-resizing mode more helpful.<br />
<br />
== Monitor Profile and Soft-Proofing ==<br />
<br />
The widgets under the main preview in RawTherapee 5 allow you to apply a monitor color profile to the preview image. This enables users who have calibrated and profiled their monitors to get an instant and accurate preview of their work, whether you're staying in sRGB or working in a wide gamut. Note: OS X users are limited to sRGB and will not get an accurate preview otherwise ([https://discuss.pixls.us/t/wide-gamut-preview-in-os-x/2481 see discussion]), while users of Linux and Windows will get a correct wide-gamut preview.<br />
<br />
Go to Preferences > [[Preferences#Color_Management_Tab|Color Management]] and point the "Directory containing color profiles" to the folder into which you saved your monitor and printer ICC profile. Restart RawTherapee for the changes to take effect. Now you will be able to select your monitor's color profile in the combo-box under the preview. Use the "Relative Colorimetric" rendering intent unless you have a good reason otherwise.<br />
<br />
One can also enable soft-proofing of the preview. This will show you what your image will look like once it gets transformed by the printer profile set in Preferences > [[Preferences#Color_Management_Tab|Color Management]]. If you want to adjust an image for printing and you have an ICC profile for your printer-paper combination you could set that as your output profile, enable "Black point compensation" in Preferences so that the blackest black in your image will match the blackest black your printer-paper combination is capable of reproducing, then enable soft-proofing. You will see what your image will look like if you print it. This allows you to make adjustments and get an instant preview of the result, saving you time and ink on test prints.<br />
<br />
The icon with exclamation mark next to the soft-proofing button will gray out areas that cannot be reproduced by your printer, i.e. areas where you will loose details.<br />
<br />
You should have a calibrated and profiled monitor in order for the soft-proofing preview to be accurate.<br />
<br />
The items you see in the monitor profile combo-box (under the main preview) and in the printer profile combobox (in Preferences > [[Preferences#Color_Management_Tab|Color Management]]) are ICC files located in a folder which you can point RawTherapee to by going to "[[Preferences]] > [[Preferences#Color_Management_Tab|Color Management]] > Directory containing color profiles".</div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=File:Rt59_preview_mask_all.png&diff=9833File:Rt59 preview mask all.png2022-11-22T18:23:32Z<p>DrSlony: </p>
<hr />
<div></div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=File:Rt59_preview_channel_all.png&diff=9832File:Rt59 preview channel all.png2022-11-22T18:23:23Z<p>DrSlony: </p>
<hr />
<div></div>DrSlonyhttp://rawpedia.rawtherapee.com/index.php?title=File:Rt59_preview_background_all.png&diff=9831File:Rt59 preview background all.png2022-11-22T18:23:11Z<p>DrSlony: </p>
<hr />
<div></div>DrSlony