Docker: Upgrade RawTherapee to fix ProRAW support

[charles-997]

What does not work as described in the documentation?
Images created from my various iPhone models that support the Apple ProRAW image type are not rendered properly in the PhotoPrism WebUI. See example:

How can we reproduce it?

Steps to reproduce the behavior:

1. Import images taken on an iPhone using Apple's ProRAW image format to your PP library.
2. Browse the images via http://photoprism..net/browse
3. Click on any of the iPhone ProRAW image to view full screen. (Note the image thumbnails also render improperly.)
4. See error

If reporting an Import, Indexing, or Performance issue, please include the number and type of pictures in your library,
as well as any configuration options you have changed e.g. for thumbnail quality. There are about 60k images in my library.

What behavior do you expect?

I expect the image to render in a viewable state similar to how Sony .ARW RAW files or Canon .CR2 RAW files are rendered.

What could be the cause of your problem?

As I understand, PP uses upstream software - DarkTable & RawTherapee to render JPEG previews from RAW images. Darktable appears to not yet support iPhone ProRAW files - refer to DarkTable GitHub Issue
Is there an alternative way PhotoPrism could render these images? I do not know the number of PhotoPrism users who 1. use an iPhone for photography and 2. use the Apple ProRAW file type, however I would be surprised if it were not a significant percentage of users.

Try to determine the cause of your problem before submitting a bug report:
https://docs.photoprism.app/getting-started/troubleshooting/

Can you provide us with example files for testing, error logs, or screenshots?

Please add example files or screenshots that help to reproduce your problem.
You may also send files via email or share a download link:
https://photoprism.app/contact

See example in PhotoPrism

Learn how to diagnose frontend issues:
https://docs.photoprism.app/getting-started/troubleshooting/browsers/

NOTE:

• You have to provide sample files and logs if it is an IMPORT, INDEXING, or METADATA issue, otherwise we will not be able to process your report
• If it is an IMPORT issue, please also provide an archive with affected files before importing them so that it's possible to reproduce your issue

Which software versions do you use?

• PhotoPrism Architecture & Build Number (220302-0059f429-Linux-AMD64)
• Database Type & Version (MariaDB)
• Operating System Types & Versions (PhotoPrism running on Linux in Docker)
• Browser Types & Versions (Firefox 99.0.1, macOS 12.3.1)
• Browser Plugins & Ad Blockers (Bitwarden)

The app version / build number can be found in Settings when you scroll to the bottom.
MySQL 8 is not officially supported anymore, see System Requirements.

NOTE:

• Always provide database and operating system details if it is a Backend, Import, or Indexing issue
• Always provide web browser and operating system details if it is a Frontend issue
• If it is a Performance problem, you must provide ALL information

On what kind of device is PhotoPrism installed?

This is especially important if you are reporting a Performance, Import, or Indexing problem. You can skip this if you are reporting a problem found on our public demo, or if it is a completely unrelated issue, such as a broken page layout.

• Device / Processor Type (Unraid custom server build, i5-8400)
• Physical Memory & Swap Space (48GB physical memory, unclear swap size)
• Storage Type (TrueNAS ZFS Array mounted to linux server via NFS. Linux server provides the storage to Docker where PP is running)
• anything else that might be helpful

NOTE:

• Always provide device, memory, and storage details when you have a Backend, Performance, Import, or Indexing issue

Do you use a Reverse Proxy, Firewall, VPN, or CDN?

Firewall- pfSense 2.5.2 on dedicated physical host. Runs a few remote access VPNs. These should be out of scope of my photoprism issue.

NOTE:

• Always provide this information when you have a Reliability, Performance, or Frontend problem, such as failed uploads, connection errors, broken thumbnails, or video playback issues
• If you are using NGINX, also provide its configuration and/or consider asking the NGINX community for advice as we do not specialize in supporting their product: https://docs.photoprism.app/getting-started/proxies/nginx/

[lastzero]

Known issue, not properly supported by Darktable and Rawtherapee yet. Should work with Sips on macOS without Docker when you build PhotoPrism from source.

[giacy86]

Hi. Latest RawTherapee dev build correctly handles Apple ProRaw iPhone dng images (though the thumbnails are a little washed out but still better than nothing). I have tested with the dev AppImage build and worked fine.
So i have copied the rawtherapee-cli bin and all related libraries to the docker container with docker cp. I have also copied a dng image for testing inside the container, entered with photoprism bash and tried to convert the dng with rawtherapee-cli -c image.dng (launching rawtherapee-cli inside the container show the correct dev build). Then i have copied the converted jpg to my home and the image looks fine.
However, when i launch a index -f or thumbs -f the thumbnails are corrupted. Darktable is disabled in settings.
Can you point me in the right direction?

[lastzero]

This request came a bit too late, as we have just released. For reference, this is the version that ships with our default Docker image:

https://packages.debian.org/bookworm/rawtherapee

[Beurling]

The problem is diffrent.Mine dng photos are all missing in the web view

[lastzero]

It seems for you the conversion is not working at all, which ultimately must be fixed in the same way.

[Beurling]

Thank you.

[lastzero]

While RawTherapee has not been updated yet, PhotoPrism can now extract JPEGs from ProRAW files so they can be indexed properly - at least in my tests.

[ark-]

Nice work on the latest Apple support. Thank you team.

I have a bunch of thumbnails like the OP also. If I reindex those using the latest development build will my thumbs be fixed?