You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 

15 KiB

OpenRGB

Visitors Pipeline Status

Visit our website at https://openrgb.org!

One of the biggest complaints about RGB is the software ecosystem surrounding it. Every manufacturer has their own app, their own brand, their own style. If you want to mix and match devices, you end up with a ton of conflicting, functionally identical apps competing for your background resources. On top of that, these apps are proprietary and Windows-only. Some even require online accounts. 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. One app to rule them all.

Features

  • Set colors and select effect modes for a wide variety of RGB hardware
  • Save and load profiles
  • Control lighting from third party software using the OpenRGB SDK
  • Command line interface
  • Connect multiple instances of OpenRGB to synchronize lighting across multiple PCs
  • Can operate standalone or in a client/headless server configuration
  • View device information
  • No official/manufacturer software required
  • Graphical view of device LEDs makes creating custom patterns easy

Supported Devices

Configuration

WARNING!

This project interacts directly with hardware using reverse engineered protocols. 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.

There have been two instances of hardware damage in OpenRGB's development and we've taken precautions to prevent it from happening again.

  • The Mystic Light motherboard code bricked the RGB controller of some MSI motherboards. The code was disabled and reworked. We have been re-adding these motherboards to the support list as we verify that the new code works with them. Affected boards can be unbricked with a Nuvoton Nu-Link adapter.
  • There were reports of bricked Gigabyte Aorus Z390 motherboards caused by dumping SMBus address 0x68 in an attempt to reverse engineer the RGB. Due to this, the SMBus Tools page on OpenRGB is hidden by default now as it has no real use to non-developers.

OpenRGB_Device_View

Windows

  • Pre-built binaries are available under the Releases section on GitLab. - You will need the Microsoft Visual 2019 C++ runtime installed. You can get it here
  • If you wish to build the application yourself:
    1. Download the latest Visual Studio Community Edition and Qt Creator.
    2. Open the OpenRGB.pro project in Qt Creator.
    3. Use the MSVC compiler kit, either 32- or 64-bit, to build the application.
    4. Run the project from Qt Creator. If you want to use your custom build standalone, download the latest matching Release package and replace the OpenRGB.exe in it with your new build.
  • You must run the application as Administrator the first time to allow InpOut32 to set up. It can be run as a normal user afterwards

USB Access

  • Early versions of OpenRGB used the WinUSB driver, installed using Zadig. This is no longer required, and you need to uninstall the WinUSB driver if you previously installed it. You can uninstall the WinUSB driver by following this guide.

Linux

  • Pre-built binaries in AppImage format are available under the Releases section on GitLab.
  • You can build the project using Qt Creator or on the command line.
    1. Install build dependencies
      • Debian/Ubuntu: sudo apt install git build-essential qtcreator qtbase5-dev qtchooser qt5-qmake qtbase5-dev-tools libusb-1.0-0-dev libhidapi-dev pkgconf libmbedtls-dev
      • Debian (before bullseye) or Ubuntu (before 21.04): sudo apt install git build-essential qtcreator qt5-default libusb-1.0-0-dev libhidapi-dev pkgconf libmbedtls-dev
      • Fedora: sudo dnf install automake gcc-c++ qt5-qtbase-devel hidapi-devel libusbx-devel mbedtls-devel
    2. git clone https://gitlab.com/CalcProgrammer1/OpenRGB
    3. cd OpenRGB
    4. qmake OpenRGB.pro
      • On Fedora, replace qmake with qmake-qt5
    5. make -j$(nproc)
  • Run the application with ./openrgb
  • You can also build a Debian package (.deb) from this source code with dpkg-buildpackage -us -B

