RawTherapee 5.13 Release Candidate 1

Hello RawTherapee users!

It has been over a year since version 5.12 was released. Fortunately, 5.13 is almost ready. Just as we have done in the past, we have prepared a release candidate for all of you to try before making the actual release. The goal is to ensure RawTherapee runs smoothly on all supported systems.

Please help us out by downloading the release candidate for your system and giving it a test run. Let us know what operating system and CPU you have and whether RawTherapee works fine. If you encounter an issue, you can report it here or at the official issue tracker on GitHub. See the instructions on how to file a good bug report here.

This release will be the first one to feature official ARM builds for Windows and Linux (macOS builds are already ARM-compatible). If you have an ARM computer running Windows or Linux, we would love to hear if the ARM builds work well for you.


Download links:


For a list of new features and enhancements since 5.12, see the release notes.

* The macOS build is not exactly the release candidate, but contains an important bug fix. It is provided by @HIRAM.

14 Likes

I was able to run the Appimage on Ubuntu 24.04.4 (16Gb ram) several times over the morning (albeit with some issues) but now it simply crashes on startup. This may be something to do with my system because a self-compiled version behaved similarly. 5.12 runs without any problems.
The issues encountered with the AppImage when I could get it to run were as follows:

  1. Slow to react on startup (system message asking me if I want to wait or force quit)
  2. the Straighten/fine rotation tool seemed to be broken. When I started drawing the horizontal line the tool icon turned into a hand icon and started panning the image. The image also zoomed randomly to 100% on several occasions while trying to draw the line.
  3. Color Appearance & Lighting
    The new R,G,B Brightness curves invariably produce artifacts and should be disabled perhaps until the next release?
1 Like

Just a quick reaction to @Wayne_Sutton.

I run the RC1 AppImage on Xubuntu 26.04 with 8GB RAM.

  • No slow startup
  • Straighten tool works for me, no random zoom to 100%.
  • I don’t see any artifacts when using those new RGB Brightness curves.
2 Likes

Thanks Paul, looks like the startup crash is something to do with my system in that case.

RC1 works like a charm under Debian 13 with 8GB RAM.

2 Likes

I have managed to get the self-compiled version working again after doing a fresh compile. The 5.12 Appimage also continues to work OK as do other Appimages but I still have the same problem with RC 5.13.

As far as the other two issues are concerned:

  1. The problem with the Straighten/fine rotation tool seems to depend on how you drag the icon once you’ve clicked on the starting point. If you drag it off at an angle away from the horizontal and bring it down (or up) to the endpoint, it works OK. If however you drag it almost horizontally, that’s when the icon changes to the hand icon and the image will pan and zoom, seemingly randomly, to 100%
  2. The brightness-curve artifacts depend on the image and the editing but here are two crops using a neutral profile and no editing apart from a slight increase in the mid-tone brightness of the green channel in the second image.


Hello Wayne, I can’t reproduce 1) and 2) with the AppImage RT 5.13 RC1.

1 Like

Hi Paul,
thanks for checking. I’ve since tried the Appimage on an identical hardware setup running Ubuntu 22.04 LTS with no problems for either 1 or 2. I then fired up my 24.04 LTS machine and loaded the Appimage. It works fine the first time but if I close and reopen it, it crashes on start up. Restarting the machine produces the same result i.e. works the first time and then crashes if I close and reopen the Appimage. Everything seems to point to a problem with my installation.

Running the Appimage from the terminal gives the following:

$ /home/wayne/AppImages/RawTherapee_5.13-rc1_x86_64_release.AppImage
/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_task_set_static_name
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_task_set_static_name
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgioremote-volume-monitor.so
/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_task_set_static_name
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgioremote-volume-monitor.so
/usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so: undefined symbol: g_task_set_static_name
Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
no mmap /media/wayne/My Passport/ImageProcessing/TEST/D75_7687.NEF
no mmap /media/wayne/My Passport/ImageProcessing/TEST/D75_7687.NEF
[appimagelauncher-binfmt-bypass/lib] ERROR: child exited with code 11

I’m way out of my depth here so if anyone has any suggestions it would be appreciated.

@Wayne_Sutton

I just tested it on Windows 11 (compiled version), and everything seems to be working normally. But that doesn’t prove anything at all.
The tests I ran (not these specific ones) - back when my grandson was here with a prototype of Ubuntu 26.04 and a Ryzen processor - lead me to believe that in certain parts of the code (where??), some instructions are sensitive to the processor type (specifically its precision) and the libraries involved. The changes I made fixed the issue on his machine (which had been experiencing random crashes).
Pull Request 7629

