i must be the only one with the keyboard workin nicely :D
Apple Pro Keyboard - Griffin Airclick USB as USB device for irkeboardemu.kext
up and down work as up and down (volume stays same)
Volume controlled by acutal sound buttons (on the keyboard)
keystrokes fire once not twice. (as the should)
Well...I got it work and it storke once not twice
but it's also volume up and down...
@dcpark: thats what i was suggesting - a kext to allow third party IR dongles to behave as apple's one.
i was considering trying a Natit-style injection approach to inject the values the apple IR module installs... but maybe a kext is the way to go, im not sure.
the above key stroke problem is caused by my old usb keyboard, not by keyboardreader... just for clarification.:p thanks again to bike and brandon!
Originally Posted by dcpark
@munky: i hope you make it, cheers! :D
working just fine for me on a CD macbook (isight as USB device). Only real complaint for me right now is having to have Keyboardreader open in a terminal window the whole time... has anyone figured out a better way of running it? is a keep-open applescript feasible?
after a little investigation, i've found the KeyboardReader can be extented to handle any HID devices, such as a remote control, joystick, and so on..
Originally Posted by munky
* the current KeyboardReader just focus on the usage:Keyboard(id=0x06) of usagepage:Generic Desktop Page(id=0x01), and handle button ids for the six keys on the keyboard. so, the productID and vendorID in the InitHIDNotification are not good namings for those variables, actually it should be usagePage and usage. i modified ids for usagePage(was productID) and usage(was vendorID) to be match with consumer electronics page, and also a few lines in FindHIDElements and InterruptReportCallbackFunction... now my remote control can trasmit 'sysctrl -w kern.sendIR=x' to IRKeyboardEmu.kext to emulate Apple Remote.
* imho, the routines for getting HID values & sending commands (currently the role of KeyboardReader) from 'any hid devices'(let Info.plist be editted later or so) can be merged into the same single kext, so that it can also receive HID values and transform into apples' code & report to the system (currently the role of IRKeyboardEmu.kext). then we could do away with terminal thing no more. :rolleyes: any sugesstions?
Keep it running is a great idea if the key isn't Space, Enter, and Up Down Left Right....
I change it to Home(as Up), End(as down), Delete(as right), Page Down(as left), Page Up(as Enter), Insert(as Space), and trying to let it run as a kext
dcpark: sounds like some interesting progress... keep us posted :)
i will let you know if i find the time to try the injection route, but time is very precious for me at the moment...
Sorry I havn't been around lately. Took a small break after the last week of coding. I'm going to start working on making the kext load and work without taking over the device. I have a few ideas and I'm going to start working on it. To those having problems with volume increasing instead of aTV control, I will look into it.
I've attached a command line tool that will let you do the "sysctl -w ..." thing without using sudo.
Here is how to use it:
1. Extract the zip file using the built-in tool in OS X.
2. If you extracted the zip file with any other tool, go to Terminal and type:
chmod 4711 /path/to/RemoteControl
3. In Finder, right click the extracted RemoteControl file and select Get Info.
Under Ownership & Permissions, set the owner to "system".
4. The tool is ready to use.
where x is the number you would pass to sysctl.
If you copy/move the tool, you have to do step 2 again.