-
-
Notifications
You must be signed in to change notification settings - Fork 525
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Huntsman V2 asynchronous colours #2218
Comments
Since OpenRazer is using the firmware's "spectrum" (rather then all being driven by software), I guess it a side effect that not all firmware have an equal synchronicity. With your workaround to restart the effect, since the device is already running "spectrum", you might need to switch them to a different effect (like static) and then back to spectrum. Alternate solution is taking inspiration from Razer Synapse -- in OpenRazer's case, write a Python script using the API to loop each device; set a colour for each column/row; draw; 'sleep'; change hue; repeat - essentially creating a software version of spectrum. If anyone has built such script, it would make a good example. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Distribution
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=23.10
DISTRIB_CODENAME=mantic
DISTRIB_DESCRIPTION="Ubuntu 23.10"
I got the following devices:
Bus 001 Device 009: ID 1532:026c Razer USA, Ltd Razer Huntsman V2
Bus 001 Device 006: ID 1532:0c02 Razer USA, Ltd Goliathus Extended
Bus 001 Device 008: ID 1532:0099 Razer USA, Ltd Razer Basilisk V3
I run them all synchronised with spectrum. After a while, however, the Huntsman V2 is no longer synchronised and shows different colours than the Goliathus Extended and Basilisk V3. I tried to create a cronjob with razer-cli -e spectrum, but it does not work.
The text was updated successfully, but these errors were encountered: