Open gabamnml opened 7 years ago
Whoops, just saw this, sorry!
@gabamnml Definitely keen to add Chroma keyboard support however I don't personally own one.
https://github.com/Benjamin-Dobell/GERazerKit/tree/master/Tools
If you're able to share the output from ./monitor.sh
with me then I can take a crack, or at least point you in the right direction.
Basically execute ./monitor.sh
(after executing ./patch.sh
) then open Razer Synapse and mess around will all the different keyboard lighting options. It'll capture all the messages responsible for changing the settings.
@Benjamin-Dobell I can't run monitor.sh correctly because when I open it returns a segmentation fault and in synapse it does not recognize anything until I re-run unpatch.sh
Here is my log:
Killing RzDeviceEngine. It will restart automatically. 2017-01-06 11:52:14.707 monitor[5416:46303] Succesfully hijacked the Razer Device Engine port. 2017-01-06 11:52:15.210 monitor[5416:46303] Could not connect to the Razer Device Engine. 2017-01-06 11:52:15.210 monitor[5416:46303] Please ensure RzDeviceEngine is running. 2017-01-06 11:52:15.714 monitor[5416:46303] Could not connect to the Razer Device Engine. 2017-01-06 11:52:15.714 monitor[5416:46303] Please ensure RzDeviceEngine is running. 2017-01-06 11:52:16.209 monitor[5416:46303] Could not connect to the Razer Device Engine. 2017-01-06 11:52:16.210 monitor[5416:46303] Please ensure RzDeviceEngine is running. 2017-01-06 11:52:16.709 monitor[5416:46303] Could not connect to the Razer Device Engine. 2017-01-06 11:52:16.710 monitor[5416:46303] Please ensure RzDeviceEngine is running. 2017-01-06 11:52:17.213 monitor[5416:46303] Could not connect to the Razer Device Engine. 2017-01-06 11:52:17.213 monitor[5416:46303] Please ensure RzDeviceEngine is running. 2017-01-06 11:52:17.714 monitor[5416:46303] Could not connect to the Razer Device Engine. 2017-01-06 11:52:17.714 monitor[5416:46303] Please ensure RzDeviceEngine is running. 2017-01-06 11:52:18.210 monitor[5416:46303] Could not connect to the Razer Device Engine. 2017-01-06 11:52:18.211 monitor[5416:46303] Please ensure RzDeviceEngine is running. 2017-01-06 11:52:18.710 monitor[5416:46303] Could not connect to the Razer Device Engine. 2017-01-06 11:52:18.710 monitor[5416:46303] Please ensure RzDeviceEngine is running. 2017-01-06 11:52:19.212 monitor[5416:46303] Could not connect to the Razer Device Engine. 2017-01-06 11:52:19.212 monitor[5416:46303] Please ensure RzDeviceEngine is running. 2017-01-06 11:52:19.615 monitor[5416:46303] >>>>>>>>>> Inbound Message (msgid: 56) >>>>>>>>>>
{ rzcontflag = 0; rzdata = <62706c69 73743030 d101025f 10135265 73706f6e 73654d73 67506f72 744e616d 655f1019 4e616761 436f6e66 69677572 61746f72 5265706c 79506f72 74080b21 00000000 00000101 00000000 00000003 00000000 00000000 00000000 0000003d>; }
rzdata = { ResponseMsgPortName = NagaConfiguratorReplyPort; }
./monitor.sh: line 28: 5416 Segmentation fault: 11 "$BASEDIR/bin/monitor"
Hmm, perhaps there's a shared library issue. In that same tools directory there's a src/
directory. If you execute ./build.sh
it'll build the monitor
binary (used by monitor.sh
).
Replace the prebuilt monitor
binary in the tools directory with the one you just built, then retry.
Same problem after run the build. Here is my screen with monitor build. This is correct?
Hey @Benjamin-Dobell I am very interested in making this work for macOS. Would you have any pointers on how the patching works on your keyboard so I could try to make it work for ours (I have the same one as @gabamnml).
I noticed one weird behavior: when the engine is patched, the focus keeps being stolen from the current application into something. It does that every couple of seconds.
Is there any possibility that there is some documentation about it to achieve integration with the keyboard or in the future makes possible?
Regards