You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Switch back to DXGI DDA: LEDs flicker again on mouse movement
Run any effect (bypasses grabber): LEDs perfectly stable, no flickering
Change capture frequency from 144 Hz to 25 Hz: no change, LEDs still flicker
Change image decimation factor from 8 to 12: no change, LEDs still flicker
Windows cursor shadow and cursor trails are both disabled: no change
What is expected?
Mouse movement on a static desktop should not cause visible LED color changes. The QT grabber handles this correctly — LEDs remain stable during mouse movement.
What is actually happening?
Every mouse movement triggers visible LED flickering when using the DXGI DDA grabber. The flickering occurs regardless of capture frequency or decimation settings. This did not happen with the old DDA grabber in version 2.0.16.
The rewritten DDA grabber (introduced in 2.2.0) likely composites the cursor into the captured frame, so every cursor movement produces a slightly different image on an otherwise static desktop. The image processing interprets these minimal pixel differences as color changes and sends them to the LEDs.
A possible fix would be to either:
Exclude the pointer/cursor from the DDA capture (skip DXGI_OUTDUPL_POINTER_SHAPE compositing)
Ignore frames where only the pointer position changed (check DXGI_OUTDUPL_FRAME_INFO.LastMouseUpdateTime vs. LastPresentTime)
Bug report
Steps to reproduce
Additional tests performed:
What is expected?
Mouse movement on a static desktop should not cause visible LED color changes. The QT grabber handles this correctly — LEDs remain stable during mouse movement.
What is actually happening?
Every mouse movement triggers visible LED flickering when using the DXGI DDA grabber. The flickering occurs regardless of capture frequency or decimation settings. This did not happen with the old DDA grabber in version 2.0.16.
The rewritten DDA grabber (introduced in 2.2.0) likely composites the cursor into the captured frame, so every cursor movement produces a slightly different image on an otherwise static desktop. The image processing interprets these minimal pixel differences as color changes and sends them to the LEDs.
A possible fix would be to either:
DXGI_OUTDUPL_POINTER_SHAPEcompositing)DXGI_OUTDUPL_FRAME_INFO.LastMouseUpdateTimevs.LastPresentTime)Hardware: NVIDIA RTX 4060 (Laptop, Lenovo Legion 14), Driver 595.76, Monitor 3440x1440 @ 144 Hz, SK6812 RGBW LEDs via WLED on ESP (WiFi, UDP-DDP)
System