Is anyone else experiencing problems with the standard White Balance profiles in the latest version of Classic LR when it comes to support for the Fujifilm X-T3? "As shot" is fine, but if I select "Daylight", "Cloudy", etc. I get a strong green cast. Have never had this problem in the past.
Same problem with X-T3, "As shot" WB Tint goes up to +66!
Apparently Adobe staff has been aware of this problem well before the release:
I don't have that camera model. However, I downloaded a sample raw image and I can confirm this issue. This forum is primarily a user to user forum. I will provide a link to a forum where the developers monitor much more closely. I don't know if this issue has been reported on that forum yet. I don't monitor that forum as closely as others do. But it is the forum where this problem should definitely be reported.
Yes Jim, I also just completed a test with a sample image and experience the same problem.
Raw files from my Olympus are fine.
It appears that Adobe engineers keep getting "stomped" in dealing with Fujifilm sensors and RAF files.
This is a known issue and will be addressed in a future update.
Apologies for the inconvenience.
Thanks - lets hope that if it's know about it's not going to be too far in the future
Have a you a timeframe for an update to fix this ?
Just updated to LR 8.1 - The issue is still there. Ouch.
It may be that you have settings applied to some of your images, and Lr is honoring the settings, including the previous versions of the color profiles that had the white balance bug. For camera matching profiles, you should be able to apply any of the "v2" versions that include the bug fix. For the Adobe Raw color profiles (e.g. Adobe Color, Adobe Landscape), the corrected profiles are based off the "v2" version of Adobe Standard. Once Adobe Standard v2 has been applied, the other Adobe Raw color profiles will be corrected.
Yes, I've found that applying the v2 profiles is better - or just hitting 'Reset' to return the RAW file to it's default settings first also helps.
Oh, I hadn't realized that I had to use a different profile, it worked, thanks!