mastodon 4.7.3Open source RGB lighting control that doesn't depend on manufacturer software. Created by @CalcProgrammer1@mastodon.social.
#OpenRGB 1.0 Released!
This monumental release encompasses nearly 3 years of work since the 0.9 release, and a year's worth of core reworks since the 1.0rc2 release candidate last year. Tons of new device support, an overhauled profile system, the option to cleanly run as a background service, PawnIO, Qt6, and much more!
Downloads for OpenRGB 1.0 are live on https://openrgb.org, plugin 1.0 builds will be coming online soon.
After a week of the general public running the new version, some minor bugs and annoyances have been brought up that weren't caught in testing. I am planning to do a 1.1 bugfix release sometime in October to address as many of the 1.0 bugs as possible. Notably, the checkbox for "Do Not Show Again" dialogs does not work properly, the SDK server doesn't respond to the plugin list requests when in service mode, some less than optimal default settings need tweaking.
The #OpenRGB Effects Plugin is now available on #Flathub! If you've installed OpenRGB from Flathub, you can now install the Effects Plugin from there as well, and new installations appear to include it by default.
https://flathub.org/en/apps/org.openrgb.OpenRGB.Plugin.Effects
My #PawnIO module for the #Valve #SteamMachine LED strip just got accepted and into a signed release. Support for the Steam Machine's LEDs under #Windows is now available in #OpenRGB pipeline/experimental builds and will be in next week's OpenRGB 1.0 release!
I've made an OpenRGB 1.0 announcement and what's new video that goes through some of the new features.
Support for the #Valve #SteamMachine under #Linux has been merged into #OpenRGB. This relies on the leds-valve kernel module that is included in the SteamOS kernel. A DKMS package is available to install this kernel module on #Arch and #Debian distros:
https://gitlab.com/CalcProgrammer1/leds-valve-dkms
or AUR leds-valve-dkms-git
There was a bug that affected quite a bit of the effects plugin in the original 1.0 build that I posted, since not many people had downloaded it yet I've pulled the release back and am re-building it with the fix. The updated release links will be live on the site once that's done.
Postponing the #OpenRGB 1.0 release by one week, I wanted to release it this weekend but there is a potential issue with certain MSI motherboards I want to investigate and the board I ordered to test it on won't get here until next Tuesday.
OpenRGB 1.0rc3 Hotfix 1 just released. This is a security hotfix version that fixes a vulnerability when running as a background/system service. Profile names are now sanitized, the service now defaults to localhost only, and there is a size cap on server/client packets. These issues have already been fixed in master/pipeline versions.
https://codeberg.org/OpenRGB/OpenRGB/releases/tag/release_candidate_1.0rc3.1
Tentative #OpenRGB 1.0 release date is over Labor Day weekend, probably either Friday Sep. 4 or Saturday Sep. 5 so that I have some time after the release to make some 1.0 related content (social posts and YouTube videos) over the long weekend.
I think we are in a pretty good state now, just want some remaining device support to get merged and a window for developers to submit final cleanups to controllers.
Not guaranteeing anything though, it could slip.
Spent the weekend figuring out how to package #OpenRGB plugins as #Flatpak extensions so that the OpenRGB Flatpak can have easily installed plugins. I haven't submitted the plugins to Flathub yet but I plan to. Also waiting to see if Flathub will grant an exception for OpenRGB to read the host /usr and /etc filesystems to perform its udev rules check properly on the Flatpak version.
I made an OpenRGB 1.0 Windows installation video showing off how to install OpenRGB as a background service with PawnIO and the Effects Plugin.
Merged a change to migrate old binary .orp format profiles from OpenRGB 1.0rc3 and earlier to the new .json format used by OpenRGB pipeline/git. It will upload the migrated profile to the background service if in service/client mode. Considering a plugin API breaking change to allow plugins to migrate their old internal configs/profiles into new OpenRGB profiles, which means pipeline users may need to update their plugins soon.
We've figured out how to properly identify #Corsair RGB DRAM types! There is an identification packet that can be requested from the RGB controller on each DRAM module containing a VID/PID identifier, firmware version, and protocol version. There's an open merge request to test these changes. It successfully detected my Vengeance RGB Pro DDR4 and Vengeance RGB DDR5. Would be great to get more testers!
https://gitlab.com/CalcProgrammer1/OpenRGB/-/merge_requests/3241
In reaction to the impending invasion of privacy #Discord wishes to force upon all of its userbase, along with a desire to use open source and community-run platforms over proprietary, VC-backed platforms, I have created an #OpenRGB guild on #Spacebar. If you don't know, Spacebar is an open source, self-hostable Discord alternative. Their intention is to replicate Discord's API and user experience.
https://fermi.chat/invite/36WvoE?instance=https%3A%2F%2Fspacebar.chat
Hotplug support has been merged into the #OpenRGB next branch. This is still quite experimental and subject to change, but I've created AUR packages openrgb-next-git and openrgb-plugin-effects-next-git for anyone who wants to live on the edge and test out the new functionality. This new package depends on hidapi-hotplug-git which is another new package for our hidapi fork with the hotplug patches. The GitLab CI for the next branch has Windows, AppImage, Debian, Fedora, and MacOS builds.
#OpenRGB's Lemmy community has moved! The new home is https://lemmy.today/c/OpenRGB! Formerly we were on lemmy.ml, but that instance has slowly been drifting away from the general purpose instance hosted by the Lemmy devs to one of some rather extremist viewpoints. I've been on lemmy.today for a year or so and have found it a pretty solid instance, plus they have the old Reddit style mlmym interface at https://lemmy.today/c/OpenRGB!
OpenRGB contributor k1-801 has been working on and maintaining a USB HID hotplug branch for years, but concerns with the required patches not making it upstream along with many other internal API and SDK issues regarding dynamically adding and removing devices meant it didn't get merged.
I've decided we will fork hidapi if we must, it is going into 1.0 final. I'm working on pulling in these changes in the next branch.
Check out this demo!
https://www.youtube.com/watch?v=8QTcOJ1HQoI
More updates soon.
@westhisup@gamepad.club The flashing LEDs thing might mean you haven't sized your ARGB header zones properly, as LEDs outside the configured range can flicker or display random colors.