Screensaver Sync Isn't Working

5 views
Skip to first unread message

Matt

unread,
Nov 9, 2025, 5:04:00 PM (2 days ago) Nov 9
to Input Director
Hi! 

I've been trying to experiment with the screen saver synchronization feature by enabling "Keep this system awake whilst Input Director is active" on all of my systems. Unfortunately, it seems inconsistent. I set all the systems to 1 minute timeout for the screensaver and sometimes it seems they follow the host system properly, other times, I'll have them bringing up their screensaver independently until I move the mouse to that screen. In other words, it is as if the computer is not being kept awake when the host is another system.

Another issue I have is if I am watching a video on a system other than the host, the host's screen saver comes on and so does the client, thus I lose my ability to watch a video unless I actively move the mouse. 

Ideally, I would love to see: all computers sync with the host screensaver policy. If any computer is doing an activity that would prevent the screensaver like a video game or watching a video, it shouldn't put the screensaver on. 

Let me know if I've done something wrong with my configuration or how I can go about fixing this. Thank you!

Shane

unread,
Nov 9, 2025, 5:33:08 PM (2 days ago) Nov 9
to Input Director
Hi Matt,

Internally, Input Director sends a message approx every 2 mins to the clients to ensure they don't start their screensavers. Try changing the screensaver timeout on your clients to 5 minutes. 

Whether a client's screensaver activates is tied to the input activity on the Director system, i.e. if it is idle, then Input Director won't stop a client initiating its screensaver. I'll have a think about the scenario of watching a video on the client system.

Regs,

Shane.

Scott Copus

unread,
Nov 9, 2025, 5:38:34 PM (2 days ago) Nov 9
to input-d...@googlegroups.com
Shane: If it helps, check out the Lithnet Idle Logoff project. It contains code to detect video and maybe audio to help determine idle time and actions. 

thanks,
Scott

--
You received this message because you are subscribed to the Google Groups "Input Director" group.
To unsubscribe from this group and stop receiving emails from it, send an email to input-directo...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/input-director/c6f575e8-f4d6-462e-a80c-2a5a99be3afen%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages