Yahoo Groups archive

Datacolor User to User Support Group.

Index last updated: 2026-04-28 23:18 UTC

Message

Re: [datacolor_group] SpyderUtility preferences

2017-03-04 by David Miller

> On Mar 3, 2017, at 12:08 PM, lcunning@... [datacolor_group] <datacolor_group@yahoogroups.com> wrote:
> 
> I purchased and installed Spyder5Pro earlier this week, and used it to calibrate both Dell monitors in a dual-monitor system (Windows 10 in case it makes any difference). I'm very happy with the results. The two monitors (for the first time in a couple of years) match each other in terms of brightness, contrast, and color balance, and prints that come out of my Canon Pro-100 now closely match what I see on my monitor. So far, so good.
> 
> My questions refer to the SpyderUtility widget that now sits in the System Tray, and its preference settings. Can anyone explain what these settings do? I have a vague idea, but I would appreciate some clarification. There's nothing in the manual regarding these settings, and I couldn't find anything on the Datacolor Web site about them.
> 
> Here are the settings I'm referring to:
> 
> General: Dialogs will be automatically dismissed after:
> The settings range from Never to 8 Hours. What dialogs, the ones that appear right after booting or rebooting the PC, or something else?
> 
> 
This will be for any dialogs that SpyderUtility might put up on the screen, while it’s running. (Display
recalibration alert, for example). The idea is to prevent them from staying on the screen indefinitely.

> Room Light: Check Room Light Level Every:
> 
> I'm guessing that setting this to anything but Never requires keeping the Spyder hardware connected via USB, which I don't plan to do. Is this correct?
> 
> 
> 
Yes, that’s correct. If the Spyder isn’t plugged in, then the periodic measurement of ambient
room light (if configured to be done periodically) is automatically disabled. When the Spyder
is plugged back in again, this will pick up again automatically if it’s configured for something
other than “Never”.

> Video Card: Load Video Card LookUp Table (LUT) Every:
> 
> The settings range from Never to 60 Minutes. Am I correct in thinking that the software reloads the LUT periodically in case Windows or other software messes with the color settings? Any recommendations as to what setting to use? Is there any penalty for reloading the LUT more often?
> 
> 
> 
Yes, that’s exactly how it works. The default of 1 minute should be “fine”. At first glance, it sounds
like this might be “too frequent”, but the fact is, if your video card LUTs get overwritten for any
reason, then your display will suddenly go “out” of calibration and it won’t be “fixed” until a time
period as long as, potentially, that full minute. (depending on “luck” and when in the default 1-minute
reload cycle that your LUTs were overwritten).

You could set it to a longer value if you like; it helps to be aware of what calibrated vs. uncalibrated looks
like, and how important in your normal workflow it is to ensure that your display “is” in calibration.

There’s no meaningful penalty for reloading the LUT more frequently; it’s a very simple system call to
do this. There’s a tiny bit of work that needs to be done to load the data from the profile, pass it to Windows
and have it refresh the video card LUTs but it’s so small as to be irrelevant. There are other, more complex
things that SpyderUtility does in the background while it’s running that are more involved than reloading
the video card LUTs.

IF you’ve applied your “fix” to Windows AND if you’re confident that Windows will be doing the right
thing itself (no need for SpyderUtility to do this periodically), then you can set it to “Never”, and, still
keep SpyderUtility running for the other reasons mentioned in my last email (for example, if you’re
using the Room Light Switching feature in either Pro+ or Elite+).

> Recalibration: Check Recalibration Every:
> 
> The settings range from Never to 6 Months. What does this check for, and how often should this be checked? I'm having the most difficulty wrapping my head around this one.
> 
> 
> 
> Recalibration: Notify if display has not been recalibrated (ReCAL) within the last:
> 
> The settings range from Never to 6 Months. I seem to remember setting this when I ran the original calibration. Is this the same thing as I saw in the main program?
> 
> 
> 
Yes. The original setting for that preference is based on what you entered at the time you calibrated
the display. This is a way that you can override it.

> Startup: Display Startup Dialogs:
> 
> I think I've figured this one out on my own. 
> 
> 
> 
That one’s a bit more obvious. :-)

> One last, generic question: Ever since SpyderUtility began living in the System Tray, I've noticed that periodically, my screensaver mysteriously stops (and the monitors come back to life) without any PC activity to cause it. This change coincided with my installing and running the Spyder software. Could SpyderUtility be causing this?
> 
> 
> 
I could look into that. I haven’t heard any reports of it, but since it’s an application that’s running in the
background and since it periodically (and by default, frequently) reloads the video card LUTs from what’s
stored in the calibration profile, I suppose it’s “possible” that Windows could interpret this as user activity,
even though it’s not “user activity”… your mouse and keyboard aren’t being touched… so, hmmm.

I’d -think- that if this was the problem, then as soon as the first default interval to reload the video LUTs
goes by, and this happens, that your displays would wake up again. Is that what’s going on, or (my guess,
otherwise you’d have said your screensaver fails to work and your system always wakes up almost immediately!)
is it much more intermittent than that?

> Thanks in advance for any guidance regarding all of this!
> 

You’re welcome! Sorry for not answering your question sooner - I’d seen it late yesterday afternoon
but didn’t have time to respond until now.

Best regards,

David Miller
Manager/Lead Developer, Consumer Graphics Software
Datacolor

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.