Error 2 w. new version 3.2

[t.g.v]

Hi,

I’m receiving error 2 after complete measurements at step “install new profile”.

regards – tg

Attachments:

You must be logged in to view attached files.

[Florian Höch]

Hi,

attach logs please.

[t.g.v]

of course.

Attachments:

You must be logged in to view attached files.

[Florian Höch]

Weird error. Seems the profile was installed regardless:

Lade Kalibrierungskurven des aktuellen Anzeigegeräteprofils...
2016-11-20 11:10:22,994 C:\WINDOWS\system32\spool\drivers\color\display1-80b8bef76e5e08eb6eb516de6fc71f61.icm
2016-11-20 11:10:23,046 About to open dispwin object on the display
2016-11-20 11:10:23,046 About to clear the calibration
2016-11-20 11:10:23,046 About to set display to given calibration
2016-11-20 11:10:23,046 Calibration set

You can also confirm this by opening up the profile associations dialog of the profile loader, or clicking on its icon.

[jcarlson]

Hi,

I’m experiencing the same error. And even if the profile seems to be installed, it is not manageable in the Window Profile color management.

Best regards.

[Florian Höch]

And even if the profile seems to be installed, it is not manageable in the Window Profile color management.

The Windows color management applet is inherently flawed when it comes to multi-monitor support, but if it doesn’t even list your display device(s), this could hint at a deeper rooted problem in your system. Make sure you use the latest video drivers for your graphics card.

[Florian Höch]

Also, it makes absolutely no sense to install a profile as system default on a single user system, so unless you have several user accounts, you shouldn’t use that option (looking at the logs above).

[t.g.v]

Weird error. Seems the profile was installed regardless

Yes, the profile is loaded. but resetting gamma-table and reloading profile doesn’t change anything on my monitor.

verification report indicates: Measured vs. assumed target whitepoint ΔE*00 of 5,4; what is strange behaviour on my system. nevertheless, single color readings were fine in result.

regards – tg

Criteria Nominal Recommended # Actual Result
Measured vs. assumed target whitepoint ΔE*00 <= 2 <= 1 5.43 NOT OK ✖
Average ΔE*00 <= 1.5 <= 1 0.52 OK ✔✔
Maximum ΔE*00 <= 4 <= 3 (20) 1.28 OK ✔✔

[Florian Höch]

Yes, the profile is loaded. but resetting gamma-table and reloading profile doesn’t change anything on my monitor.

Look at DisplayCAL-apply-profiles.log after setting calibration state to “Reset” and then “Load profiles”. Do you see any errors after “Lade Kalibrierungskurven des aktuellen Anzeigegeräteprofils…”? (the log above looks fine, apart from the UI bug that you need to close profile information windows before closing the profile associations dialog).

verification report indicates: Measured vs. assumed target whitepoint ΔE*00 of 5,4; what is strange behaviour on my system. nevertheless, single color readings were fine in result.

This just means the measured whitepoint is probably not close to the daylight locus.

[t.g.v]

after reset/load again it reads:

2016-11-21 18:24:43,977 Menu command:
2016-11-21 18:24:43,977 Set calibration state to reset vcgt
2016-11-21 18:24:44,040 Setze Grafikkarten-Gammatabelle zurück…
2016-11-21 18:24:44,042 1. PB248 @ 0, 0, 1920×1200 (Primär)
2016-11-21 18:24:44,046 …ok.
2016-11-21 18:24:58,220 Menu command:
2016-11-21 18:24:58,220 Set calibration state to load profile vcgt
2016-11-21 18:24:58,325 Lade Kalibrierungskurven des aktuellen Anzeigegeräteprofils…
2016-11-21 18:24:58,325 1. PB248 @ 0, 0, 1920×1200 (Primär) -> display1-330a22be1a03ff953eac1d111a4123a2.icm
2016-11-21 18:24:58,342 …ok.

[Florian Höch]

That looks fine. If you disable the profile loader, does dispwin -v -c (clear calibration) and dispwin -v -L (reload display profile calibration) from a command prompt work? (btw, maybe you’re just not noticing a change because your monitor is already close to the default gamma 2.2 target, so the calibration is nearly linear?)

[Florian Höch]

Btw, after further investigating I’ve found the error 2 “File not found” / “Datei nicht gefunden” that occurs after profile installation if the profile name contains “special” characters to be bogus – it can be safely ignored and the profile was already installed when the error is thrown.

[t.g.v]

Hi,

after some windows-restarts everything is ok. my guess is: i had a mediaplayer plus madvr running in background; obviously blocking  profile-reload. what makes sense.

regards -tg

[Florian Höch]

after some windows-restarts everything is ok. my guess is: i had a mediaplayer plus madvr running in background; obviously blocking profile-reload.

Hmm, in that case the profile loader would have grayed the menu items to allow calibration reload/reset. Still glad you got it working.

[t.g.v]

“display1-330a22be1a03ff953eac1d111a4123a2.icm”  seems not to contain special characters.

tg

[Author]

Posts