Commit 752df61

But perhaps Ciecam also needs to be modified, as I had proposed here
PR 7700

But perhaps that’s not it…
I’m going to test it on Ubuntu 24.04 LTS.

I just test on Ubuntu24.04.4LTS Linux 6.17.0-35-generic: no problems…
But that proves absolutely nothing. Your machine might not have any problems at all… (I’m talking about the hardware).

Jacques

1 Like

I’m running RT RawTherapee_5.13-rc1_x86_64_release.AppImage on OpenSuse Tumbleweed. It’s working fine, but I’m struggling with synchronization of metadata in image / xmp sidecar. This example of 2 pictures is about rating/ rank:

==> starting point, 2 pictures, metadata for tif embedded, for Raw in xmp sidecar

exiftool -xmp:Rating *.tif *.xmp; grep Rank *.pp3
======== Pic-2.tif
Rating : 1
======== Pic-1.ARW.xmp
Rating : 1
2 image files read
grep: *.pp3: Datei oder Verzeichnis nicht gefunden

==> RT shows correct 1 star rating
==> Changed rating to 2 stars with RT

xiftool -xmp:Rating *.tif *.xmp; grep Rank *.pp3
======== Pic-2.tif
Rating : 1
======== Pic-1.ARW.xmp
Rating : 1
2 image files read
Pic-1.ARW.pp3:Rank=2
Pic-2.tif.pp3:Rank=2

With the given setting I would expect metadata to be the same.

Does anybody have problem adding tools to local adjustment spots? I’m using 5.13 RC1 with my Simplified Chinese translation and can’t add: GHS (which I noticed has changed to Equalization and pre tone-mapping, will update it), é²œę˜Žåŗ¦&å†·ęš–(Vibrance & Cool/Warm), å±€éƒØåå·®&å°ę³¢(Local Contrast & Wavelets). I switched to Japanese and can’t add one thing at all. I’m assuming there is something wrong on my side and will test the zip version, but it’s certainly weird.

@syyrmb

For me, there are no issues with either configuration (Windows 11 and Ubuntu 24.04),

But anything is possible. What’s curious is this avalanche of malfunctions with version 5.13, given that nothing significant has changed compared to dev or others PR.

Jacques

1 Like

Thanks for testing Jacque, I figured it’s something wrong with my PC (I have multiple versions of RawTherapee for different purposes, so maybe things went messy because of that). A few month ago I also encountered a problem which no other people can replicate. So I’m glad that it seems it’s only me and there is no actual problem with RawTherapee itself.

1 Like

Hello, starting the AppImage from a terminal gives the same error messages, except for the last three. My AppImage works normal.

Could it be that the app crashes because of the space character between My and Passport?

1 Like

Hello Wayne
@Wayne_Sutton

Can you test the PR related to ā€˜secam16’? I made a change in Ciecam (the one I suggested for RC5.13): Selective editing CAM16 & Wavelet.

Of course, using the compiled version (if you can) and the executables (the AppImage, in your case).

secam16

Actions
Actions

Of course, there are differences compared to RC-5.13, but this might make it possible to eliminate some unknowns.

Thank you

Jacques

1 Like

Hello Jacques @jdc , thank you, the secam16 x86 Appimage seems to have fixed both the crash and the artifacts generated by the Brightness curves. I have opened and closed it a dozen times or so without any problems. I only tried the Brightness curve on the image I posted above and there doesn’t seem to be any problem (with reasonable Brightness increases in any case). I’ll try it on a few other images tonight.

That’s a good point Paul, I hadn’t noticed that. I’ll see if I can edit it without reformatting the disk.
EDIT: that seems to be the problem - I simply unmounted the disk and started and closed the Appimage several times without it crashing. As soon as I mounted the disk and selected it in RawTherapee, it crashed as previously. It’s strange though that this seems to happen only with this particular Appimage.

1 Like

Self compiled on Manjaro (7.0.10-1) Cinnamon (6.6.8)
AMD Ryzen 7 5800H, 16GB, RTX3050 Mobile

No problems.

1 Like

Strange indeed – but strange things do happen, especially with computers! :upside_down_face:
Glad you solved your crash problem!

1 Like

Thanks for your help Paul. In reality it’s not completely solved because while unmounting the disk fixes the problem, removing the space in the label doesn’t. I went through and corrected a few other instances of spaces in the file or folder names but there must still be some lurking in there somewhere. As I mentioned above this isn’t a problem with Jacques’ @jdc secam16 branch but finding out why is beyond me especially in this heat.