#OpenRGB 0.9 has been released! Check it out at https://openrgb.org! The full release notes are available on GitLab here:
https://gitlab.com/CalcProgrammer1/OpenRGB/-/releases/release_0.9
This update supports all of my new computer’s components. Thank everyone involved so much for this.
Just a quick question, I was right to assign 24 LEDs for the Corsair SP120 fans, right? Did a cursory search since it wasn’t on the table on the OpenRGB site.
SP120 looks to have just hub mounted LEDs. It doesn’t say on Corsair’s site but from the pictures I would guess 4 LEDs per fan. I have ML140 RGB fans in one of my builds and they also have hub mounted LEDs, 4 per fan. You can experiment with changing one LED at a time to see when you no longer see any effect from changing them and figure out the number of LEDs that way as well.
I pretty sure SP120 has 8 LEDs per fan.
Edit: Sorry the pro (3 pack with the controller), has 8
There are different skus.
Works for everything except my old Razer Core V1 with GeForce GTX 1080ti Founder’s edition.
It does detect the Core now, but it doesn’t respond to OpenRGB.
Before my Razer Abyssus Essential didn’t work but now it does!
Hmm, I did some fixups for the Core V1 this time around. I tested on Windows but not on Linux though. There were some other Razer Controller changes but they were mostly keyboard related (moving keyboard layouts to the new Keyboard Layout Manager framework). The rest were small cleanups that I didn’t think should impact functionality.
Does the Razer Core show a version or serial number in the Information tab?
The Serial: is BY1651U00100058
Hmm, ok, it looks like it is at least using the correct interface. You do have a GPU installed, right? I think I remember the Core not lighting up at least the internal zone if there’s no GPU (or maybe an incompatible one?).
I use the Nvidia GeForce 1080ti Founders Edition.
Watched the Core’s back LEDs in a darkened room and that part does respond to OpenRGB.
Just as you said, the LED strip below graphics card doesn’t respond due to the antiquity of my GPU.
Hello! I am trying to have the OpenRGB goes light off on a keyboard from a MSI laptop with Linux Mint 21.2. I can’t find a way to have to light goes off during lock screen, screensaver or don’t touch the keyboard or the mouse for a certain ammount of time. There is a way to have that work like that?
This is not a feature in OpenRGB, though it could be added as a plugin or external script. If you can detect this event in a script, you can call
openrgb --color blackfrom the script to turn off the lights.Thank you
openrgb --color blackDoesn’t work. It load the program, not change the LED color. It possible to do with$ openrgb -p Redafter I saved a profile with the color to load. Or “Off” if i want to turn off the keyboard. OpenRGB see the keyboard even if return an error with i2c that are actually loaded.<h2>WARNING:</h2><p>One or more I2C/SMBus interfaces failed to initialize.</p><p>RGB DRAM modules and some motherboards’ onboard RGB lighting will not be available without I2C/SMBus.</p><p>On Linux, this is usually because the i2c-dev module is not loaded. You must load the i2c-dev module along with the correct i2c driver for your motherboard. This is usually i2c-piix4 for AMD systems and i2c-i801 for Intel systems.</p><p>See help.openrgb.org for additional troubleshooting steps if you keep seeing this message.<br></p> Profile loading: Succeeded for MSI MysticLight MS-1563 v0001 @ HID: /dev/hidraw1 Updating mode for MSI MysticLight MS-1563 v0001 to 1
I can also read the keyboard feedback with
evemu-recordbut I lack the capability to do a scrip with this command. Anyone know how to use it?The i2c message can be ignored if all your devices use USB. I2C is pretty much only used by RGB RAM, GPUs, and some older motherboards. Mystic Light motherboards use USB.
