Lightroom/Camera Raw: Fuji GFX Raw File White Balance Issues - Magenta Tint

I'm using the full resolution JPEG generated in camera, not the lower resolution embedded JPEG.

When I compare in-camera to ACR, the ACR files requires C2 more magenta correction, based on sampling the white area of the test card on both images.

RAW Conversion


In-Camera JPEG

PS and LR use the exact same Adobe Camera Raw plugin. The only difference is that ACR doesn't have LR's Library module and preview capability. It's good I checked this issue inside LR because I can confirm what you're seeing in LR's Library module preview when only standard previews have been built and not 1:1 previews.

In the below screenshots I cannot confirm what you're seeing in the Develop module and JPEG export files. These were opened in PS and compared the values compared in the ColorChecker Grayscale top bar. The posted file is Adobe RGB profile to keep as close as possible to my wide gamut NEC PA272w display profile. The measurements speak for themselves.


Once thing I noticed is that the As Shot WB (5400, 13) is not correct and the image has a distinct blue tint. Using the WB Eydropper on the top Grayscale bar the values are 6150 -4. This is not a huge difference, but incorrect if the camera was properly set for the color meter measured WB. Regardless all three screen shots have the exact same shift including the Embedded Preview created in-camera using your WB settings. So it appears WB was not set correctly in-camera.

Don't get me wrong–I'm not doubting you're seeing this issue on your system. It's just that I can't duplicate it on my Windows 10 system using LR 8.2.1. When I get a chance I'll run the same tests using PS and ACR to see if there's any difference.
EDIT: I have no way of extracting the embedded preview in the RAF file for checking inside PS. It will help if you can reshoot the below ColorChecker with raw + JPEG file format enabled in-camera. Then upload both to Dropbox. Thank you!

I don't use LR, as I said previously - I use PS, so the instructions you're providing make zero sense to me. The fact that your visual experience and mine are different, and that we are using different software, is an issue, on top of my existing problem.

FWIW I wrote my doctorate thesis in color space analysis for robotic vision systems, so maybe I'm more critical than most when it comes to digital color, but regardless, the issue is still presenting itself to me, and other GFX/Adobe users

Let's focus on the actual screen rendering and not the WB values for now. The amount of "actual" WB shift in the image rendering is small compared to the large differences in As Shot WB readings. It's indicative of an issue, but not the problem we need to identify and nail down right now.

Let's address this question, "Given that I'm having to explain the above to you - can I ask what your qualification is to be reviewing this issue?"

I am not an Adobe employee and assisting you as any other user would in this forum. Adobe has assigned some of the more experienced users the title of 'Champion' with ability to edit and move posts as well as communicate directly with Adobe staff. My statement, "I have no idea how LB and CC values are converted to the single Tint value" is in reference to how Adobe converts the raw file's WB matrices to 'As Shot' values, regardless of how they are set in-camera. I established my own color processing lab back in the 1970s and certainly know what CC filters are and how to use them.

In my last post concerning the Studio sample RAF file, "Does that concur with what you see in the Studio sample file DSCF9452.RAF?" If not tell me what you are seeing in the actual screen rendering not WB values.

After looking at this further I discovered building a 1:1 Preview for the DSCF9452.RAF file (Library> Previews> Build 1:1 Previews) removes the magenta tint shift observed in the lower right and left gray background area. Do you see that as well when viewing the image in the Library module? If not 'Remove' the file from LR and reimport it with 'Standard Preview' selected in the Import module 'Build Previews' selector. This is not normal behavior so I need to confirm you are seeing the same behavior...or not! I tried disabling 'Use Graphics Processor,' but it had no affect on the magenta tint with only a Standard preview built.
Hopefully Adobe staff will comment shortly.

I'm worried by your use of the term 'identical' - the two versions are not identical, and the magenta cast is visible on the backdrop, model, grey card etc - the skin tone is a dead giveaway. Do you not see that?

This file shows 5400k +13 WB 'as shot' setting when I bring it into ACR. Actual WB should be 6250k -4 WB, which matches what the camera sees. As with all files, the issue is low K and high CC offsets on the 'as shot', which do not match what the camera is recording.

BINGO–Your Studio sample - GFX50S RAF file really demonstrates the issue!
The embedded preview and LR raw file renderings are identical, but the backdrop shifts to a magenta tint in the lower right and left sides of the image. I used the PROVIA/Standard camera profile, which best matches the embedded preview rendering. As you mentioned all of the camera profiles exhibit the issue. Thanks for hanging in there with me to establish something Adobe can evaluate and fix.

Does that concur with what you see in the Studio sample file DSCF9452.RAF?

https://www.dropbox.com/s/huats888hifq95h/DSCF9452.RAF?dl=0

Given that I'm having to explain the above to you - can I ask what your qualification is to be reviewing this issue?

The color meter CC (Color-Correction) displays Kodak filter number(s) of the necessary light-balancing filter(s) to make for easy selection of the required light balancing filter. Whereas the LB system uses amber or blue filters, the CC system uses magenta or green color compensating filters. CC is the system Adobe represent in ACR, so you only have to use the CC value from the meter.

If you're not seeing it visually, then I'd recommend screen calibration as it's clear as day here. And the eyedropper tool backs it up 100% of the time