Kontrolliere wie Bilder bearbeitet werden.

Bildverarbeitung

always use LittleCMS 2 to apply output color profile
If this option is activated, Ansel will use the LittleCMS 2 system library to apply the output color profile instead of its own internal routines. This is significantly slower than the default but might give more accurate results in some cases.

Falls das gegebene ICC-Profil LUT-basiert ist oder eine LUT und eine Matrix enthält, dann wird Ansel LittleCMS 2 nutzen, um die Farben zu rendern, unabhängig von den Werten dieses Parameters (Standard ausgeschaltet).

Pixel-Interpolation (Verformung)
Der Pixel-Interpolator für Rotation, Objektivkorrektur, Verflüssigen, Zuschneiden und endgültiges Skalieren.

Wann immer wir ein Bild skalieren oder verzerren, müssen wir einen Pixel-Interpolations-Algorithmus wählen (für Details siehe Wikipedia ). Für Verzerren-Module bietet Ansel bilineare, bikubische oder lanczos2. Generell ist bikubisch eine sichere Option für die meisten Fälle und ist der Standard.

Pixel-Interpolator (Skalieren)
Der Pixel-Interpolator für das Skalieren. Es werden die gleichen Optionen zur Verfügung wie für die Verzerren-Module, mit zusätzlich lanczos3.

lanczos3 kann ein Überschießen der Pixel verursachen, was zu Artefakten führt, aber manchmal eine knackigeres Erscheinen ergibt. Diese Option gibt es deshalb nur für Transformations (Skalierungs) Algorithmen und ist der Standard.

3D lut root folder
Define the root folder (and sub-folders) containing Lut files used by the lut 3D module
Finde monochrome Voranzeigebilder
Schalte diese Option ein, um die Bilder zu analysieren und bezeichne jene, die monochrom sind mit dem Tag darkroom|mode|monochrome. Die Analyse basiert auf der Voranzeige, die importierten Bild eingebettet ist. Das steht für einen komfortableren Arbeitsablauf, wenn du mit monochromen Bildern arbeitest, aber es wird den Import-Prozess verlangsamen, also ist diese Möglichkeit standardmäßig ausgeschaltet.

CPU, GPU, Memory

Ansel resources
Choose how much of your system and graphics card (GPU) memory will be used by Ansel. Four options are provided by default:
  • small takes roughly 20% of your system memory and 40% of your GPU memory. This might be acceptable on very large systems, especially if you’re not exporting images. Mostly, though, this can only be recommended if you are using a lot of other demanding applications at the same time as Ansel.
  • default takes roughly 60% of your system memory and 70% of your GPU memory. This mode is recommended if you’re not exporting a lot of images, have at least 16Gb of system memory and 4Gb of GPU memory, and also are running a lot of other application at the same time as Ansel.
  • large takes roughly 75% of your system memory and 90% of your GPU memory. This is the best option if you are only using Ansel on your system and/or are exporting a lot of images.
  • unrestricted is not generally recommended. In this mode Ansel may attempt to use more memory than your system has available. This might be possible if your system uses swapping when all of its system memory is taken, but it could lead to system instability. Use this mode with care, only when exporting very large images that Ansel cannot otherwise handle.
