We’re putting the finishing touches on RawTherapee 5.12. It should be ready in about a month. Here’s a preview of what you can expect in the release.
Raw dehaze: Automatically adjusts the raw black points to reduce haze. This makes use of the “poor man dehaze” experiments seen in this topic: Call for example raw files.
Framing: Adds a solid color frame/border around the image at the time of export.
Support for demosaiced floating-point DNGs.
Abstract Profile Contrast Enhancement: A sub-tool of Abstract Profile that offers an easy way to add local contrast.
Selective Editing Color Appearance tone mapper enhancements: Additional options for the RGB channel Slope tone mapper and a new Sigmoid based tone mapper.
Improved recognition of Sony lenses.
Generalized Hyperbolic Stretch: A new global tone mapper available in Selective Editing. See this topic for more information: Generalized Hyperbolic Stretch.
Translations: New Ukrainian (Українська) translation and updates to the Simplified Chinese (简体中文) translation.
We want to make sure 5.12 works well for everyone. You can help us achieve this by lending a hand in any of these areas:
Camera support: Have a camera that isn’t fully supported? Let us know and provide sample images. We may be able to fix the following issues before the release: magenta color-cast especially in the shadows (black level too low), clipped shadows and green color cast (black level too high), very dull colors (missing color matrix), too bright with clipped highlights (white level too low), magenta highlights (white level too high), black bar(s) along the edges (wrong raw crop), or parts of the image cropped away (wrong raw crop). If you are experiencing other issues, you can still let us know! If we can’t fix it before the release, we will try to in the next one. Refer to Adding Support for New Raw Formats - RawPedia for more details about adding camera support.
Translations: There’s still time to contribute translations. RawTherapee has been translated to many languages, but only a few have been updated recently. Small contributions still help. RawPedia has details on how to contribute: Translating RawTherapee - RawPedia.
Bug reports: Grab a development build. Find the ones that start with “RawTherapee_dev_” here. Report any issues you find. We are especially interested in so-called “regressions” — problems with things that used to work without issue. The official method of reporting bugs is here: How to write useful bug reports - RawPedia. For the purpose of the 5.12 release, you may report bugs here if it’s more convenient.
Sounds like we have yet another slew of amazing new tools and features to look forward to. As always, my humble appreciation and admiration goes out to all those who work so passionately on this incredible project.
I downloaded the AppImage, but I get this error after integration and start:
(Manjaro 6.4.8, Kernel 6.14.0-1, fuse 3.16.2-1)
fuse: memory allocation failed
squashfuse 0.5.2 (c) 2012 Dave Vasilevsky
Usage: squashfuse [options] ARCHIVE MOUNTPOINT
(null) options:
-o offset=N offset N bytes into ARCHIVE to mount
-o subdir=PATH mount subdirectory PATH of ARCHIVE
-o notify_pipe=PATH named pipe that will receive 's' (success)
or 'f' (failure) when the mountpoint is ready
-o timeout=N idle N seconds for automatic unmount
-o uid=N set file owner to uid N
-o gid=N set file group to gid N
FUSE options:
-h --help print help
-V --version print version
-d -o debug enable debug output (implies -f)
-f foreground operation
-s disable multi-threaded operation
-o clone_fd use separate fuse device fd for each thread
(may improve performance)
-o max_idle_threads the maximum number of idle worker threads
allowed (default: -1)
-o max_threads the maximum number of worker threads
allowed (default: 10)
fuse: memory allocation failed
squashfuse 0.5.2 (c) 2012 Dave Vasilevsky
Usage: squashfuse [options] ARCHIVE MOUNTPOINT
(null) options:
-o offset=N offset N bytes into ARCHIVE to mount
-o subdir=PATH mount subdirectory PATH of ARCHIVE
-o notify_pipe=PATH named pipe that will receive 's' (success)
or 'f' (failure) when the mountpoint is ready
-o timeout=N idle N seconds for automatic unmount
-o uid=N set file owner to uid N
-o gid=N set file group to gid N
FUSE options:
-h --help print help
-V --version print version
-d -o debug enable debug output (implies -f)
-f foreground operation
-s disable multi-threaded operation
-o clone_fd use separate fuse device fd for each thread
(may improve performance)
-o max_idle_threads the maximum number of idle worker threads
allowed (default: -1)
-o max_threads the maximum number of worker threads
allowed (default: 10)
squashfuse 0.5.2 (c) 2012 Dave Vasilevsky
Usage: squashfuse [options] ARCHIVE MOUNTPOINT
(null) options:
-o offset=N offset N bytes into ARCHIVE to mount
-o subdir=PATH mount subdirectory PATH of ARCHIVE
-o notify_pipe=PATH named pipe that will receive 's' (success)
or 'f' (failure) when the mountpoint is ready
-o timeout=N idle N seconds for automatic unmount
-o uid=N set file owner to uid N
-o gid=N set file group to gid N
FUSE options:
-h --help print help
-V --version print version
-d -o debug enable debug output (implies -f)
-f foreground operation
-s disable multi-threaded operation
-o clone_fd use separate fuse device fd for each thread
(may improve performance)
-o max_idle_threads the maximum number of idle worker threads
allowed (default: -1)
-o max_threads the maximum number of worker threads
allowed (default: 10)
Can't open squashfs image: Bad address
Cannot mount AppImage, please check your FUSE setup.
You might still be able to extract the contents of this AppImage
if you run it with the --appimage-extract option.
See https://github.com/AppImage/AppImageKit/wiki/FUSE
for more information
execv error: No such file or directory
Hi Paul. At this time, there is no preview for the framing tool. The frame is only added at the time of export.
Hi Kurt. Does this happen to other AppImages? How much free RAM do you have? I see that some people have problem with AppImages (in general, not RawTherapee) when AppImageLauncher is installed.
I just tested with RT…ghs_release.AppImage from Jan22. This worked. It was the first time that an image produced this error message.
And: 10GB free RAM.
Paul, you’re right, there are messages in history (and labels) where 5.11 appears. Why?
There are two reasons for this in Color Appearance (CAM16 & JzCzHz).
First reason:
Compatibility - if a user has used the ‘Sigmoid Q’ functions included in the CAM16 loop, ‘Log encoding Q’ included in the Cam16 loop, or ‘Sigmoid Jz’ in 5.11, the user must restore their settings. But with 5.12 I change the algorithm for Sigmoid.
I introduced a version of ‘Sigmoid’ in 5.12 that is similar to Darktable’s (with some modifications, however). It is incompatible - even though the principle is the same with version 5.11.
This 5.12 version of Sigmoid is still present in “Source Data Adjustments > Tone Mapping Operators” based on RGB data ‘Sigmoid based’, but also, depending on the case, in the CAM16 loop, based on Brightness Q, ‘Sigmoid Q’. The results are obviously different. You’ll also find the change in JzCzHz, where ‘Sigmoid Jz’ (version 5.12) replaces ‘Sigmoid Jz’ (version 5.11) with others sliders.
Second reason:
In addition to compatibility requirements, I chose to allow the user to choose between the two types of algorithms via the “Tone Mapping Operators Q(CAM16) & J(Jz)” menu, just below the CAM Model selection (5.12 or 5.11).
There’s nothing to prevent a user from “mixing” the two, creating two Spots, if they wish.
