Setting color to 255,0,225 ends up setting the color to red #37
Unanswered
AidenJames1995
asked this question in
Q&A
Replies: 1 comment 2 replies
-
Well I think I fixed that, apparently my motherboard only likes direct mode. Now I'm trying to get my RAM to set a color, but nothing:
RAM sticks are G.Skill TridentZ Royal |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm just getting started with OpenRGB and OpenRGB-Python and I'm having problems getting something as simple as setting a color programmatically to stick.
Here's my code:
`from openrgb import OpenRGBClient
from openrgb.utils import RGBColor, DeviceType
client = OpenRGBClient()
client.clear() # Turns everything off
motherboard = client.get_devices_by_type(DeviceType.MOTHERBOARD)[0]
motherboard.set_color(RGBColor(255,0,255))
motherboard.set_mode("static")
`
Admittingly, I'm not the best with python, I'm more a PHP programmer, but I don't see anything wrong with the code here. When I run this, the motherboard and the devices plugged into the addressable header on the board will flash purple for about 0.25 second and then fall back to red. If I manually set a color in OpenRGB then run this, it will set it to the color selected in OpenRGB after turning everything off for a brief moment. For whatever reason it seems to be tied to set_mode. When ever I run this without that call it seems to works fine.
Beta Was this translation helpful? Give feedback.
All reactions