A new release of OpenRGB 0.7, an open source toolkit for controlling RGB lighting in peripherals, has been published. Package supports ASUS, Gigabyte, ASRock and MSI motherboards with RGB subsystem for case lighting, ASUS, Patriot, Corsair and HyperX backlit memory modules, ASUS Aura/ROG, MSI GeForce, Sapphire Nitro and Gigabyte Aorus graphics cards, various controllers LED strips (ThermalTake, Corsair, NZXT Hue+), glowing coolers, mice, keyboards, headphones and Razer backlit accessories. Information about the protocol for interacting with devices is mainly obtained through reverse engineering of proprietary drivers and applications. The code is written in C/C++ and distributed under the GPLv2 license. Ready builds are generated for Linux, macOS and Windows.
New features include:
- Added settings menu. Now, to configure specific functionality (E1.31, QMK, Philips Hue, Philips Wiz, Yeelight devices and devices controlled via a serial port, for example, based on Arduino), you do not need to edit the configuration file manually.
- A slider has been added to control the brightness of devices that have this setting in addition to the color setting.
- In the settings menu, you can now control the autorun of OpenRGB at system startup. You can specify additional actions that OpenRGB will perform on such a launch (apply profiles, launch in server mode).
- Plugins now have a versioning mechanism to avoid crashes due to using outdated builds with new versions of OpenRGB.
- Added the ability to install plugins through the settings menu.
- Added a logging console to make it easier to get crash information from new users. The log console can be enabled in the settings in the "Information" section.
- Added the ability to save settings to the device, if the device has Flash-memory. Saving is done on command only to avoid wasting the Flash resource. Previously, for such devices, saving was not performed for the same reasons.
- When new devices are detected that require dimensional adjustment (ARGB controllers), OpenRGB will remind you to do so.
Added support for new devices:
- Extended list of detected GPUs (Gigabyte, ASUS, MSI, EVGA, Sapphire, etc.)
- Expanded the list of supported MSI Mystic Light motherboards (due to the peculiarities of this series of motherboards, untested devices remain unavailable by default to avoid RGB controller softlock)
- Fixed issues with Logitech mice found in version 0.6.
- Added operating modes Logitech G213
- Philips Hue (including Entertainment mode)
- Corsair Commander Core
- HyperX Alloy Origins Core
- Alienware G5 SE
- ASUS ROG Pugio (ASUS mouse support improved overall)
- ASUS ROG Throne headset stand
- ASUS ROG StrixScope
- New devices have been added to the Razer Controller.
- Obinslab Anne Pro 2
- ASUS Aura SMBus controller renamed to ENE SMBus controller (more correct OEM name), the controller itself is somewhat expanded: Added support for ASUS 3xxx series GPUs (ENE controller) and XPG Spectrix S40G NVMe SSD (ENE controller, requires running as Administrator/root for work). Fixed controller conflict with Crucial DRAM.
- HP Omen 30L
- Cooler Master RGB Controller
- Cooler Master ARGB Controller direct mode
- Keyboard
- Blinkinlabs BlinkyTape
- Alienware AW510K Keyboard
- Keyboard Corsair K100
- SteelSeries Rival 600
- SteelSeries Rival 7×0
- Logitech G915, G915 TKL
- Logitech G Pro
- Sinowealth 0016 keyboard
- Fixed flickering on HyperX devices (especially HyperX FPS RGB)
- All Crucial DRAM addresses are discoverable again, this will most likely solve the problem of incomplete stick detection.
- GPU Gigabyte RGB Fusion 2
- GPU EVGA 3xxx
- EVGA KINGPIN 1080Ti and 1080 FTW2
- ASUS Strix Evolv Mouse
- MSI GPU direct mode
Issues fixed:
- Fixed USB device detection issues related to interface/page/usage values differing between OS
- Key placement maps (layouts) have been fixed on many devices.
- Improved log formatting
- Fixed WMI multiple initialization issue (caused inability to rediscover SMBus devices)
- Slightly improved user interface
- Fixed application crashes when connecting Logitech mice (G502 Hero and G502 PS)
- Fixed application crashes when unloading plugins
Known Issues:
- Some of NVIDIA's recently added GPUs (ASUS Aura 3xxx, EVGA 3xxx) do not work under Linux due to flaws in the I2C/SMBus implementation in NVIDIA's proprietary driver.
- Wave effect does not work on Redragon M711.
- Indicators of some Corsair mice are not signed.
- Some Razer keyboards do not have layouts.
- In some cases, the number of Asus Addressable channels may not be correctly determined.
When upgrading to a new version, there may be compatibility issues with profile and dimension files, and they will need to be recreated. When migrating from versions prior to 0.6, OpenRazer (OpenRazer-win32) should also be disabled in the settings to enable the built-in Razer controller, which supports more devices.
Source: opennet.ru