Open eltomek opened 2 years ago
You are using a RawTherapee version that is too old. The "official" stable release that is mentioned here and which you are using does not support the X-T30. Newer version do have a tailor-made DCP profile for this specific camera. There are many other reasons as well why you should not be using that one: This versions has, now fixed, bugs. It supports a wider range of newer gear. It has some new features and some of the already present features are updated/expanded upon.
I would suggest you to use one of the latest, and 99% stable, development builds.
You can choose which one from this Pixls topic
@jade-nl I may be wrong but I don't think that's the problem of RT version: the one referred at the official website (5.8) works just the same to the latest dev release (5.8-3093-g9b837e59b). Both releases contain ".\dcpprofiles\FUJIFILM X-T30.dcp"
files (and they are identical in those 2 versions).
I figured out that the problem is with Windows 11. Don't know why RT can't map the camera model onto the correct file or read the file from the disk.
With the official RT5.8 ran on Windows 11, the auto-matched camera profile is inactive, like it wasn't available in the RT system at all and
With the same official RT5.8 ram on Windows 10, for the same RAW:
The official and dev release versions are indeed different in terms of how the X-T30 (and others) are defined in camconst.json
and hence the impact is seen when the Camera Standard option is used, seems like the dev release has more vivid colors than the official release (both shots with linear Tone Curves):
Official:
Dev release:
Finally, on Windows 11 I am able to achieve satisfactory results either by loading the X-T30.dcp file manually and setting the tone curve linear (better option when using film simulations which assume linear tone curves) or using the dev release and auto-adjusting the tone curves, the images are similar but not identical.
I may be wrong but I don't think that's the problem of RT version:
You are correct!
I loaded the file and noticed differences and, with so many people running into problems atm with the old stable 5.8 version I jumped to conclusions.
OK, so this issue can be summarized as follows:
Checked on RT5.8 official version as well as the latest dev release (5.8-3093-g9b837e59b).
RT does not load up the ".\dcpprofiles\FUJIFILM X-T30.dcp"
file upon loading the RAF file (Fujifilm's RAW file) in Windows 11 and therefore the Auto-matched camera profile
is inactive.
The same operation, with the same RT versions on Windows 10 read the file correctly and the option is available to be selected
I don't know if that's a bug or feature but I've noticed that when I load the RAW file from Fujifilm X-T30, the color profiles are loaded properly. The DCP file for X-T30, along with other newer Fujifilm camera profiles is provided as part of the regular 5.8 release now.
Steps to reproduce the issue:
"c:\Program Files\RawTherapee\5.8\dcpprofiles\FUJIFILM X-T30.dcp"
, see the colors are correct now (correct means they are almost identical to CaptureOne's version).The CaptureOne Fuji Edition out of the box view when opened RAW:
So, it looks like the X-T30 DCP profile is correct however for some reasons it's not read and applied as "Camera standard". In fact, when I take the
"c:\Program Files\RawTherapee\5.8\dcpprofiles\FUJIFILM X-T30.dcp"
file and rename it so that RT can't find it at all, I get the same results as in step 1 (which confirms the X-T30 profile is ignored when "Camera standard" is selected).The RAW file is available at https://drive.google.com/file/d/13_cIlbCBGyPFt0Q56g99JXw4CRxUEqZz/view?usp=sharing