We have been re-adding these motherboards to the support list as we verify that the new code works with them.
The Mystic Light motherboard code bricked the RGB controller of some MSI motherboards. There have been two instances of hardware damage in OpenRGB's development and we've taken precautions to prevent it from happening again. While we do our best to make sure we're sending the right data, there is always some risk in sending data to hardware when we don't understand exactly how that hardware works. This project interacts directly with hardware using reverse engineered protocols. See the OpenRGB Settings page for information about the configuration file. See the Supported Devices page for the current list of supported devices. Graphical view of device LEDs makes creating custom patterns easy. 
No official/manufacturer software required. Can operate standalone or in a client/headless server configuration. .jpg "amd led control")
Connect multiple instances of OpenRGB to synchronize lighting across multiple PCs. Control lighting from third party software using the OpenRGB SDK. Set colors and select effect modes for a wide variety of RGB hardware. What if there was a way to control all of your RGB devices from a single app, on both Windows and Linux, without any nonsense? That is what OpenRGB sets out to achieve. On top of that, these apps are proprietary and Windows-only. If you want to mix and match devices, you end up with a ton of conflicting, functionally identical apps competing for your background resources. 
Every manufacturer has their own app, their own brand, their own style. One of the biggest complaints about RGB is the software ecosystem surrounding it.
0 kommentar(er)
