OpenRGB 0.7 comes with a configuration menu, bug fixes and more

For those who are unfamiliar with OpenRGB, they should know that it is RGB lighting device control software and is a implementation offered is pretty solid which supports multiple generations of Aura controllers on Intel and AMD platforms, which eliminates the need to install official proprietary applications that are tied to a specific manufacturer.

OpenRGB is compatible with Aura compatible drivers used in various RGB memory module manufacturers including G.Skill Trident Z RGB and others.

The project offers a library of functions with a universal API to control the backlight of applications, a console utility and a graphical interface in Qt. Supports the choice of color change modes (color wave, etc.), control of backlight zones, application of advanced effects, definition of the LED design and synchronization of the backlight with the actions performed (color music, etc.).

Main new features of OpenRGB 0.7

In this new version that is presented a settings menu has been added and in which now, to configure a specific functionality (E1.31, QMK, Philips Hue, Philips Wiz, Yeelight devices and devices controlled via a serial port, for example based on Arduino), it is not necessary to edit the file configuration manually.

Another change that is implemented is in the OpenRGB automatic start control which on system startup is now available in the setup menu. You can specify additional actions that OpenRGB will take in this release (applying profiles, launching in server mode).

It is also highlighted that added the ability to save settings to a device if there is Flash memory on the device. Saving is done by command only to avoid wasting Flash resources. Previously, saving was not performed for such devices for the same reasons.

The plugins now have a version control mechanism to avoid crashes due to legacy builds with newer versions of OpenRGB.

Also added a slider to control the brightness of the devices that have these settings in addition to the color settings, the ability to install plugins through the settings menu was also added and a logging console was added to make it easier to get information on crashes from new users.

Finally, it is also mentioned that when new devices are found that require dimensionality adjustment (ARGB drivers), OpenRGB will ask the user to do so.

As for problems that were solved:

  • Fixed issues with USB device detection related to interface / page / usage settings that differ between operating systems
  • Fixed key location maps (layouts) on many devices.
  • Improved record format
  • Fixed multiple WMI initialization issue (resulting in inability to re-detect SMBus devices)
  • Slightly improved user interface
  • Fixed app crashes when connecting Logitech mice (G502 Hero and G502 PS)
  • Fixed app crashes when downloading plugins

Regarding the list of new supported devices, We can consult them here. PYou can check the hardware compatibility that currently supports this utility in the following link.

How to install OpenRGB on Linux?

For those who are interested in being able to install OpenRGB on their system, they should follow the instructions that we share below.

The first thing to do is install the latest edition of Qt Creator.

In the case of Ubuntu and derivatives we must install some dependencies:

sudo apt install qt5-default libusb-1.0-0-dev libhidapi-dev

Now we are going to obtain the utility with the command:

git clone https://gitlab.com/CalcProgrammer1/OpenRGB

Done this now we must update the submodules:

git submodule update --init –recursive

And here we can do two things, one of them is to open the project with QT creator or compile it in the system.

To compile, just run the following commands:

cd OpenRGB
qmake OpenRGB.pro
make -j8
./OpenRGB

At the end of the compilation we must allow access to SMBus.

In Intel we can do it with the command:

modprobe i2c-dev i2c-i801

Or in the case of AMD, we must first list the SMBus drivers with:

sudo i2cdetect -l

Once the controller has been identified, we must grant permissions to the controller, for example:

sudo chmod 777 /dev/i2c-0

Finally, it should be taken into account that there are still some capabilities to persist in all reboots, but the main functionality of configuring colors and modes is stable.

If you want to know more about it you can check the details In the following link.


Be the first to comment

Leave a Comment

Your email address will not be published. Required fields are marked with *

*

*

  1. Responsible for the data: AB Internet Networks 2008 SL
  2. Purpose of the data: Control SPAM, comment management.
  3. Legitimation: Your consent
  4. Communication of the data: The data will not be communicated to third parties except by legal obligation.
  5. Data storage: Database hosted by Occentus Networks (EU)
  6. Rights: At any time you can limit, recover and delete your information.