@Mega_DerpBro maybe your DNG is not a proper raw file but a “linear” one? Please upload it.
Even if we were to jump through Microsoft’s hoops to get certification and pay the price (couldn’t even find the cost), it still wouldn’t necessarily prevent that warning.
Nothing is lost, don’t exaggerate. And while waiting for a Windows 5.7 build with the fixed cache and config paths, you can fix the problem for yourself by using environment variables: File Paths - RawPedia
Looks like neither. RawTherapee’s Windows installer doesn’t look for a HaldCLUT folder at all. Go to Preferences > Image Processing > Directories and set your HaldCLUT folder. As @gaaned92 pointed out, if you’re on Windows then RawTherapee 5.7 may simply have found an old options file which contained a different HaldCLUT folder path. I will upload the fixed 5.7 build later today.
It works fine in Linux, I just tested. Please write a proper report if you made sure the requirements are met: GIMP Plugin - RawPedia Also see @gaaned92’s reply.
Yes, please do rename the release builds (not the non-releases).
Could Windows users please verify whether opening a raw file from GIMP-2.10.12 using the following latest RawTherapee 5.7 build works correctly? Correctly means that when you open a raw file from GIMP, RawTherapee should appear.
For the latest version.
On spaces in the file name (spaces in the directory name do not bother).
I repeated the error on another computer (also Windows10, Gimp-2.10.12 64bit).
If I change the name from Test space.nef to Testspace.nef - it works fine.
On file-rawtherapee.exe in Gimp.
In the registry (regedit.exe) - ok.
First of all, if RT5.7 is isntalled there is no possibility to choos RT in Gimp (Preferences-> Image Export & Import) only darktable and placeholder, no rawtherapee
With RT.5.6 all options are present and works ok
This is probably because the plugin cannot detect the RT executable at GIMP startup. Hence my question regarding the output of rawthrapee.exe -v -w.
I currently have no access to a windows machine, so I cannot check this myself…
My fault, it comes from a patch I have introduced to force-disable client side decorations on windows (unless specifically enabled by the user via the GTK_CSD environment variable). I was printing the value of the variable for debugging, and the printout was left there by mistake…
I am fixing this right now, will put a message here as soon as the new package is available.