python-rgbkeyboards icon indicating copy to clipboard operation
python-rgbkeyboards copied to clipboard

Implement support for Razer keyboards on Linux using openrazer

Open RedFantom opened this issue 8 years ago • 5 comments

Support for Razer keyboards will not be added, for a few reasons.

There would be two ways to add support for these keyboards:

  • By using the new REST based API of the Razer Synapse software
  • By writing code that calls into DLL-files distributed only with the Razer Synapse software Both of these methods clearly make the whole library dependent on not only closed-source software (which I am okay with), but a completely closed ecosystem, which I cannot agree with.

Razer does provide a separate SDK (which still requires the Synapse software to be installed), but this is quite a complicated one with lots of weird data structures (which, I my opinion, are completely overkill for the task they should perform), which would be difficult to replicate in Python's ctypes.

RedFantom avatar Jul 19 '17 17:07 RedFantom

There is openrazer but it only supports linux.

henryruhs avatar Jan 05 '19 02:01 henryruhs

Thank you for sharing this with me! When I searched for a solution one-and-a-half years ago, I was unable to find openrazer. However, I will still not be implementing support anytime soon, as there are no testers and thus I do not know whether my code for other keyboards than my own even works...

RedFantom avatar Jan 10 '19 09:01 RedFantom

@RedFantom I could provide testing or give an helpful hand - I use openrazer allready in a project.

henryruhs avatar Jan 10 '19 09:01 henryruhs

I have openrazer installed as well,and i can test the library. Btw would be nice having some kind of support for windows too.

eadmaster avatar Sep 26 '19 17:09 eadmaster

Right now commit 3f40891 adds the only limited support for Razer keyboards. Anyone is welcome to try it and report the results!

However, at the moment I am quite busy already, so it is unlikely that I'll be able to devote time to this project anytime soon. The structure of a keyboard back-end is not extremely complicated and there are quite some back-ends already present to build on, so perhaps someone is interested in picking it up?

I'll accept any stable back-end that does not require external software running (so with Windows DLL-files is fine), but as I no longer run Windows and still only have the single keyboard, testing it would be impossible.

RedFantom avatar Sep 28 '19 14:09 RedFantom