1.3.1 hotfix

This is a small hotfix for 1.3.1 due to a coding mistake if a device with multiple matrix subdevices was connected the led created for the second subdevices was equal to the 1st + 2nd subdevice instead of 2nd only, though creating unwanted leds and make the plugin don't function correclty :)

1.3

In this small update I Fixed bugs related to JSON Parse error and devices with multiple matrix zones.
In a future version I'll add better server management with tray icon and more. Stay Tuned !

1.2

This updates bring a fix for large devices (with too much leds) not working
I'm working on solving other issues and improving the server by adding a tray icon and easy management

Stability and bug fixes releases !

This update fix:

• Main connection issues (by giving uniques IDs to each devices)
• Improve connection speed when adding/removing devices
• The server is now more resilient and will automatically reconnect to openRGB if the connection is lost
• Minors improvments and bugs fixes

First release !

This update add suport for :

Multiple zones control support
Multiple Device Support
Independent LED control support
Custom shaped devices support

And more !

Alpha 0.1

This is the first release of OpenRGB Bridge for SignalRGB:

Right now this plugin is only working well with only one device connected to signalRGB through my plugin, Only one color LED is supported, that means that if you have multiple LED they are all going to lit the same color and a lot of bugs quirks and clunky behaviors are to be expected. Everying is going to be fixed in later releases

This plugin allow you to control devices that are supported by OpenRGB but not by SignalRGB (like Nvidia Founder Edition Graphics Cards)

First Download and put OpenRGBBridge.js and OpenRGBBridge.qml in your SignalRGB plugin folder (documents -> WhirlwindFX -> Plugins)

To make this plugin work make sure you have OpenRGB installed and running on your system. You can download it from the official website. Don't forget to start the SDK server by goind to the SDK server tab and clicking on "Start Server". Then under The Settings tab in "General Settings" make sure to enable "Start at login", "Start Minimized" and "Start Server". And make sure the deevice you want to controll is supported by OpenRGB and that it's control mode is set to Direct

You also need to download an intermediate server binary in the release section just under this message or if you prefer install node.js and download the bare node.js file and run it using the following command: "node server.js." If you use the EXE file it will be automatically runned on windows startup the next time (you can disable this behavior by adding "--no-startup" to the filename).

The intermediate server will be running on port 9730 by default, if you want to change the port you can do that by modifying the server.js file directly or by renameing your js/exe file by adding "--port=${THE PORT YOU WANT}" depending on what file you picked. You can also show the console window if you want by adding "--console" to the filename. And then don't forget to tick the "Use a custom port for the intermediate server" checkbox and enter the port you choosed in the input that will appear.

Then after everything is up and running you can connect to the OpenRGB SDK server by entering the Ip and the Port displayed in the OpenRGB SDK server tab (it should be "127.0.0.1" and "9730" by default) and clicking on "Connect". Then you can select the devices you want to control that are not directly supported by SignalRGB. Thoses devices will be synced with your current layout and effects and will automatically be added on signalRGB startup.