Conversation
|
If all color values are required anyway (rgb), it might make sense to put them into one argument, like --colors 255,255,255 (like on the equaliser). But Im open for discussion here. Im not sure how the polynomial function was created, but you also might consider using splines, which are simpler and more transparent (if applicable in this case, as this wouldnt be a "smooth" curve then): #197 (comment) |
That's a good idea actually. I had also thought about setting the colors with their hex codes (--colors FF55AA)
I sent from the Windows Logitech G Hub all the values from 0 to 255 (changing one color channel) and saved every hex value from wireshark. Then I created a table with its respective graph and I calculated a curve that fits the points. I did something like this guy did (which also has an interesting repo): |
|
This PR is stale because it has been open 300 days with no activity. Remove stale label or comment or this will be closed in 60 days. |
|
This PR was closed because it has been stalled with no activity. |
Description
This pull request adds the arguments required for setting RGB values on some headsets and the implementation for the Logitech G733.
This development was carried out on a Logitech G733 on Linux.
Configuration options
Examples
headsetcontrol -R 255 -B 255headsetcontrol -G 255 -tClarifications