Jump to content

CorpNewt

Members
  • Posts

    37
  • Joined

Reputation

10 Good
  1. Hmm... I loaded up the daemon with the --nohwload and then pushed the num-pad and other keys that aren't responding and it doesn't do anything at all... Chip-Mac:~ Chip$ sudo /Applications/ckb.app/contents/resources/ckb-daemon --nohwload ckb: Corsair RGB driver beta-v0.1.5+t11 Hardware load disabled Root controller ready at /var/run/ckb0 Connecting Corsair K70 RGB Gaming Keyboard (S/N: 0701503FAE3618E3530D5EE9F5001944) Starting input thread for /var/run/ckb1 Corsair K70 RGB Gaming Keyboard ready at /var/run/ckb1 When I press the keys that do work, I get things like this: Input 0x00 0x01 (0x15): 010100000000000000000000000000000000000000 RGB switch kb: -2 (21) kp: 0x003b, 1 Input 0x00 0x01 (0x15): 010000000000000000000000000000000000000000 RGB switch kb: -2 (21) kp: 0x003b, 0 Thanks for helping me troubleshoot this. It looks like the newer version of the driver just isn't catching anything from those keys.
  2. I'll download it and give it a run. Any idea what might be causing the daemon to hang when launched by the launchd service? I have to unplug-replug the keyboard to be able to type my password and then when I log in, go into activity monitor and force quit the ckb-daemon to allow it to restart, then everything seems to work without a hitch. I will take a look at the new testing build and see if the same thing persists there. Don't worry about taking time with the bugs ;) You've already kicked more than enough *** on this project and even with a few potholes here and there I still prefer your driver on my mac side over the official drivers on my windows side. Thanks again for all your hard work and help! Edit: Okay, I installed the new testing version and I still need to unplug-replug forcequit to get the keyboard up and running, and I still have the issue of the number pad not working. I also checked out a bunch of other keys and it looks like the ones that do work are the standard a-z keys and the number keys above the qwerty row, the media keys also work. The ones that don't work are 10-key, backspace, enter, spacebar, punctuation keys (,./;'[]\), the delete, end, home, etc. They don't type the keys, or perform any of the reactive animations so I'm guessing the daemon doesn't even see them getting pressed. Hopefully that info helps! For the meantime, I'm just going to keep rocking the master build and do my usual unplug-replug dance. I might right a shell script that force-quits the ckb-daemon when I log in. I have also noticed that the daemon seems to hang and my startup times are like double-triple when the keyboard is plugged in.
  3. Using the latest master build, I've run into the issues of ckb-daemon hogging 50+% of the cpu at boot up and not being able to detect the keyboard until I unplug it, plug it back in, and then force quit ckb-daemon with Activity Monitor. I tried the latest testing build, but it disabled the use of my 10-key pad. I couldn't find any settings pertaining to that, and tried a clean install. Any ideas?
  4. I've noticed that recently the lighting on the keyboard just likes to freeze. The functionality is all still there and all remapped keys work just fine, but I have to restart everything to get the lighting to move again. After messing with the polling rate when it freezes, I've found that if I set it to the bios mode, or up one from there (8), I can get it to come back on. But anything higher and it is still frozen. Maybe it's an issue with the way Mac handles keyboard polling?
  5. Cool! Thanks for the response. I'll let you know if I find anything else!
  6. Hmm, got it fixed by using the quickinstall script. I had been just building ckb and switching everything out. Guess that's that! Edit: I did notice a new issue though. I use an M-Audio M-Track usb audio interface, and I can't have it plugged in to the usb port next to the one I use for the keyboard since this last update. If U = Empty USB slot, K = Keyboard and M = M-Track: U U K M U U Doesn't work, but ANY combination that puts the keyboard and M-Track in different rows does. For example: K U U M U U Does work. Not sure why this might be? I have enough usb ports to get by with moving things around, but it's still kind of a weird phenomenon. Let me know if you need more info!
  7. The new version seems to be working just fine after the firmware upgrade... I feel like I'm blind though, I'm on Mac OS 10.10.3 and I can't for the life of me find anything that states to start at login... I had been running it with the standard launch at login option using the user settings in the system preferences application which works okay, but it always starts with the window front and center. I'm going to try and delete everything, and set it up from scratch and see if that helps.
  8. As always, everything is working phenomenally, and thank you so much for all your hard work! Is there any way to increase the timing accuracy from 0.1 seconds to 0.01 seconds? Also, can we start the menu item minimized, instead of having the full window visible? Thank you so much!
  9. Just a side note, not sure if this is default behavior in MacOSX, but when Caps lock is on, and I press shift, it does not make the letters lowercase. They all stay uppercase regardless of whether shift is being pressed. Not really a problem, just an observation. Other than that, things are running swimmingly! Thanks again for all the hard work!
  10. So far everything is running awesome! I have noticed that if I right-click on an animation to duplicated it, CKB will crash on me though. Also, ckb-daemon is always showing as "not responding" in the activity monitor, I don't think that affects anything, just curious as to why. Thanks again for all the hard work! The modifier switches work perfectly!
  11. As always, awesome improvements! Thanks again for all your hard work! As for your questions: 1. I think the auto-save system works well for me. It hasn't been anything that I've looked at and wished was different. It runs very transparent. 2. Undo/Redo would be worthwhile from my experience, especially when working with more complex lighting modes. 3. I agree with your thoughts on the binding/lighting modes. I haven't done any looking as of yet, but is there a way to bind a key, or key combination to switch modes?
  12. Would you mind just adding another checkbox, or some way to swap the command and option keys? That way it functions like a standard mac keyboard. Either way, switching the keybindings manually isn't that difficult.
  13. The key repeats appear to be fixed! I also love the fact that I don't have to run a script to swap the command and option keys. Out of curiosity, why in CKB do you have it swap the control and command keys? Everything is working very well though! Thanks again!
  14. They delay in windows is roughly about a second. Not sure if that's the issue though as it repeats extra slow too. I'll do some extra digging and see what I can find.
  15. I'm still having issues with the backspace key taking a good 4 seconds before the repeats start. Is this something with the keyboard driver, or something in the Mac OS that I'm missing? Other than that, things are working flawlessly! Phenomenal job!
×
×
  • Create New...