I even took the profile from a file generated via LR and patched it into the RT file. No dice.
exiftool -icc_profile -b /Volumes/stuff/Pictures/OUT/X10012149_F5.6_1-1300s_ISO200_PROVIA_35-LR.jpg > profile.icc
exiftool “-icc_profile<=profile.icc” RT.jpg
Morning, @Claes! I’m not sure which part of the screen that snippet refers to. My RT5.9 bottom line looks like below from in the editor (I’m on macOS!). How do I check what you’re asking about?
Finally, sincere and heartfelt thanks to the devs for bringing in great new features which I had a quick glimpse of in the latest build! Exciting times ahead!
@Claes, would you be kind enough to mark the thread as ‘Solved’ if that is the norm? I can’t edit the title for whatever reason. Many thanks!
There are folk on this forum who dislike this operation, but honestly, as a commercial image producer, this process causes me zero problems.
When you export an image that’s tagged with an RTv4 (or v2) colour space, bugger all else can understand it.
RTv4sRGB supposedly maps colours the same as sRGB_v4_ICC_preference.icc, but what ever you view your output images in - say Chrome or Firefox - is expecting a profile instruction header starting sRGB, not RTv4…it’s the RT bit that causes the problem.
There was never any need for this ‘profile renaming’ in RT, and it doesn’t occur in DarkTable.
Anyway, give it a try with the two sRGB profiles I’ve attached, and see if it still causes you a problem.
Thanks @Andy_Astbury1. I did see most of your videos and they were very helpful.
I also copied the files you attached but for some reason can only see the sRGB2014.icc in my output list. I’m still investigating.
Hi how to solve this issue on Mac. I use RT 5.9 on MacBook
Pro M1 and find the color saturation change between preview and export jpg same as this like you .Could you please tell me how to solve it?