{"id":105748,"date":"2022-11-28T21:36:39","date_gmt":"2022-11-28T19:36:40","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/vypusk-openrgb-0-8-instrumentariya-dlya-upravleniya-rgb-podsvetkoj-periferijnyh-ustrojstv"},"modified":"2022-11-28T21:36:39","modified_gmt":"2022-11-28T19:36:40","slug":"vypusk-openrgb-0-8-instrumentariya-dlya-upravleniya-rgb-podsvetkoj-periferijnyh-ustrojstv","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/vypusk-openrgb-0-8-instrumentariya-dlya-upravleniya-rgb-podsvetkoj-periferijnyh-ustrojstv","title":{"rendered":"Release of OpenRGB 0.8, a toolkit for managing RGB lighting of peripheral devices","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
After almost a year of development, the new release of OpenRGB 0.8 has been published, an open-source toolkit for managing RGB lighting of peripheral devices. The package supports motherboards from ASUS, Gigabyte, ASRock, and MSI with RGB subsystems for case lighting, RAM modules with lighting from ASUS, Patriot, Corsair, and HyperX, graphics cards from ASUS Aura\/ROG, MSI GeForce, Sapphire Nitro, and Gigabyte Aorus, various LED strip controllers (ThermalTake, Corsair, NZXT Hue+), glowing coolers, mice, keyboards, headphones, and Razer accessories with lighting. Information about the device interaction protocol is primarily obtained through reverse-engineering proprietary drivers and applications. The code is written in C\/C++ and is distributed under the GPLv2 license. Ready builds are created for Linux (deb, rpm, appimage), macOS, and Windows. As before, all builds created after the release will have version number 0.81.
<\/center> <\/p>\n
The new release features a partially redesigned and optimized interface, added program localization including a Russian language translation (except for some functionality added during the release stabilization stage). <\/p>\n
Among the changes: <\/p>\n
\n
udev rules are now generated automatically.\n
The inpout32 library, which caused issues when running alongside certain antivirus and anti-cheat programs (Vanguard), has been replaced with WinRing0.\n
For proper operation alongside official SMBus device software on Windows, a system mutex is now used, solving most issues.\n
The list of supported devices has been expanded with a large number of graphics cards from ASUS, Gigabyte, EVGA, MSI, Gainward, and Palit. In addition, support for NVIDIA Illumination graphics cards has been added; however, at the moment, like with older NVIDIA graphics cards, it only works on Windows due to issues with i2c operation through the proprietary NVIDIA driver (the problem can be fixed by installing the beta driver). The well-known issue with MSI MysticLight motherboards has been resolved, and they are once again supported, while the list of supported motherboards has been expanded.\n
In addition to a large number of 'classic' peripherals that have been added, the list also includes NanoLeaf modular lights. For DIY devices, SRGBMods Raspberry Pi Pico can now be used, and Arduino can now be connected via i2c. <\/ul>\n
Among known issues: <\/p>\n
\n
The path for settings still should not contain non-ASCII characters. A fix was prepared but did not make it into the release to maintain compatibility with existing plugins; however, it will be included in current builds after the release.\n
It has come to light that the manufacturer of Sinowealth keyboards reused the VID\/PID values from Redragon keyboards using a different protocol. To avoid potential issues (up to bricking), the code supporting Sinowealth keyboards has now been disabled and is unsupported.\n
The 'wave' effect does not work on Redragon M711.\n
Some Corsair mice have unmarked LEDs.\n
The layout list is incomplete on some Razer keyboards.\n
The number of Asus Addressable channels may be inaccurate.\n
As usual, after an update, it is recommended to recreate existing device profiles; old ones may not work or may function incorrectly, and when updating from versions before 0.6, the plugin folder should be cleared as there was no versioning system for plugin APIs before 0.6. <\/ul>\n
![\"Release](\"\/wp-content\/uploads\/2022\/11\/b36b02bdd59160076681c29569713c28.jpg\")
<\/center> <\/p>\n