When synchronizing the 80HE lights with SignalRGB/OpenRGB, the light bar no longer does anything and stays stuck to whatever it was displaying.
It would be great to fix the keyboard firmware so that the light bar either works independently and is able to continue displaying what is configured on wootility or allow the light bar to be controlled by the software.
#Fix/improve Wooting 80HE Light Bar Indicator when using SignalRGB/OpenRGB
tardy badge
Fix/improve Wooting 80HE Light Bar Indicator when using SignalRGB/OpenRGB
grizzled spindle
using the rgb sdk overrides all RGB of the keyboard
the fix is replicating the functions in whatever controls your RGB
tardy badge
Not necessarily, other keyboard like Nuphy separate both. In this case, if the lightbar is controllable, then I can look into enhancing the plugin to control it. If it's not controllable, then it would be great to keep capabilities. I'm not sure where to look - maybe inside https://github.com/WootingKb/wooting-rgb-sdk somewhere.
I'm looking at the plugin right now and can make enhancements.
grizzled spindle
feel free to do so
wont really change anything cause as soon as the firmware receives the rgb sdk commands it stops internal rgb processing
tardy badge
that was my thought, then I need to find the packets
grizzled spindle
i mean that wont really help you either
youd have to change the firmware to process rgb and receive rgb commands
and that will most likely drastically reduce either accuracy of sensor data for keys or the scanrate internally
tardy badge
The led bar is an additional 10Leds, so nothing impossible I think. The Wooting Two has more keys and is capable of it. If there is a way to encode in the existing payload the light bar, then it's doable.
At the worse case, it would be great to clear the led bar if nothing else can be done when the SDK takes over.
I don't see any files for the firmware on github though - so can't really see the Pros/Cons there.
grizzled spindle
oh thats what you mean. i thought you meant modifying it so the sdk doesnt stop internal rgb processing
actually not sure what @sturdy nexus plans for the led bar and the rgb sdk in this regard
tardy badge
I'm not sure what is best. Either way, I want to make the led bar not appear like it crashed or bugged out. So continuing to process, letting the SDK sync with additional data or clearing it completely as "not supported" would be great.