<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Special Topics on darktable 5.8 user manual</title>
    <link>https://docs.darktable.org/usermanual/5.8/en/special-topics/</link>
    <description>Recent content in Special Topics on darktable 5.8 user manual</description>
    <generator>Hugo</generator>
    <language>en</language>
    <atom:link href="https://docs.darktable.org/usermanual/5.8/en/special-topics/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>memory &amp; performance tuning</title>
      <link>https://docs.darktable.org/usermanual/5.8/en/special-topics/mem-performance/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.darktable.org/usermanual/5.8/en/special-topics/mem-performance/</guid>
      <description>&lt;h1 id=&#34;memory-requirements&#34;&gt;&lt;a class=&#34;dt-anchor&#34; href=&#34;#memory-requirements&#34; aria-label=&#34;Link to this section&#34;&gt;#&lt;/a&gt;memory requirements&lt;/h1&gt;&#xA;&lt;p&gt;Processing a Raw image in darktable requires a great deal of system memory. A simple calculation makes this clear: For a 20 megapixel image, darktable requires a 4x32-bit floating point cell to store each pixel, meaning that each full image of this size will require approximately 300MB of memory just to store the image data. In order to actually process this image through a given module, darktable needs at least two buffers (input and output) of this size, with more complex modules potentially requiring several additional buffers for intermediate data. Without further optimization, anything between 600MB and 3GB of memory might be required to store and process image data as the pixelpipe executes. On top of this is darktable&amp;rsquo;s code segment, the code and data of any dynamically-linked system libraries, as well as further buffers that darktable uses to store intermediate states (cache) for quick access during interactive work.&lt;/p&gt;</description>
    </item>
    <item>
      <title>variables</title>
      <link>https://docs.darktable.org/usermanual/5.8/en/special-topics/variables/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.darktable.org/usermanual/5.8/en/special-topics/variables/</guid>
      <description>&lt;p&gt;darktable supports variable substitution in a number of modules and preference settings. For example:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Defining file names in the &lt;a href=&#34;https://docs.darktable.org/usermanual/5.8/en/module-reference/utility-modules/shared/export/&#34;&gt;export&lt;/a&gt; module&lt;/li&gt;&#xA;&lt;li&gt;Displaying image information in the darkroom&amp;rsquo;s &lt;a href=&#34;https://docs.darktable.org/usermanual/5.8/en/module-reference/utility-modules/darkroom/image-info-line/&#34;&gt;image information line&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;Displaying image information in the lighttable&amp;rsquo;s overlays and tooltips (see &lt;a href=&#34;https://docs.darktable.org/usermanual/5.8/en/preferences-settings/lighttable/&#34;&gt;preferences &amp;gt; lighttable&lt;/a&gt;)&lt;/li&gt;&#xA;&lt;li&gt;Placing text on an image in the &lt;a href=&#34;https://docs.darktable.org/usermanual/5.8/en/module-reference/processing-modules/watermark/&#34;&gt;&lt;em&gt;watermark&lt;/em&gt;&lt;/a&gt; processing module&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h1 id=&#34;available-variables&#34;&gt;&lt;a class=&#34;dt-anchor&#34; href=&#34;#available-variables&#34; aria-label=&#34;Link to this section&#34;&gt;#&lt;/a&gt;available variables&lt;/h1&gt;&#xA;&lt;p&gt;The following variables are available, though they may not all be applicable in every context:&lt;/p&gt;</description>
    </item>
    <item>
      <title>darktable&#39;s color pipeline</title>
      <link>https://docs.darktable.org/usermanual/5.8/en/special-topics/color-pipeline/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.darktable.org/usermanual/5.8/en/special-topics/color-pipeline/</guid>
      <description>&lt;p&gt;Most image processing applications come from the 1990s and/or inherit a 1990s workflow. These applications processed images encoded with 8 bit unsigned integers because it was more memory- and computationally-efficient. However, due to the use of an integer format (which implies rounding errors) they had to apply a &amp;ldquo;gamma&amp;rdquo; (essentially a transfer function applying a power 1/2.2 or 1/2.4 to encode the RGB values) and increase the bit-depth in the low-lights in order to reduce rounding errors there (humans are very sensitive to low-light details). The 8 bit integer formats are also technically limited to the 0-255 range. Anything outside of this range overflows and is clipped to the nearest bound.&lt;/p&gt;</description>
    </item>
    <item>
      <title>midi device support</title>
      <link>https://docs.darktable.org/usermanual/5.8/en/special-topics/midi-device-support/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.darktable.org/usermanual/5.8/en/special-topics/midi-device-support/</guid>
      <description>&lt;h1 id=&#34;introduction&#34;&gt;&lt;a class=&#34;dt-anchor&#34; href=&#34;#introduction&#34; aria-label=&#34;Link to this section&#34;&gt;#&lt;/a&gt;introduction&lt;/h1&gt;&#xA;&lt;p&gt;MIDI is a communication protocol used by many electronic musical instruments (&amp;ldquo;pianos&amp;rdquo;), digital audio studio equipment (&amp;ldquo;control surfaces&amp;rdquo;) and even dedicated &amp;ldquo;photo editing keyboards&amp;rdquo; like the Loupedeck/Loupedeck+ (but not their later products). Such devices commonly feature sets of keys/buttons and sometimes encoders (knobs/rotors) and faders (sliders). Buttons sometimes feature lights, which makes them ideal for toggling features in darktable, because the lights can reflect the current (on/off) status. Encoders and faders are ideal for use with on-screen sliders in processing modules. They can be &amp;ldquo;endless&amp;rdquo; (without a start/end point and without any markings on the knob) allowing greater than 360 degrees rotation, and they may be motorized. This is helpful when switching between images or points in the editing history since the &amp;ldquo;physical&amp;rdquo; position of the encoders/faders always corresponds to the on-screen position. You may also find a ring of LEDs around an encoder that indicates its current value.&lt;/p&gt;</description>
    </item>
    <item>
      <title>using a test environment</title>
      <link>https://docs.darktable.org/usermanual/5.8/en/special-topics/test-environment/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.darktable.org/usermanual/5.8/en/special-topics/test-environment/</guid>
      <description>&lt;p&gt;To run multiple installations of darktable on your computer, for example to try out a &lt;a href=&#34;https://github.com/darktable-org/darktable/releases/nightly&#34; target=&#34;_blank&#34;&gt;nightly build&lt;/a&gt;, you can give each installation its own configuration without affecting the others.&lt;/p&gt;&#xA;&lt;p&gt;Three steps are needed:&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;Install the additional version of darktable without overwriting the existing installation.&lt;/li&gt;&#xA;&lt;li&gt;Give it its own configuration directory.&lt;/li&gt;&#xA;&lt;li&gt;Make sure it doesn&amp;rsquo;t touch edits created by other installations.&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;hr&gt;&#xA;&lt;p&gt;Note: It is possible to affect your main installation if you make mistakes in separating your testing setup. Before starting off, make sure to backup your &lt;a href=&#34;https://docs.darktable.org/usermanual/5.8/en/preferences-settings/config-directory/&#34;&gt;configuration directory&lt;/a&gt; and consider setting up a regular backup schedule of the configuration directory.&lt;/p&gt;</description>
    </item>
    <item>
      <title>using multiple computers</title>
      <link>https://docs.darktable.org/usermanual/5.8/en/special-topics/multiple-computers/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.darktable.org/usermanual/5.8/en/special-topics/multiple-computers/</guid>
      <description>&lt;p&gt;Editing the same photos from multiple computers requires some setup as darktable has no dedicated function for sharing its database across computers.&lt;/p&gt;&#xA;&lt;p&gt;The &lt;a href=&#34;https://docs.darktable.org/usermanual/5.8/en/overview/sidecar-files/local-copies/&#34;&gt;local copies&lt;/a&gt; feature is the included solution for &amp;ldquo;editing on the road&amp;rdquo; and could be used if your files live on a NAS or external storage.&lt;/p&gt;&#xA;&lt;h2 id=&#34;general-considerations&#34;&gt;&lt;a class=&#34;dt-anchor&#34; href=&#34;#general-considerations&#34; aria-label=&#34;Link to this section&#34;&gt;#&lt;/a&gt;General considerations&lt;/h2&gt;&#xA;&lt;p&gt;Multiple machines are not natively supported. darktable assumes one local database per installation; there is no built-in functionality for resolving edit-conflicts.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