SMBus Access

  • SMBus access is necessary for controlling RGB RAM and certain motherboard on-board LEDs.
  • If you are not trying to use OpenRGB to control RGB RAM or motherboard LEDs, you may skip this section.
  • ASUS and ASRock motherboards have their RGB controller on an SMBus interface that is not accessible by an unmodified Linux kernel (for now). I am working on getting patches submitted upstream, but for now you must patch your kernel with the provided OpenRGB.patch file.
  • Allowing access to SMBus:
    1. Load the i2c-dev module: sudo modprobe i2c-dev
    2. Load the i2c driver for your chipset:
      • Intel:
        • sudo modprobe i2c-i801
        • sudo modprobe i2c-nct6775 - Secondary controller for motherboard LEDs (requires patch)
      • AMD:
        • modprobe i2c-piix4
        • Unmodified kernel will have one interface, patched kernel will have two. The first at 0x0B00 and the second at 0x0B20. The 0x0B20 interface is for motherboard LEDs.
  • Instructions on patching the kernel:
  • Some Gigabyte/Aorus motherboards have an ACPI conflict with the SMBus controller.
    • Add acpi_enforce_resources=lax to your kernel command line and reboot. The controller should now show up.
      • On Fedora, install grubby and then execute this.
      grubby --update-kernel=ALL --args="acpi_enforce_resources=lax"
      
      • If you want to check if the kernel was loaded with this option you can execute this command from the terminal once you've rebooted.
        cat /proc/cmdline
      
  • You'll have to enable user access to your SMBus if you don't run as root.
    • List all SMBus controllers: sudo i2cdetect -l
    • Note the number for PIIX4, I801, and NCT6775 controllers.
    • Give user access to those controllers, for instance: sudo chmod 777 /dev/i2c-0

USB Access

  • USB devices require udev rules to access as a normal user.
  • You can run OpenRGB as root to detect all USB devices.
  • Udev rules are included in this repo:
    • Copy the 60-openrgb.rules file to /etc/udev/rules.d/
    • Reload rules with sudo udevadm control --reload-rules && sudo udevadm trigger

MacOS

  • Pre-built binaries in zipped application package format are available under the Releases section on GitLab.
  • You can build the project using Qt Creator or on the command line.
    1. Install build dependencies with Homebrew
      • Install Homebrew by following the instructions at https://brew.sh/
      • brew install git qt5 hidapi libusb mbedtls@2
      • brew link qt5
    2. Create a local certificate called OpenRGB with code signing capability
    3. git clone https://gitlab.com/CalcProgrammer1/OpenRGB
    4. cd OpenRGB
    5. qmake OpenRGB.pro
    6. make -j8
    7. macdeployqt OpenRGB.app -codesign=OpenRGB
    8. Copy the OpenRGB.app application package to Applications

SMBus Access

  • SMBus/I2C devices are currently not supported on MacOS.

USB Access

  • USB devices may require the Input Monitoring permission. You can add OpenRGB in System Preferences > Security & Privacy > Privacy.

Join Our Discord

Visit Our Subreddit

How-Tos and FAQs

Support OpenRGB

  • OpenRGB is a project I created to solve a problem I had with the RGB ecosystem. My goal isn't to make money off of this project. That said, people have requested to donate, and donations allow me to buy more RGB stuff to reverse engineer.
  • Donate via PayPal
  • Become a Patron (I'm not doing any Patreon-exclusive content, it's purely for donation)
  • Donate via Bitcoin: 1N83YPu7btXYadPS1neB9zX7X1QTdpyZQ

History of OpenRGB

  • OpenRGB is a continuation of OpenAuraSDK, which itself was created out of reverse engineering work done on the Keyboard Visualizer project. For a complete history of the RGB projects that led to OpenRGB's creation, see the History page.

Contributing

  • Want to contribute support for a new device? Check out the RGBController API page for documentation of how OpenRGB implements device control.
  • Want to create a new OpenRGB SDK client implementation? Check out the OpenRGB SDK Documentation page for documentation of how the OpenRGB SDK network protocol functions.

OpenRGB SDK

Applications Supporting OpenRGB SDK

OpenRGB Plugins

Projects Used

Projects Researched

While no code from these projects directly made its way into OpenRGB, these projects have been invaluable resources for protocol information.