Trying out PL7 at the moment and struggling with the colour handling.
With a GFX100s image of a city-beach scene in cloudy daylight, if I use the white-balance eye-dropper on a grey area the white balance is way off with far far too much green (tint -82!). But if I use the eye-dropper on an area of deep yellow sand, the resulting white balance looks ok. If I choose a different area of grey or sand I get different results again.
I suspect that the problem is that the UI the eye-dropper’s visible position on screen does not correspond to the actual part of the image that is sampled.
Possibly related, some of the Fuji film simulations (eg Astia-Soft) appear much too saturated, resulting in unnatural Neon oranges and pinks in scenes with muted lighting. I can correct for this by reducing saturation or the strength of the rendering, but I did not need to do this in PL6.
Which update are you talking about, 5.15? I am still on 5.14, so I guess I should better not update?
@Barbara-S , are there any plans to fix this bug in version 5 as well? And if not, do you consider to take down the last update, so that people will not destroy their functioning version of PL5?
stuck
(Canon, PL7+FP7+VP3 on Win 10 + GTX 1050ti)
5
I’m running PL 5.15.0 on both Win 10 and Win 11 and I can’t reproduce this. When I change the ‘RAW White Balance’ setting from ‘As Shot’ to anything else, the relevant values change (e.g. for Daylight the Temp becomes 5200K and the Tint becomes 0) and the white balance of the image changes in keeping with the chosen setting.
i know, i’ve seen it, that’s why i said what i said.
on MAC, changing white balance to other setting wouldn’t change colours in any pictures, but the value on the chart does change, if i click on the value then WB change to “custom”.