Jump to content

CalcProgrammer1

Member
  • Posts

    12
  • Joined

  • Last visited

Everything posted by CalcProgrammer1

  1. OpenRGB's current release (0.5) as well as master branch pipeline builds should be safe. As with all reverse engineered software, the risk of hardware bricking is non-zero, but this is more during the development phase than the end user phase. The issue with bricking was MSI motherboards, and we have taken steps to fix that and thoroughly test the fix before reenabling it for general use. OpenRGB's GitLab page can be found here: https://gitlab.com/CalcProgrammer1/OpenRGB
  2. Try taking out your RAM modules and swapping them all to different slots. For some reason, this seems to be a reset switch of sorts for the Aura-based RAM RGB controller. If it's not detecting in any software across reboots I doubt a Windows reinstall will change anything, except if you have Valorant/Vanguard installed, as Vanguard blocks i2c access in some RGB apps.
  3. I'm working on an open source RGB control app that aims to do just that: https://gitlab.com/CalcProgrammer1/OpenRGB
  4. I am working on an open source RGB control application called OpenRGB. It supports a wide variety of devices on both Windows and Linux. It is still in early development but is usable in its current state. I just added an SDK so that other apps can control RGB through it. https://gitlab.com/CalcProgrammer1/OpenRGB The supported devices list can be found on the project wiki. I also have an audio visualizer app that syncs all your devices using the OpenRGB SDK and can flash them to music. https://gitlab.com/CalcProgrammer1/KeyboardVisualizer
  5. I'm working on an open source universal RGB app. It doesn't support everything just yet, but we're adding new devices all the time and a lot of other people have contributed drivers. It supports most Asus Aura motherboards, some Gigabyte motherboards, most RGB RAM, a few GPUs, and a lot of peripherals and RGB lighting kits. For ARGB fans, you need to use software compatible with whatever ARGB controller you're using. Usually this is your motherboard, but you can also use USB ARGB controllers like Corsair's Lighting Node devices or Asus' ROG Aura Terminal. My project: https://gitlab.com/CalcProgrammer1/OpenRGB
  6. I'm working on an open source alternative to all the proprietary, vendor-specific RGB control apps. My app is called OpenRGB and the goal is to create a user interface that can handle any RGB device from any manufacturer, then write open source device drivers for as many RGB devices as possible. I already have a fair number of devices supported - ASUS Aura, Gigabyte RGB Fusion, ASRock Polychrome RGB, Razer, Corsair, G.Skill, HyperX, and more brands have at least some support so far. My app works in both Windows and Linux. I recently added the ability to save profiles so you can configure your whole RGB setup and save it to a single file, loadable with one click from the tray icon or UI. Also has a rudimentary CLI for those who don't want a GUI. Project is still in early development. https://gitlab.com/CalcProgrammer1/OpenRGB
  7. I'm working on an open source RGB control application called OpenRGB. The goal is to support as much hardware as I can and enable full control of everything in one app. I have a lot of motherboards and RAM supported as well as Corsair Lighting Node/Commander Pro, NZXT Hue+/Hue2, Thermaltake Riing Plus, and more. I only have the original K70 RGB supported as far as Corsair peripherals go, but I am planning to expand that as the protocols are documented. My program supports Windows and Linux. https://gitlab.com/CalcProgrammer1/OpenRGB
  8. I'm working on adding Gigabyte X470/B450 era boards to my OpenRGB project. My project is a completely open source reimplementation of as many RGB protocols as I can reverse engineer. No official software required, which allows it to run on both Windows and Linux. I have support for some Corsair fan controllers (Lighting Node Pro, Commander Pro) and G.Skill RGB RAM among other things. X370 and X570 Gigabyte boards are supported but not X470, though I have a Reddit user who has provided protocol captures. If you want to help add support I can send you the capture program I wrote. My project can be found here: https://gitlab.com/CalcProgrammer1/OpenRGB
  9. I'm working on an open source RGB app that may be what you're looking for. My app is designed to support as many RGB devices from as many vendors as possible. I'm writing all the hardware interface code from scratch or from other open source projects, no official SDKs or official software required. My project currently supports a fair number of devices. The Corsair Lighting Node Pro and Commander Pro are supported (which drive Corsair RGB fans) and Asus Aura based RGB RAM is supported (Trident Z RGB uses an Aura chipset). I have some ASRock motherboards supported but no X570 yet. I'd be happy to help reverse engineer it and add support. Other manufacturers have changed their RGB systems for X570 so I'm not sure how ASRock did theirs. My project supports both Windows and Linux. It's in early development right now so there are no releases yet. https://gitlab.com/CalcProgrammer1/OpenRGB
  10. I'm working on an open source RGB control app for Windows and Linux. My goal is to support as many systems as I can to unify the RGB mess. I currently support Asus Aura motherboards and RAM, Corsair Vengeance RGB/Pro RGB, HyperX RGB RAM, and a handful of other partially supported devices including Gigabyre RGB Fusion 1.0 motherboards and ASRock motherboards. I would like to support more! https://gitlab.com/CalcProgrammer1/OpenRGB.
  11. See my OpenRGB project on GitLab. Previously known as OpenAuraSDK, it is a project to create open source, Windows and Linux drivers for Asus Aura, Aura RAM, some other manufacturers' RAM (Corsair, HyperX), other motherboards (Gigabyte and ASRock partially implemented), and assorted other stuff like the AMD Wraith Prism cooler, NZXT Hue+, etc. Should work just fine for your motherboard and RAM. https://gitlab.com/CalcProgrammer1/OpenRGB
  12. Adding to the discussion here, I got this RAM kit for my AMD Ryzen build and it's great. The software is based on ASUS Aura, though it's a rebranded Aura app with the G.Skill logo. I believe there is a way to use it with the ASUS Aura app as well, but unfortunately I had to return my ASUS motherboard (bricked itself) so I can't test that. The LED controller does not affect RAM speed at all, as it does not use the DDR memory interface at all. All DDR RAM modules since DDR1, possibly even earlier, have a small EEPROM nonvolatile memory chip on them called the SPD EEPROM (serial presence detect), this chip stores the timings, XMP profiles, model number, etc. data so that the PC can identify the RAM and autoconfigure the correct settings for it. This EEPROM chip is connected over a secondary communication interface called SMBUS, which itself is a slightly restricted version of I2C. Your chipset/southbridge contains at least one SMBUS host controller, and that's how the PC hardware communicates with the SPD EEPROM. G.Skill uses this SMBUS interface for their LED controller, not the main memory bus. I'm working on reverse engineering this protocol so I can write a Linux driver for the RGB controller and integrate it into my RGB music visualizer application. I managed to send a command set using i2cset on Linux that changes the color of the RAM, so I should be able to reimplement it properly soon.
×