#20480 (Bug) DisplayCal + SpyderX results in faulty calibration

+1 0

New
Component: DisplayCAL
Created by Arjun P

Last modified


Hi Team,

I have a SpyderX Pro which I’m using with DisplayCal 3.8.7.1. I have tried numerous runs with the device but it always ends up with pathetic values. I’m a noob so help me locate the exact issue. I have attached the logs but on the high level, I could see lots of retries yielding poor results. What am I doing wrong? Should I have to enable/ disable some key parameters? Using Argyll 2.1.1 USB plugin software.

Got lots of inverting Jacobian failed (3) error messages:

Logs:

16:42:39,467 Patch 14 of 32 DE 0.683486, W.DE 0.683486, W.peqDE 0.314836, OK ( < 0.900000)
16:42:41,089 Patch 15 of 32 DE 13.768960, W.DE 13.768960, peqDE 13.806303, Repeat
16:42:47,608 Patch 15 of 32dispcal: inverting Jacobian failed (3) – falling back
16:42:47,609 DE 13.768960, W.DE 13.768960, peqDE 13.806303, Repeat
16:42:49,170 Patch 15 of 32 DE 180.131421, W.DE 180.131421, peqDE 180.545084, Repeat
16:42:50,907 Patch 15 of 32 DE 103.680701, W.DE 103.680701, peqDE 103.254197, Repeat
16:42:52,569 Patch 15 of 32 DE 238.880668, W.DE 238.880668, peqDE 239.230999, Repeat
16:42:54,286 Patch 15 of 32 DE 28.008857, W.DE 28.008857, peqDE 27.771469, Repeat
16:42:55,871 Patch 15 of 32 DE 58.527877, W.DE 58.527877, peqDE 58.918017, Repeat
16:42:57,533 Patch 15 of 32 DE 4.941826, W.DE 4.941826, peqDE 4.585477, Repeat
16:42:59,137 Patch 15 of 32 DE 1.434011, W.DE 1.434011, peqDE 1.141761, Repeat
16:43:00,644 Patch 15 of 32 DE 1.291849, W.DE 1.291849, W.peqDE 1.702068, Fail ( > 0.900000)
16:43:02,279 Patch 16 of 32 DE 14.717152, W.DE 14.717152, peqDE 14.273966, Repeat
16:43:08,780 Patch 16 of 32dispcal: inverting Jacobian failed (3) – falling back
16:43:08,796 DE 14.717152, W.DE 14.717152, peqDE 14.273966, Repeat
16:43:10,339 Patch 16 of 32 DE 77.305883, W.DE 77.305883, peqDE 77.030911, Repeat
16:43:12,101 Patch 16 of 32 DE 137.591613, W.DE 137.591613, peqDE 14.273966, Repeat (got ↲
↳ worse)
16:43:13,739 Patch 16 of 32 DE 79.512629, W.DE 79.512629, peqDE 79.233561, Repeat
16:43:15,493 Patch 16 of 32 DE 65.357699, W.DE 65.357699, peqDE 66.470833, Repeat
16:43:17,132 Patch 16 of 32 DE 90.196384, W.DE 90.196384, peqDE 89.901916, Repeat
16:43:18,871 Patch 16 of 32 DE 51.652239, W.DE 51.652239, peqDE 14.273966, Repeat (got worse)
16:43:20,490 Patch 16 of 32 DE 82.932031, W.DE 82.932031, peqDE 82.647319, Repeat
16:43:22,237 Patch 16 of 32 DE 14.717152, W.DE 14.717152, W.peqDE 14.273966, Fail ( > ↲
↳ 0.900000)
16:43:23,819 Patch 17 of 32 DE 12.716641, W.DE 12.716641, peqDE 12.621152, Repeat
16:43:30,335 Patch 17 of 32dispcal: inverting Jacobian failed (3) – falling back
16:43:30,336 DE 12.716641, W.DE 12.716641, peqDE 12.621152, Repeat
16:43:31,894 Patch 17 of 32 DE 40.554946, W.DE 40.554946, peqDE 12.621152, Repeat (got worse)
16:43:33,529 Patch 17 of 32 DE 40.554946, W.DE 40.554946, peqDE 12.621152, Repeat (got worse)
16:43:35,190 Patch 17 of 32 DE 40.554946, W.DE 40.554946, peqDE 12.621152, Repeat (got worse)
16:43:36,865 Patch 17 of 32 DE 42.742128, W.DE 42.742128, peqDE 12.621152, Repeat (got worse)
16:43:38,515 Patch 17 of 32 DE 63.430377, W.DE 63.430377, peqDE 12.621152, Repeat (got worse)
16:43:40,183 Patch 17 of 32 DE 70.241269, W.DE 70.241269, peqDE 71.390221, Repeat
16:43:41,910 Patch 17 of 32 DE 41.664839, W.DE 41.664839, peqDE 12.621152, Repeat (got worse)
16:43:43,526 Patch 17 of 32 DE 12.716641, W.DE 12.716641, W.peqDE 12.621152, Fail ( > ↲
↳ 0.900000)
16:43:45,246 Patch 18 of 32 DE 12.751754, W.DE 12.751754, peqDE 12.424136, Repeat
16:43:51,812 Patch 18 of 32dispcal: inverting Jacobian failed (3) – falling back
16:43:51,816 DE 12.751754, W.DE 12.751754, peqDE 12.424136, Repeat
16:43:53,378 Patch 18 of 32 DE 36.775138, W.DE 36.775138, peqDE 36.935514, Repeat (got worse)
16:43:55,131 Patch 18 of 32 DE 153.090258, W.DE 153.090258, peqDE 12.424136, Repeat (got ↲
↳ worse)
16:43:56,798 Patch 18 of 32 DE 36.775138, W.DE 36.775138, peqDE 36.935514, Repeat (got worse)
16:43:58,528 Patch 18 of 32 DE 99.876099, W.DE 99.876099, peqDE 12.424136, Repeat (got worse)
16:44:00,190 Patch 18 of 32 DE 36.775138, W.DE 36.775138, peqDE 36.935514, Repeat (got worse)
16:44:01,923 Patch 18 of 32 DE 27.156925, W.DE 27.156925, peqDE 26.733117, Repeat
16:44:03,588 Patch 18 of 32 DE 114.432614, W.DE 114.432614, peqDE 116.282925, Repeat
16:44:05,293 Patch 18 of 32 DE 12.751754, W.DE 12.751754, W.peqDE 12.424136, Fail ( > ↲
↳ 0.900000)
16:44:06,917 Patch 19 of 32 DE 13.006801, W.DE 13.006801, peqDE 12.566553, Repeat
16:44:13,463 Patch 19 of 32dispcal: inverting Jacobian failed (3) – falling back
16:44:13,476 DE 13.006801, W.DE 13.006801, peqDE 12.566553, Repeat
16:44:15,025 Patch 19 of 32 DE 32.981222, W.DE 32.981222, peqDE 33.114152, Repeat (got worse)
16:44:16,788 Patch 19 of 32 DE 153.571230, W.DE 153.571230, peqDE 12.566553, Repeat (got ↲
↳ worse)
16:44:18,460 Patch 19 of 32 DE 32.981222, W.DE 32.981222, peqDE 33.114152, Repeat (got worse)
16:44:20,194 Patch 19 of 32 DE 113.709067, W.DE 113.709067, peqDE 12.566553, Repeat (got ↲
↳ worse)
16:44:21,858 Patch 19 of 32 DE 32.981222, W.DE 32.981222, peqDE 33.114152, Repeat (got worse)
16:44:23,586 Patch 19 of 32 DE 195.681276, W.DE 195.681276, peqDE 12.566553, Repeat (got ↲
↳ worse)
16:44:25,226 Patch 19 of 32 DE 32.981222, W.DE 32.981222, peqDE 33.114152, Repeat (got worse)
16:44:26,947 Patch 19 of 32 DE 13.006801, W.DE 13.006801, W.peqDE 12.566553, Fail ( > ↲
↳ 0.900000)