See the memory & performance tuning section for more information.
Festplatten-Backend für den Thumbnail-Cache aktivieren
Wenn aktiviert, speichert Ansel alle Thumbnails auf der Festplatte als sekundären Cache und hält so die Thumbnails für den Fall zugänglich, falls diese aus dem primären Cache gelöscht werden. Dies erfordert mehr Speicherplatz auf der Festplatte, beschleunigt aber die Leuchttisch-Ansicht, da es die erneute Bearbeitung von Miniaturansichten vermeidet (standardmäßig aktiviert).
Disk-Backend für vollen Vorschau Cache aktivieren
Wenn aktiviert, schreibt Ansel eine vollständige Vorschau auf die Festplatte (.cache/Ansel/), wenn sie aus dem Speicher-Cache entfernt wird. Beachten Sie, dass dies viel Speicherplatz beanspruchen kann (mehrere Gigabyte für 20k Bilder) und Ansel wird niemals zwischengespeicherte Bilder löschen. Es ist jedoch sicher, diese manuell zu löschen, wenn Sie möchten. Die Leistung des Leuchttisches wird stark erhöht, wenn das Bild im vollen Vorschaumodus vergrössert wird (Standard aus).
activate OpenCL support
Your GPU can be used by Ansel to significantly speed up processing. The OpenCL interface requires suitable hardware and matching OpenCL drivers on your system. If one of those is not found the option is grayed out. Can be switched on and off at any time and takes immediate effect (default on).
OpenCL scheduling profile
Defines how preview and full pixelpipe tasks are scheduled on OpenCL enabled systems:
  • default: the GPU processes the center view pixelpipe; the CPU processes the preview pipe,
  • very fast GPU: both pixelpipes are processed sequentially on the GPU.
  • multiple GPUs: both pixelpipes are processed in parallel on different GPUs – see the multiple devices section for more information,
tune OpenCL performance
Defines how Ansel will attempt to tune OpenCL performance for your system. The following options are provided (default nothing):
  • nothing: do not attempt to tune OpenCL performance.
  • memory size: this parameter currently (by default) applies a fixed 400MB headroom to all devices and assumes the remainder (total device memory less 400MB) is available for OpenCL module processing. You can also choose to amend this value or have Ansel attempt to auto-detect available memory by changing a parameter in your Anselrc file. Please see the memory & performance tuning section for more details. If you choose to enable auto-detection, switching this parameter off and on again will force a re-detection at the next pipe run.
  • memory transfer: when Ansel needs more memory than it has available, it breaks your images into tiles, which are processed separately. When tiling, Ansel frequently needs to transfer data between system and GPU memory. This option tells Ansel to use a special copy mode (pinned memory transfer), which can be faster, but can also require more memory on some devices. On other devices it might degrade performance. There is no safe general way to predict how this option will function on a given device so you will have to test it for yourself. If you have multiple devices, you can switch pinned memory transfer on or off on a “per device” basis by directly editing your Anselrc file.
  • memory size and transfer: use both tuning mechanisms.
See the memory & performance tuning section for more information.

Libraw

Ansel uses the Rawspeed library by default to decode raw image files. Rawspeed is flawlessly integrated in Ansel, but does not support Canon .CR3 files yet. For this reason, a basic support of Libraw has been implemented such that owners of recent Canon cameras can still decode their files. Libraw also tends to support new formats faster than Rawspeed.

The options of this section allow users to force the use of Libraw for any picture they want, using rules based on file extension and camera/vendor EXIF metadata. The feature is brittle and unsafe in general because we don’t check and sanitize every possible flavour of encoding.

Supported files
  • Canon .CR3
Files that seem to be working
  • Olympus .ORF
  • Hasselblad .3FR
  • Nikon .NEF non-compressed
Files that definitely don’t work and make the software crash
  • Nikon sRAW and compressed .NEF
  • Phase One .IIQ
Raw file extensions to load through Libraw
case-insensitive, coma-separated list of the file extensions. Default : cr3.
Camera models to load through Libraw
case-insensitive, coma-separated list of the camera models as they appear in the Display metadata module, under the model field. You may have to enable this field using the preferences of the module if it does not appear in the widget.
Camera makers to load through Libraw
case-insensitive, coma-separated list of the camera manufacturers as they appear in the Display metadata module, under the maker field. You may have to enable this field using the preferences of the module if it does not appear in the widget.

To debug this feature : 

  1. Start Ansel in command line using ansel -d imageio. For each loaded image, it will tell which library was used to decode it,
  2. If the settings you input make the software crash at startup, remove the libraw/extensions, libraw/models, libraw/makers configuration keys in the anselrc configuration file, located in ~./config/ansel folder on Linux and Mac, or APPDATA\.config\ansel on Windows.