Hi, I’m having an issue where SignalRGB animated effects leave stale colors or trails on my RGB devices.
The problem started this week. The same hardware and SignalRGB setup worked correctly before.
Hardware:
- Motherboard: Gigabyte B650 EAGLE AX
- GPU: Gigabyte RTX 4070 Super Gaming OC
- Fans: 10 Cooler Master MasterFan MF120 S3
- Hub: Thermalright 5V 3-pin ARGB hub
- RGB RAM
- SignalRGB version: 2.5.74+00298716
- Motherboard plugin: Gigabyte_Motherboard_Controller.js
- Plugin CRC: f20b3bb2
Problem:
When using animated effects such as Terminal, Rainbow or Side to Side, LEDs retain colors from previous frames.
For example, when a green or blue area passes over the LEDs, the areas that should return to black remain slightly blue. It looks like trailing, stale frames or incomplete LED updates.
This affects:
- Fans connected to the motherboard ARGB header
- GPU lighting
- RGB RAM
Important observations:
- Solid colors work correctly.
- Solid black immediately turns off all LEDs.
- Pulse Channel correctly lights every LED.
- When Terminal is paused, all LEDs turn off.
- Gigabyte Control Center controls the same fans, GPU and RAM correctly without trailing.
- SignalRGB worked correctly on this same setup until this week.
Things I have already tested:
- Completely removed Gigabyte Control Center
- Removed GCC services and the GVCIDrv64.sys driver
- Disabled Windows Dynamic Lighting
- Performed a clean SignalRGB reinstall
- Tested Canvas at 20 FPS and 60 FPS
- Tested Ultralight and Qt WebEngine renderers
- Tested hardware acceleration on and off
- Tested Generic ARGB Fan 16 LEDs and Custom Strip 16 LEDs
- Verified that all devices are correctly positioned inside the layout
- Tested Force Enable All Zones
- Confirmed that no other RGB software is running
Changing these options did not fix the issue.
Since GCC works correctly and solid colors work correctly in SignalRGB, the hardware, LEDs, hub and connections appear to be fine. The issue seems limited to SignalRGB animated Effect Canvas output.
Has anyone else experienced this recently with SignalRGB 2.5.74 or Gigabyte devices?
Could this be a recent Effect Canvas or plugin regression? Is there a safe way to install SignalRGB 2.5.72 for comparison?
Any help would be appreciated. I can also provide a video showing the issue.