Razer Chroma Devices and Windows Lock | Razer Insider
Skip to main content
I know this question has come before in general/vague terms elsewhere. But I'm seeing mixed behavior when synchronizing Chroma Lighting. Razer Synapse 3 is configured and working great for the most part.



This is a brand new build; all of the latest BIOS, drivers, and Razer software are installed with Windows 10 Pro 64-bit.



Relevant system details:





X570 AORUS PRO WIFI

AMD Ryzen 7 5800X

Lian Li O11 Dynamic Razer Edition

Razer Goliathus Extended Chroma

Razer Mamba Elite

Razer Huntsman Elite



I also have these 3rd party RGB components connected via Chroma Connect:



G.Skill Trident Z Neo RGB (F4-3600C16-16GTZN)

Floe Riing RGB 360 TT Premium Edition

2 x Pure Plus 12 RGB Radiator Fan TT Premium Edition (3-Fan Pack)





When I'm logged in, all of the RGB syncs with the "Spectrum Cycling" Quick Effect -- looks great.



However, when I lock my PC (Win+L) things diverge a bit. These components remain on the "Spectrum Cycling" Quick Effect in perfect sync:



Lian Li O11 Dynamic Razer Edition

Razer Goliathus Extended Chroma

Razer Mamba Elite



The Razer Huntsman Elite keyboard is out of sync, but still on the "Spectrum Cycling" Quick Effect.



The 3rd party components stay on whatever color they were when the PC was locked.



The keyboard is probably the most troubling/bizarre one.



My question is, is there any way to address all of these anomalies on the Windows Lock screen? The goal would be for everything to stay in sync even while my PC is not actively being used.
This isn't actually a bug but a limitation. As of this time, the Chroma SDK will stop working if the computer is locked, in sleep, or hibernation mode. This is why the devices revert to their default lighting effects or even get stuck if it's caught in the middle of a transition.
Thank you for the response. So why would my "Razer Huntsman Elite" not stay in sync with the other Razer peripherals?



Regarding ChromaSDKService, is this something on the radar to come up with a solution? Regardless of how you label it -- limitation vs. bug -- the current state is definitely not desirable. Central RGB control is one of the reasons that I chose the products that I did for this build -- an inability to control them in common use scenarios is a big problem.
Blackbird714
Regarding ChromaSDKService, is this something on the radar to come up with a solution?


I do not have any information about that as of this time.



As for the out of sync devices, it could be a minor difference in timings. Devices that employ light diffusion typically have a slightly faster timing compared to those that have per-key lighting. This is why Synapse is required to be active for custom lighting to take effect.
CookiesCookie settings