5. WHY - Metadata for many new and various camera and imaging equipment (eg. CR3) is now recognized in metadata-exiv2
6. HOW - This branch changes the way metadata is read by RT under the hood.
Caveats: lensfun works ok, with reasonable limitations. For example, exiv2 can read that this is from an R7, and is stating which Sigma lens is on, but the equipment is still too new for lensfun, which did not match anything automatically.
@jhmnieuwenhuis You may have a try at this latest build in the same folder, replaces previous.
OHH WAIT-- -you have two copies of RawTherapee in the Applications folder, that causes an error unfortunately, you will have to swap them so only one exists inside the folder at a time. Thanks…
nope, at work… thought I could do some testing whilst editing some work photos.
When I click your link 4. WHERE I get forwarded to an icloud page saying I need to log in to mount the shared folder.
Since it’s a work computer the appleid situation is a bit strange. Not really a mac guy and trying to make sure I won’t become one
(rawtherapee:6620): Gtk-WARNING **: 19:26:22.299: Could not load a pixbuf from /org/gtk/libgtk/theme/Adwaita/assets/bullet-symbolic.svg.
This may indicate that pixbuf loaders or the mime database could not be found.
Error: Directory Image, entry 0x935c has invalid size 7161803041; skipping entry.
Error: Directory Image, entry 0x935c has invalid size 12003611241; skipping entry.
Error: Directory Image, entry 0x935c has invalid size 4476128841; skipping entry.
Error: Directory Image, entry 0x935c has invalid size 9847472401; skipping entry.
Slight correction.
I am a bit rusty on Rawtherapee.
When i use the down arrow to the right of the pallet, nothing happens.
When i click directly on the pallet there is a message on the cmd window
** (rawtherapee:6686): CRITICAL **: 19:32:31.962:
unhandled exception (type Glib::Error) in signal handler:
domain: g-io-error-quark
code : 15
what : Creating an app info from a command line not currently supported
Mica - RT 5.9 public release has the old style external editor command line setup.
open -b “com.adobe.Photoshop” does indeed open the image from RT into Photoshop 2023 just as it should.
Removing all traces of 5.9 public release totally from the system, and replacing with any of the dev builds using the NEW external editor command line setup - no dice, nil, nada, no export.
Remove the 5.9dev build and replace with 5.9 public release - it all works again.
Same machine, same OS, and same Photoshop installation.
So, seeing as the “old way” works and the “new way” does not, logically, it’s more likely the new RT is at fault here.