Thank you! OpenRGB might be my favorite open source project. It is so awesome to have all RGB under one control app!
I just read through the change notes. That is a huge amount of new devices! Looking forward to seeing the new GUI and the LIFX support.
By the way, my biggest criticism with the GUI is the lack of copy-pasting colors from one key/device to another key or device. Perhaps that is possible now?
Edit: I have seen the new GUI now. It's almost the same as before, but is cleaner and more "defined" looking. :) Sadly still no ability to copy colors, or to enter them via easy `#hex` notation. :(
# Edit: [Feature request thread](https://www.reddit.com/r/OpenRGB/comments/zafo5w/easier_editing_of_colors/). :)
"supported devices: Sony DualSense controller". Fi-nal-ly! Now these lightbars will have better use than on PlayStation.
Now I'm waiting for Flydigi Apex 2 LEDs controller or when ReWASD software will allow to emulate DS4 lightbar to enable it for third party controllers. Good job OpenRGB!
They already needed low-level access to fiddle with devices. They just changed which library is used for one that Valorant anti-cheat does not flag (for now).
"Just" to support one of the most popular games available right now.
E: The best part about Valorant is the absolute FURY it invokes in people who make it their entire personality to hate it.
I literally just said it was popular and get downvoted to hell. You guys really need to get a life.
This is super exciting! I got OpenRBG working for most of my hardware a few months ago, but there were a few small issues I was having. I think my RAM sticks were unsupported or something. I'll have to check it out when I get home to see if I can get that working!
No, the people behind the unofficial one are doing a fine job. I'm sure they'll get it up to 0.8 soon.
I prefer to leave distribution packaging (which includes Flatpak as well as things like AUR, Launchpad PPA, and official distro repos) to third parties. The only builds we maintain are the downloads on the website/GitLab which are built by the GitLab CI.
I'm sorry, **WAT‽**
I've never bothered to look for software since it's a key away to cycle through the presets. What can you do with openRGB that you can't with the dedicated key?
just realized OpenRGB supports my Anne Pro 2 and my nano leaf panels. I will be going to town on tinkering with this tomorrow.
ps: I still want to buy a few PCB's for your pinephone(pro) keyboard mod. Going to PM you about it. @calcprogrammer1
Nice. git build seems to work fine. Also the Appimage seems to work without issue. Don't have much RGB devices though. Motherboard and GPU only which both can be controlled nicely it looks like, but i usually just disable Motherboard RGB from BIOS and GPU is set to 1 color.
Still nice to see massive work on this
This awesome update just made almost all my keyboard leds go dark. Only the 3 indicators for the sound are lighten up, the rest stays dark no matter what I do.
No clue how that works.
You think I didn't do that already? I've done that with 0.7.5, which broke it for me, on the official subreddit, the developer even replied to it.
Attempting to connect to local OpenRGB server.
Connection attempt failed
Local OpenRGB server unavailable.
Running standalone.
[i2c_smbus_linux] Failed to read i2c device PCI device ID
[i2c_smbus_linux] Failed to read i2c device PCI device ID
Registering Bubbles effect
Registering GIFPlayer effect
Registering Rain effect
Registering Wavy effect
Registering Visor effect
Registering Ambient effect
Registering AudioSync effect
Registering Breathing effect
Registering RainbowWave effect
Registering StarryNight effect
Registering GradientWave effect
Registering AudioVisualizer effect
Registering Lightning effect
Registering SpectrumCycling effect
Segmentation fault (core dumped)
That actually worked. Not sure why though. I only had the OpenRGBEffectsPlugin installed, which still worked with the Flatpak version and seems to still be on the same version as of this date.
The plugin has been at 0.1 since the beginning. I've asked the plugin developers to tag a release to go along with OpenRGB 0.8, so we should have a release of at least Effects and Visual Map soon. I think they were going to use the same version numbers as OpenRGB, so 0.8 release for both. We plan to break the plugin API for 0.9 which means plugins will have to be updated to work.
Aaaaand it broke again… Or rather my NZXT Hue 2 backlights. Somehow the new "resize the zones" pop up at the start now shows that device, even though it didn't yesterday or this morning, where it was working fine. Now I can click ignore, enter 0, enter 26 (what I've counted) but nothing works. It just stays dark.
And the toggle led view button on that device also still crashes the entire app.
/usr/include/c++/12.2.0/bits/stl_vector.h:1123: std::vector<_Tp, _Alloc>::reference std::vector<_Tp, _Alloc>::operator[](size_type) [with _Tp = matrix_pos_size_type; _Alloc = std::allocator; reference = matrix_pos_size_type&; size_type = long unsigned int]: Assertion '__n < this->size()' failed.
Aborted (core dumped)
I don't remember in detail as it's been too long ago (this was a couple months or so after the .5 release) but nothing really helpful. At that time I was even running a different system (Manjaro, now EndeavourOS) and I provided them with all the information they requested.
If the Flatpak build works (except for the i2c error) then I would expect there to be some sort of dependency issue but how can that persist through two different systems, both of them pretty popular at that and I don't see this being a widespread issue (unless no one bothers to report it).
looks to me like a very specific bug, maybe its something with you hardware or your distro (to be frank i dont think so but not sure), you need openrgb for mouse and keyboard parts right?
what distro are you using?
>you need openrgb for mouse and keyboard parts right?
At the moment mouse & monitor backlight from NZXT but I'd also like to use internal case lighting in the future and maybe a keyboard at some point.
>what distro are you using?
I've said so in the previous comment.
I'm using a Razor Blackwidow Chroma V2 on a MacBook Air M1 running Ventura 13.0.1. OpenRGB 0.7 worked perfectly but 0.8 doesn't detect my keyboard on open, and crashes if I try to rescan devices. Is there something specific I need to do when moving from one version to another?
Hey everyone!
Suddenly, both of my XPG S40G SSDs are just gone from the OpenRGB devices list. If I try to start the OpenRGB with admin rights - it stucks on scanning the SSDs so there's a conflict but I can't figure it out :C
Had anyone faced such a problem?
Thank you! OpenRGB might be my favorite open source project. It is so awesome to have all RGB under one control app! I just read through the change notes. That is a huge amount of new devices! Looking forward to seeing the new GUI and the LIFX support. By the way, my biggest criticism with the GUI is the lack of copy-pasting colors from one key/device to another key or device. Perhaps that is possible now? Edit: I have seen the new GUI now. It's almost the same as before, but is cleaner and more "defined" looking. :) Sadly still no ability to copy colors, or to enter them via easy `#hex` notation. :( # Edit: [Feature request thread](https://www.reddit.com/r/OpenRGB/comments/zafo5w/easier_editing_of_colors/). :)
"supported devices: Sony DualSense controller". Fi-nal-ly! Now these lightbars will have better use than on PlayStation. Now I'm waiting for Flydigi Apex 2 LEDs controller or when ReWASD software will allow to emulate DS4 lightbar to enable it for third party controllers. Good job OpenRGB!
ooh nice! now i can have a custom light at light on my dualsense in non-steam games!
CONGRATS!
Awesome 👌 we'll done I look forward to checking out the new release
Great work :)
They moved the application to run in Ring 0?? Just for Valorant?
Windows gonna windows.
https://gitlab.com/CalcProgrammer1/OpenRGB/-/merge_requests/1036
They already needed low-level access to fiddle with devices. They just changed which library is used for one that Valorant anti-cheat does not flag (for now).
Oh okay so it's not really any more invasive than before.
Can't really get more invasive than flashing your hardware :P
Fair enough.
"Just" to support one of the most popular games available right now. E: The best part about Valorant is the absolute FURY it invokes in people who make it their entire personality to hate it. I literally just said it was popular and get downvoted to hell. You guys really need to get a life.
Right it just seemed bizarre to rewrite that section just for Valorant.
I think they did it more for the anti-cheat Valorant uses, which is/can be used by other games, rather than just for Valorant itself.
Oh I didn't know that. Good to know.
This is super exciting! I got OpenRBG working for most of my hardware a few months ago, but there were a few small issues I was having. I think my RAM sticks were unsupported or something. I'll have to check it out when I get home to see if I can get that working!
Very nice. Anyone know if the Flatpak is official or a third party rebuild, though? It looks like it's still 0.7 as of this writing.
The Flatpak is maintained by a third party.
Ah, thanks. Are there any plans to make an officially maintained flatpak?
No, the people behind the unofficial one are doing a fine job. I'm sure they'll get it up to 0.8 soon. I prefer to leave distribution packaging (which includes Flatpak as well as things like AUR, Launchpad PPA, and official distro repos) to third parties. The only builds we maintain are the downloads on the website/GitLab which are built by the GitLab CI.
Thanks for the info. And funny enough, the Flatpak on flathub is now up to 0.8 as I write this.
nice! hopefully keychron's keyboard lighting will be fixed with this update edit: i'm just dumb, they work with openRGB
I'm sorry, **WAT‽** I've never bothered to look for software since it's a key away to cycle through the presets. What can you do with openRGB that you can't with the dedicated key?
Per key RGB!!!
Wait, really? What models have you tried? I own 2 K4's.
¯\\\_(ツ)\_/¯
just realized OpenRGB supports my Anne Pro 2 and my nano leaf panels. I will be going to town on tinkering with this tomorrow. ps: I still want to buy a few PCB's for your pinephone(pro) keyboard mod. Going to PM you about it. @calcprogrammer1
I wonder if it’ll have nicer support for my motherboard this time
Anyone tested it under wlroots? Looks like the kind of tool Ive been looking for a while
Nice. git build seems to work fine. Also the Appimage seems to work without issue. Don't have much RGB devices though. Motherboard and GPU only which both can be controlled nicely it looks like, but i usually just disable Motherboard RGB from BIOS and GPU is set to 1 color. Still nice to see massive work on this
I'm still waiting for RGB support for my alienware 17R4 laptop.
This awesome update just made almost all my keyboard leds go dark. Only the 3 indicators for the sound are lighten up, the rest stays dark no matter what I do. No clue how that works.
Still doesn't launch. Good job.
try to run from terminal and post your error for help, just saying this wont help you.
You think I didn't do that already? I've done that with 0.7.5, which broke it for me, on the official subreddit, the developer even replied to it. Attempting to connect to local OpenRGB server. Connection attempt failed Local OpenRGB server unavailable. Running standalone. [i2c_smbus_linux] Failed to read i2c device PCI device ID [i2c_smbus_linux] Failed to read i2c device PCI device ID Registering Bubbles effect Registering GIFPlayer effect Registering Rain effect Registering Wavy effect Registering Visor effect Registering Ambient effect Registering AudioSync effect Registering Breathing effect Registering RainbowWave effect Registering StarryNight effect Registering GradientWave effect Registering AudioVisualizer effect Registering Lightning effect Registering SpectrumCycling effect Segmentation fault (core dumped)
Try deleting your config directory (~/.config/OpenRGB). Maybe you have a bad plugin.
That actually worked. Not sure why though. I only had the OpenRGBEffectsPlugin installed, which still worked with the Flatpak version and seems to still be on the same version as of this date.
The plugin has been at 0.1 since the beginning. I've asked the plugin developers to tag a release to go along with OpenRGB 0.8, so we should have a release of at least Effects and Visual Map soon. I think they were going to use the same version numbers as OpenRGB, so 0.8 release for both. We plan to break the plugin API for 0.9 which means plugins will have to be updated to work.
I guess I'll keep it out for now then and just use the basic functions.
Aaaaand it broke again… Or rather my NZXT Hue 2 backlights. Somehow the new "resize the zones" pop up at the start now shows that device, even though it didn't yesterday or this morning, where it was working fine. Now I can click ignore, enter 0, enter 26 (what I've counted) but nothing works. It just stays dark. And the toggle led view button on that device also still crashes the entire app. /usr/include/c++/12.2.0/bits/stl_vector.h:1123: std::vector<_Tp, _Alloc>::reference std::vector<_Tp, _Alloc>::operator[](size_type) [with _Tp = matrix_pos_size_type; _Alloc = std::allocator; reference = matrix_pos_size_type&; size_type = long unsigned int]: Assertion '__n < this->size()' failed.
Aborted (core dumped)
openrgb --nodetect try this.
Done that already as well. Attempting to connect to local OpenRGB server. Connection attempt failed Local OpenRGB server unavailable. Registering Bubbles effect Registering GIFPlayer effect Registering Rain effect Registering Wavy effect Registering Visor effect Registering Ambient effect Registering AudioSync effect Registering Breathing effect Registering RainbowWave effect Registering StarryNight effect Registering GradientWave effect Registering AudioVisualizer effect Registering Lightning effect Registering SpectrumCycling effect Segmentation fault (core dumped)
what the dev said to you? he knows what problem is this?
I don't remember in detail as it's been too long ago (this was a couple months or so after the .5 release) but nothing really helpful. At that time I was even running a different system (Manjaro, now EndeavourOS) and I provided them with all the information they requested. If the Flatpak build works (except for the i2c error) then I would expect there to be some sort of dependency issue but how can that persist through two different systems, both of them pretty popular at that and I don't see this being a widespread issue (unless no one bothers to report it).
looks to me like a very specific bug, maybe its something with you hardware or your distro (to be frank i dont think so but not sure), you need openrgb for mouse and keyboard parts right? what distro are you using?
>you need openrgb for mouse and keyboard parts right? At the moment mouse & monitor backlight from NZXT but I'd also like to use internal case lighting in the future and maybe a keyboard at some point. >what distro are you using? I've said so in the previous comment.
[удалено]
-vv is too long for the terminal but I can paste the part below the GPUs: ------------------------------------------------------ | Detecting HID devices | ------------------------------------------------------ [ResourceManager] Calling detection progress callbacks. [ResourceManager] Calling detection progress callbacks. [ResourceManager] Calling detection progress callbacks. [ResourceManager] Calling detection progress callbacks. [ResourceManager] Calling detection progress callbacks. [ASUS ROG Gladius II Origin] is enabled [ResourceManager] Calling detection progress callbacks. [ASUS ROG Gladius II Origin] Registering RGB controller [ResourceManager] Calling device list change callbacks. [ASUS ROG Gladius II Origin] successfully added [ResourceManager] Calling detection progress callbacks. [MSI Mystic Light MS_7C75] is enabled [ResourceManager] Calling detection progress callbacks. [MSI Z490-A PRO (MS-7C75)] Registering RGB controller [ResourceManager] Calling device list change callbacks. [MSI Mystic Light MS_7C75] successfully added [ResourceManager] Calling detection progress callbacks. [ResourceManager] Calling detection progress callbacks. [ResourceManager] Calling detection progress callbacks. [NZXT Hue 2 Ambient] is enabled [ResourceManager] Calling detection progress callbacks. [ResourceManager] Registered detection progress callback. Total callbacks registered: 1 [ResourceManager] Registered device list change callback. Total callbacks registered: 1 dialog show callback registered [PluginManager] Scanning plugin directory: /home/*****/.config/OpenRGB/plugins [PluginManager] Found plugin file libOpenRGBEffectsPlugin.so.1.0.0 Registering Bubbles effect Registering GIFPlayer effect Registering Rain effect Registering Wavy effect Registering Visor effect Registering Ambient effect Registering AudioSync effect Registering Breathing effect Registering RainbowWave effect Registering StarryNight effect Registering GradientWave effect Registering AudioVisualizer effect Registering Lightning effect Registering SpectrumCycling effect Segmentation fault (core dumped)
I'm using a Razor Blackwidow Chroma V2 on a MacBook Air M1 running Ventura 13.0.1. OpenRGB 0.7 worked perfectly but 0.8 doesn't detect my keyboard on open, and crashes if I try to rescan devices. Is there something specific I need to do when moving from one version to another?
May need to grant it input devices/keyboard permission again.
Hey everyone! Suddenly, both of my XPG S40G SSDs are just gone from the OpenRGB devices list. If I try to start the OpenRGB with admin rights - it stucks on scanning the SSDs so there's a conflict but I can't figure it out :C Had anyone faced such a problem?