- This topic has 6 replies, 2 voices, and was last updated 8 years ago by
.
-
Posts
-
I often see those overview charts like they’re shown on notebookcheck.com for example. Now I bought a Spyder5 Express and first tried to use their original software, which is (sorry) crap. It produced totally wrong colours after calibration and doesn’t show any information at all. Now after a few hours with DisplayCAL I got nice results and lots of data.
What I’m looking for is a report like that seen in Calman. With an overview of the dE values per colour, the target/actual comparison and the colour space chart with rectangles and circles.
DisplayCAL can generate a report that seems to have most of this information, spread over many screen pages, but the colour space chart (the last one) doesn’t have a background and the target/actual can’t be seen either. Can I set up DisplayCAL to show that information as well? And maybe also generate a more compact report with the mentioned information?
PS: Forgot to mention: I’ve tried Calman but it can’t find my device so it’s completely useless to me.
Hi,
DisplayCAL can generate a report that seems to have most of this information, spread over many screen pages, but the colour space chart (the last one) doesn’t have a background and the target/actual can’t be seen either.
This depends on the type of verification you run – see the documentation.
The documentation doesn’t tell me a lot about the different report types. And it’s a bit too many to try them all and see the form of the results. I’d have expected sample outputs of each report.
BTW, is it normal that the report isn’t available until a calibration has been done? At least the report command is disabled on another computer directly after installing it. I’m now running the calibration (which takes about an hour!) and see whether the report is available after that.
The documentation doesn’t tell me a lot about the different report types.
It’s very extensive and covers all possible variations.
I’d have expected sample outputs of each report.
That would be way too much.
BTW, is it normal that the report isn’t available until a calibration has been done?
Yes. In a color managed environment, it doesn’t make much sense to evaluate the native response of a display against a given standard, although that is possible by enabling simulation profile and setting tone curve to “Unmodified” on the verification tab.
Yes. In a color managed environment, it doesn’t make much sense to evaluate the native response of a display against a given standard, although that is possible by enabling simulation profile and setting tone curve to “Unmodified” on the verification tab.
Well, my primary concern right now is measuring what a monitor does without any corrective measures. This should tell me how close to sRGB the output already is. If it’s way off or doesn’t nearly cover the colour space then it’s probably now what I’m looking for and I need to find another monitor. My main work is outside of ICC-capable software so creating a profile isn’t too useful to me.
I have now measured the new monitor and I’m confused by the results of DisplayCAL.
When I run the normal calibration and profiling, I get a result that differs greatly in the preview. Enabling or disabling the profile preview has a large effect on the normal desktop appearence. This cannot be verified however by switching between the sRGB and the newly installed calibration from the Windows colour management settings. There’s hardly any visible difference between the two. So I assume that “preview disabled” in DisplayCal has shown me something wrong but not what I’d see without using any calibration whatsoever.
Then I have run the verification. Once with default settings (which I don’t fully understand): In the top settings selection the new monitor entry, in the middle selection “Erweiterte Überprüfungs-Testform” and in the bottom selection “” (empty). That gives me very good results in the report. But I have the feeling that it simply verifies what was profiled just ago, so I wouldn’t expect any difference here. This is useless. Measuring what was just set doesn’t make me any wiser.
The next verification was with “current settings” at the top, where I’ve selected the “sRGB” profile in the Windows settings. That showed a difference in the target whitepoint of 3.93 but the colours were good.
The third verification with the new monitor settings again at the top selection and sRGB simulation showed a whitepoint difference of 3.95 and 5.72, the colour dE values are avg 1.48 and max 6.78 (mainly for red/yellow hues).
So this monitor might show very accurate colours or they might as well be off. I don’t know.
Looks like the German saying “wer viel misst, misst Mist.”
What is the suggested procedure to measure the monitor at its native settings with no calibration or profiling? Is DisplayCAL able to do that? Should I need CalMAN for that, like any other hardware review seems to do, then the Spyder5 colorimeter was a wrong invest because that isn’t supported by that software.
So I assume that “preview disabled” in DisplayCal has shown me something wrong but not what I’d see without using any calibration whatsoever.
That’s exactly what it does: Preview disabled = calibration disabled.
But I have the feeling that it simply verifies what was profiled just ago, so I wouldn’t expect any difference here.
Indeed. You would run this type of test after some time has passed (e.g. a week), and this would then tell you if the display has drifted since it was last calibrated and profiled.
The third verification with the new monitor settings again at the top selection and sRGB simulation showed a whitepoint difference of 3.95 and 5.72, the colour dE values are avg 1.48 and max 6.78 (mainly for red/yellow hues).
This shows how well the monitor can reproduce an sRGB target. It’s gamut is probably too small to cover the whole of sRGB (gamut coverage is shown in the profile installation dialog).
What is the suggested procedure to measure the monitor at its native settings with no calibration or profiling?
Choose a simulation profile of your choice (e.g. sRGB) and enable “Use simulation profile as display profile”.
