Home › Forums › Help and Support › Spyder: Measuring Refresh Rate Failed
- This topic has 19 replies, 2 voices, and was last updated 8 years, 9 months ago by Florian Höch.
-
AuthorPosts
-
2015-05-03 at 18:36 #482
This wasn’t an issue with the last development version, but in 3.0.0 I get this error for every patch.
cheers
2015-05-03 at 18:54 #483Hi,
the message is coming from Argyll CMS.
Not sure if it’s a problem unless you’re measuring a “refresh” type display (e.g. Plasma, CRT). Which Spyder version is this?2015-05-03 at 19:00 #484Hi
it’s a Spyder5pro,
if I could get the 0install to launch the previous snapshot version I would confirm the error origin (but the cache manager always crashes). I ran the calibration using the last snapshot and don’t recall any errors though.2015-05-03 at 19:03 #485I’m still not clear on what it is that you are seeing:
Is it just a message in the progress dialog? In that case it can probably be safely ignored.
Or is it an actual error that prevents running measurements? What’s the measurement mode set to?2015-05-03 at 19:07 #486it’s a message in the progress dialog, I think all it’s affecting is the completion estimate.
Measurement Mode is set to LCD (white LED), the error doesn’t occur in LCD (generic) though. I hadn’t been able to access the extra modes until this release.2015-05-03 at 19:10 #487I hadn’t been able to access the extra modes until this release.
That makes sense, Spyder5 support is about the only difference between DCG 2.9.1.3 beta and 3.0. Can you attach the log after the run is finished? Thanks.
2015-05-03 at 19:18 #488Will do. Thanks for a great product, by the way.
2015-05-03 at 20:22 #4892015-05-03 11:48:25,430 Patch 60 of 64dispcal: Warning – Spyder: measuring refresh rate failed
2015-05-03 11:48:47,959 Patch 60 of 64dispcal: Warning – Spyder: measuring refresh rate failed
2015-05-03 11:49:09,326 Patch 60 of 64dispcal: Warning – Spyder: measuring refresh rate failed
2015-05-03 11:49:36,391 Patch 60 of 64dispcal: Warning – Spyder: measuring refresh rate failed
2015-05-03 11:49:55,625 DE 8.310816, W.DE 8.310816, peqDE 3.301543, Repeat
2015-05-03 11:50:03,509 Patch 60 of 64dispcal: Warning – Spyder: measuring refresh rate failed
2015-05-03 11:50:22,723 DE 5.121794, W.DE 43.278142, peqDE 42.976921, Repeat
2015-05-03 11:50:24,861 Patch 60 of 64dispcal: Warning – Spyder: measuring refresh rate failed2015-05-03 12:33:03,887 Patch 230 of 271dispread: Warning – Spyder: measuring refresh rate failed
2015-05-03 12:33:06,855 Patch 231 of 271dispread: Warning – Spyder: measuring refresh rate failed
2015-05-03 12:33:10,246 Patch 232 of 271dispread: Warning – Spyder: measuring refresh rate failed
2015-05-03 12:33:13,207 Patch 233 of 271dispread: Warning – Spyder: measuring refresh rate failed
2015-05-03 12:33:16,622 Patch 234 of 271dispread: Warning – Spyder: measuring refresh rate failed
2015-05-03 12:33:20,813 Patch 235 of 271dispread: Warning – Spyder: measuring refresh rate failed
2015-05-03 12:33:23,753 Patch 236 of 271dispread: Warning -Spyder: measuring refresh rate failedI have the same error after updating today. I am using spyder 4 express. Since I cannot find the old version of Argyll (i think it was 1.6.3?), I don’t know if this is the dispcalgui or argyll.
Attachments:
You must be logged in to view attached files.2015-05-03 at 20:29 #491Hi,
can you attach the profile? Thanks.
2015-05-03 at 20:58 #492Attached is all the things in the storage folder.
Thanks.
Attachments:
You must be logged in to view attached files.2015-05-03 at 21:10 #494Profile looks fine. I think you can safely ignore the warning.
2015-05-04 at 2:32 #495SPyder4Express same messages with LCD (White LED) selected. Messages do not appear with LCD (generic).
2015-05-04 at 23:25 #496Same issue with mine. I am running at a 96Hz refresh rate using the Spyder4. I would ignore the message if its okay but unfortunately during the calibration process this message completely floods the calibration status, so I cannot monitor which phase of the process it is in, or which patch, etc. It just repeats the message “dispcal: Warning – Spyder: measuring refrash rate failed” 3 times and that is it.
2015-05-04 at 23:37 #497It’s just a cosmetic problem though. It’ll be fixed by an Argyll 1.7.1 update.
What you could try as a work-around if it bothers you not being able to monitor progress is importing the i1 Profiler colorimeter corrections (“Tools” menu) and use the white LED spectral correction instead of the Spyder4 white LED mode.
2015-05-05 at 13:07 #498@Florian
Does Spyder5 use the same “*.bin” corrections than Spyder4? I mean the same data and/or the same number of backlight types.
So if you have tested a Spyder5 for DCG3 release, we would like to know that things before buying a brand new Spyder5 colorimeter: how many backlight types, nm resolution, RGBW or just W specta…
AFAIK old Spyder4 does not have GBLED support and there is no datacolor offical installer for download yet, so I cannot check it by myself unless I buy one… but I want to know its capabilities before buying.@FirstAnonymous. Is it possible that you could check this by yourself on your Spyder5Pro? Florian had a python script to translate Spyder’s “.bin” corrections to “.CCSS” and then you could inspect it with a spreadsheet easily (CCSS is just text). It it seems too complicated, just report us backlight types and resolution by open them with a text editor. For example, spacing between measurements should like:
[…]
KEYWORD “SPEC_380”
KEYWORD “SPEC_390”
[…]
That points to 10nm resolution of samplesI mean, its a reasonable request to Spyder5 owners and will be a very useful information tha manufacrurer does not give to us. Thanks in advance
-
AuthorPosts