DisplayCAL (text/plain | 2019-10-09 15:25:52)
WhatsApp Image 2019-10-09 at 6.52.28 PM (image/jpeg | 2019-10-09 15:25:52)


12 comments on “DisplayCal + SpyderX results in faulty calibration”

  1. Something seems to be interfering with calibration. Close any background programs. Disable any and all dynamic features of the display (auto-dimming/contrast, power saving, ambient sensors etc).

  2. Hi Florian,

    No background programs are running.. Actually I tried it after rebooting the display and try running this after 30min.  I have enabled the power settings in such a way that the screen doesnt sleep in the middle of calibration. I am unable to identify what the error is. I tried the device in another laptop also. I have the same issue there as well..

    Can you please help identify the issue?

     

    Attached is the power and display settings: display

    power

  3. Adding:

    I tried running the device with the OEM software coming along with it (Datacolor Pro software). It worked fine without any issues although the profile looked a bit on the warmer side 🙁 . So, I dont think there is any problem with the device.

  4. I see some stuff in the tray that does not look standard. Your problem seems to start about three to four minutes in, the Spyder software measures much fewer patches (less accurate as a result) so it’s probably already finished at that time.

    Also make sure you are doing the SpyderX instrument calibration (off screen, with cap tightly on) correctly.

  5. Hi Florian,

    I retried it after closing Chrome applications (which was running earlier). Now, it worked fine. Let me try it on another laptop as well (Where i had the issue) and comment..

    BTW, Thanks for the tips..

  6. Do you use Spyder5 for correction? (since there are no SpyderX for correction)

    Not sure if this is what you’re asking, but you cannot use corrections made for the Spyder5 with the SpyderX. It’s a different instrument.

    I have the same problem still can not solve this issue *SAD*

    When the software asks you to take the instrument and place the cap on, what do you do?

  7. Actually.. This is one of the mistakes I did. When the software asks us to take the instrument and place the cap on, I was keeping it open on the screen but actually it should be kept closed.

    Just a request for the developers — Can be accompanied by a pic showing users to close the lid. Kind of confusing!!! We have a measurement window showing up just before this step which makes us  put the hardware on the screen and ignore this step.

  8. We have a measurement window showing up just before this step which makes us put the hardware on the screen and ignore this step.

    Yes. The sequence is: 1. Put instrument on screen 2. Take off for sensor calibration when asked. There really is no way around it. I’m almost certain that even with a graphic, some people will probably ignore this step or think it is “unnecessary” for some reason.

  9. @Florian: Thanks for the response.

    I will tell you where the confusion is — When we are about to start the calibration, the measurement window pops up first (where there is no actual message to put the device on screen but the human tendency puts the device there 😉 ) and second is the step where we have to keep the lid of calibrator closed and third is to put the device on screen.. So this is kind of confuses the first user…

    Now, it works perfectly on all my devices.. Kind of becoming a PRO now :P…

    Thanks for the immediate help. You can go ahead and close the ticket as “Not a Bug”

Leave a Reply