Colour changed
-
@herf - Why change it? It was perfect! I'm not going to use it like this. This is a mess.
-
@saritasarita what are you seeing?
Again, there should not be a visible change for most people if you're using the same kelvin value as before. The change is mostly designed to work better with wide-gamut displays.
If you're unhappy with the setting, we also changed the preset before bed, and you can move the slider or choose a different preset.
-
Having reverted back to v3, I am not 100% sure any more whether I am seeing a difference between v3 and v4 in "classic" mode.
Of course in default v4 mode, there is an obvious different during night time, when v4 has a much more intense setting, and I often work very late so I will have noticed that straight away.
With v4 in classic mode, avoiding the new night time settings, I'm not so sure I'm seeing any difference, although I can't seem to get comfortable with it.
I will try it a few more days and see if I get used to it.
-
hi
use display data for better color accuracy introduces a cloying slight greenish tinge on my w520
(turning it off pushes red even at 5000k - in between would be perfect)
to be fair the display data and default profile are notoriously bad for the 95% sRGB panel on my computeri am using a profile from the same panel type as mine
(the optional calibrator for this model is bullocks - and this panel only calibrates well with some equipment)
the default profile has serious red issues (as does this monitor with no profile at all - worse though - think aRGB reds on a sRGB panel)i seem to recall being able to tolerate much warmer values with the old transfer function but with v4 i cant stand anything below 4200k
please allow a reg value for old behavior if possible.
thanks
-
Is it a wide-gamut panel (the FHD model back then was) or are you saying it is 95% sRGB? In the newest version, you can post the "driver info" from the options menu and it will show what the panel is reporting. (Download again from the website.)
And does f.lux look better without the profile installed? It may just be a bad profile!
-
panel is 95% sRGB (considered wide gamut sorta - reds exceed sRGB colorspace)
stock profile is trash (i remember reading the display data was also questionable on this panel)monitor is useless without a decent icc profile. i am using a user created one from the same model but not my panel. this is a hard to profile tn panel (the lcd backlight temperture being a big factor)
does unchecking use display data cause the program to ignore the monitor profile?
-
NVIDIA 21.21.13.7691: NVIDIA Quadro 1000M (20170217)
ThinkPad Display 1920x1080
Dimensions: 344 x 193
Year: 2009
Chroma:
R=0.675781 0.314453
G=0.214844 0.665039
B=0.140625 0.069336
W=0.313477 0.329102
sRGB gamut: 102%, AdobeRGB gamut: 91%the profile i am currently using is supposed to be 6500k but is possibly slightly warmer
(the garbage thinkpad supplied profile is about 7200k - 8200k it is based on native white) -
I know this exact panel - have a T510 in the closet!
https://fluxometer.com/rainbow/#!id=Thinkpad T510 FHD/6500K-ThinkpadT510FHDAnd I can see what you mean.
The old version of f.lux will make "more saturated" colors here (kind of like the panel does for everything), because it is assuming your display is sRGB, which it isn't. The new version is trying to pull it back to "real" colors. But maybe the chromaticities have moved a little bit since 2009, so that might be where the yellowish effect is coming from. I will try to think of a better solution for this - we should do a little better. We have some other options in the code that might work too.
-
thanks for the reply
so apparently the 95% refers to 95% ntscregardless my question stands
"does unchecking use display data cause the program to ignore the monitor profile?"i believe use display data may be over compensating the green channel
(i may go back and whip up an avg of the 2 sets of LUT values and test them but it looks like my issue has to do with the green channel alone)i am concerned about a slight green bias when the box is checked.
fyi this machine has seen very little on time and the panel almost no uv exposurelenovo stockpiled this monitor and was still using it in the w530
the version i used to like on this machine was the old beta from 2012 with the nvidia setting (was icc aware)
fyi i was looking at the LUT tables and i wonder if the lines could be smoothed (get rid of value duplication) in v4 (the steps seem a bit lazy) -
@herf
is your t510 display profiled?
could you upload or send me the icc file so we can cross comparei will upload some text files of LUT values + the profile i am using that you can test on your t510 and a link to necessary tools.
-
@herf
im not sure what changed but it seems that the green tinge issue i was having is basically resolved or at least acceptable. I am now using checked "use display data for better accuracy" and am back to using 3400kcurrently running 4.66 (beta checked)
thanks
