2015-01-05, 18:01
Anyone?
2015-01-06, 22:00
The main problem is that all actions are sending keyboard actions (like up, down, enter) making it hard to verify against Kodi.
Try to disable section Windows and Starter, and activate section AppleRemote (right click menu on each section)
If your remote is correctly installed and the HIDs are correct in the XML you should be able to move around in the tree in eventghost
If you also check the alternative in the left bottom in eventghost (Log only assigned events) you can verify that you have the right events (HID numbers) connected in the XML
As a reminder the numbers (HID) are very similar for short click and long click and press and release button.
When I get the time I will comment what type of actions there is on each event because it is hard if you don't have the same remote
Try to disable section Windows and Starter, and activate section AppleRemote (right click menu on each section)
If your remote is correctly installed and the HIDs are correct in the XML you should be able to move around in the tree in eventghost
If you also check the alternative in the left bottom in eventghost (Log only assigned events) you can verify that you have the right events (HID numbers) connected in the XML
As a reminder the numbers (HID) are very similar for short click and long click and press and release button.
When I get the time I will comment what type of actions there is on each event because it is hard if you don't have the same remote
2015-01-07, 22:01
(2015-01-06, 22:00)MickeJ Wrote: The main problem is that all actions are sending keyboard actions (like up, down, enter) making it hard to verify against Kodi.
Try to disable section Windows and Starter, and activate section AppleRemote (right click menu on each section)
If your remote is correctly installed and the HIDs are correct in the XML you should be able to move around in the tree in eventghost
If you also check the alternative in the left bottom in eventghost (Log only assigned events) you can verify that you have the right events (HID numbers) connected in the XML
As a reminder the numbers (HID) are very similar for short click and long click and press and release button.
When I get the time I will comment what type of actions there is on each event because it is hard if you don't have the same remote
Thank you so much. Once I activated AppleRemote section and added the codes I started getting it to work in Kodi. I have a few more questions please.
1. So what are the different sections (Starter, Windows, AppleRemote) for?
2. I noticed that sometimes it registers say left cursor twice when pressed once. Any tips to correct this?
3. Also, when scrolling in Kodi it moves much slower holding down remote curser button then holding down keyboard curser key. Is there a way to fix this?
4. How would I go about getting this to work with different media software such as MediaPortal? I tried but not all the keys work which is strange bc they have same basic keyboard commands.
2015-01-07, 23:27
Nice that it worked.
The sections are as follows:
- AppleRemote - Handle all Kodi/XBMC events for the Apple Remote
- Starter - Handles activation and deactivation of AppleRemote (so if Kodi is not active stop act on remote events)
- Windows - Handles remote events when Kodi is not active (changyc added that section so be able to start Kodi from the remote - see earlier post)
Regarding the double events, please check the HIDs because the are probably not the same.
For me it's HID.2587EEA508 and HID.2687EEA508 (the second one is the long click event triggered)
Earlier I had a "normal" remote with interaction with XBMC without EventGhost and the scrolling there was the same as for me now, think the remote doesn't send the event as quickly as the keyboard. You can always go one step to the right and scroll a page at a time...
The Apple Remote and EventGhost has nothing to do with Kodi and should work for other things (as the Windows section we have that let you move around in Windows Explorer or Icons and select things). Looks like some trial and error needs to be done.
First start with getting all events that the remote sends (for one click, long click) then create macro in EventGhost, add the event and add an action to the event that sends keyboard-clicks. If you are trying this in my XML please disable all sections so there is no collision.
You can always add an action and manually trigger it in EventGhost to try the keyboard function out.
The sections are as follows:
- AppleRemote - Handle all Kodi/XBMC events for the Apple Remote
- Starter - Handles activation and deactivation of AppleRemote (so if Kodi is not active stop act on remote events)
- Windows - Handles remote events when Kodi is not active (changyc added that section so be able to start Kodi from the remote - see earlier post)
Regarding the double events, please check the HIDs because the are probably not the same.
For me it's HID.2587EEA508 and HID.2687EEA508 (the second one is the long click event triggered)
Earlier I had a "normal" remote with interaction with XBMC without EventGhost and the scrolling there was the same as for me now, think the remote doesn't send the event as quickly as the keyboard. You can always go one step to the right and scroll a page at a time...
The Apple Remote and EventGhost has nothing to do with Kodi and should work for other things (as the Windows section we have that let you move around in Windows Explorer or Icons and select things). Looks like some trial and error needs to be done.
First start with getting all events that the remote sends (for one click, long click) then create macro in EventGhost, add the event and add an action to the event that sends keyboard-clicks. If you are trying this in my XML please disable all sections so there is no collision.
You can always add an action and manually trigger it in EventGhost to try the keyboard function out.
2015-01-08, 00:33
You have been very helpful. I forgot to ask one more question. How do you set this up to run in background including after restart? Does event ghost need to be a startup item?
2015-01-09, 16:11
Is it possible to get the Apple (A1294) remote to work with the built in IR-reciver on the Intel NUC DN2820 (CIR) and and Windows 7?
I had a little test but I couldn't figure it out, any help is appreciated.
I had a little test but I couldn't figure it out, any help is appreciated.
2015-01-21, 01:54
I have managed to get a driver that was made for linux (found at https://github.com/Evinyatar/atvclient/w...buntu-8.04) working on Windows using Cygwin. This makes the official built in IR-receiver work with XBMC. The only problem is it doesn't work after hibernation.
Here are the steps to get it working:
1. Download Cygwin (32 bit only) from http://cygwin.com/setup-x86.exe (The 64-bit version is missing a critical library.)
2. Click next through the setup until the "Select Packages" page.
Select libusb-win32, libusb 1.0-devel, gcc-g++, git, make, automake 1.14, pkg-config.
3. Now finish the installation.
4. Start Cygwin
5. Run "git clone https://github.com/CharlieBashford/atvclient.git". This downloads the atvclient from github.
6. Run "mv /lib/pkgconfig/libusb-1.0.pc /lib/pkgconfig/libusb.pc". This will rename libusb-1.0.pc to libusb.pc.
7. Run "cd atvclient".
8. Run "export 'LIBUSB_LIBS=-lusb-1.0 -lusb'".
9. Run "./configure && make".
10. Run "make install".
10. Plug in the IR reciever, make sure it is installed as a generic HID device using the default Windows drivers. If it is installed as a Apple IR Reciever:
Right click Computer.
Select Manage.
Go to Device Manager.
Right click Apple IR Reciever under Human Interface Devices.
Select "Browse my computer for driver software".
Select "Let me pick from a list of device drivers on my computer".
Select "USB Input Device".
11. Download libusb-win32 from http://sourceforge.net/projects/libusb-w...-releases/. Select the latest version, then select libusb-win32-bin-x.x.x.x.zip. The latest version at the time of writing was 1.2.6.0.
12. Open download, go to bin folder, select inf-wizard.
13. Click Next, Select IR Receiver, then click Next twice. Click Save. Click Install Now. If Windows can't verify the publisher, click "Install this driver software anyway". Click Okay.
14. Add c:/cygwin/bin to your path variable, see http://www.computerhope.com/issues/ch000549.htm#0 for more details.
15. Now run c:/cygwin/usr/local/sbin/atvclient.exe.
Warning: May need to restart computer to save environment variables. If you get an error saying missing cygwin1.dll, you need to restart.
Note: add "-d" argument when running via command prompt to enable debugging.
Optional: Create shortcut to c:/cygwin/usr/local/sbin/atvclient.exe and put it in your startup folder.
Here are the steps to get it working:
1. Download Cygwin (32 bit only) from http://cygwin.com/setup-x86.exe (The 64-bit version is missing a critical library.)
2. Click next through the setup until the "Select Packages" page.
Select libusb-win32, libusb 1.0-devel, gcc-g++, git, make, automake 1.14, pkg-config.
3. Now finish the installation.
4. Start Cygwin
5. Run "git clone https://github.com/CharlieBashford/atvclient.git". This downloads the atvclient from github.
6. Run "mv /lib/pkgconfig/libusb-1.0.pc /lib/pkgconfig/libusb.pc". This will rename libusb-1.0.pc to libusb.pc.
7. Run "cd atvclient".
8. Run "export 'LIBUSB_LIBS=-lusb-1.0 -lusb'".
9. Run "./configure && make".
10. Run "make install".
10. Plug in the IR reciever, make sure it is installed as a generic HID device using the default Windows drivers. If it is installed as a Apple IR Reciever:
Right click Computer.
Select Manage.
Go to Device Manager.
Right click Apple IR Reciever under Human Interface Devices.
Select "Browse my computer for driver software".
Select "Let me pick from a list of device drivers on my computer".
Select "USB Input Device".
11. Download libusb-win32 from http://sourceforge.net/projects/libusb-w...-releases/. Select the latest version, then select libusb-win32-bin-x.x.x.x.zip. The latest version at the time of writing was 1.2.6.0.
12. Open download, go to bin folder, select inf-wizard.
13. Click Next, Select IR Receiver, then click Next twice. Click Save. Click Install Now. If Windows can't verify the publisher, click "Install this driver software anyway". Click Okay.
14. Add c:/cygwin/bin to your path variable, see http://www.computerhope.com/issues/ch000549.htm#0 for more details.
15. Now run c:/cygwin/usr/local/sbin/atvclient.exe.
Warning: May need to restart computer to save environment variables. If you get an error saying missing cygwin1.dll, you need to restart.
Note: add "-d" argument when running via command prompt to enable debugging.
Optional: Create shortcut to c:/cygwin/usr/local/sbin/atvclient.exe and put it in your startup folder.
2015-01-21, 22:53
Sorry for late answer DAlba..
There is a setting in under File -> options to autostart at startup.
There is a setting in under File -> options to autostart at startup.
2015-01-21, 23:24
Hi Nissefisk
Regarding how to make a Apple remote work on a NUC, I have no clue.
If the IR receiver/Transmitter is eHome complaint (or certified whatever they call it), the remote should work.
I only run it on my Mac mini and there I have boot camp installed.
I saw somewhere there, that you could download the drivers extracted (Apple doesn't promote this) from boot camp (have no link so you have to google it), but if the drivers will work with your built in IR receiver I don't know.
If you open Device manager up, what drivers are installed for your IR?
Found this old article about the problem you have that may send you in one direction..
https://uroscion.wordpress.com/2009/01/2...otewithpc/
Good luck
Regarding how to make a Apple remote work on a NUC, I have no clue.
If the IR receiver/Transmitter is eHome complaint (or certified whatever they call it), the remote should work.
I only run it on my Mac mini and there I have boot camp installed.
I saw somewhere there, that you could download the drivers extracted (Apple doesn't promote this) from boot camp (have no link so you have to google it), but if the drivers will work with your built in IR receiver I don't know.
If you open Device manager up, what drivers are installed for your IR?
Found this old article about the problem you have that may send you in one direction..
https://uroscion.wordpress.com/2009/01/2...otewithpc/
Good luck
2015-01-25, 12:12
(2015-01-21, 23:24)MickeJ Wrote: Hi Nissefisk
Regarding how to make a Apple remote work on a NUC, I have no clue.
If the IR receiver/Transmitter is eHome complaint (or certified whatever they call it), the remote should work.
....
Good luck
Thanks MickeJ and CTBC for the help I will give it another go
2016-09-15, 08:03
Sorry for reviving this old thread again but what is the status quo on using the Apple remote on windows (non Apple hardware!) with either an Apple IR controller or the flirc adapter? The second way is easier I assume but is the long press available yet?
2019-01-15, 12:54
(2015-01-21, 01:54)CTBC Wrote: I have managed to get a driver that was made for linux (found at https://github.com/Evinyatar/atvclient/w...buntu-8.04) working on Windows using Cygwin. This makes the official built in IR-receiver work with XBMC. The only problem is it doesn't work after hibernation.Hi! I'm copile atvclient.exe with Cygwin, add libusb ir driver in devices. Trying startup atvclient.exe and got the continues loop with "got nuffing: -22"
Here are the steps to get it working:
1. Download Cygwin (32 bit only) from http://cygwin.com/setup-x86.exe (The 64-bit version is missing a critical library.)
2. Click next through the setup until the "Select Packages" page.
Select libusb-win32, libusb 1.0-devel, gcc-g++, git, make, automake 1.14, pkg-config.
3. Now finish the installation.
4. Start Cygwin
5. Run "git clone https://github.com/CharlieBashford/atvclient.git". This downloads the atvclient from github.
6. Run "mv /lib/pkgconfig/libusb-1.0.pc /lib/pkgconfig/libusb.pc". This will rename libusb-1.0.pc to libusb.pc.
7. Run "cd atvclient".
8. Run "export 'LIBUSB_LIBS=-lusb-1.0 -lusb'".
9. Run "./configure && make".
10. Run "make install".
10. Plug in the IR reciever, make sure it is installed as a generic HID device using the default Windows drivers. If it is installed as a Apple IR Reciever:
Right click Computer.
Select Manage.
Go to Device Manager.
Right click Apple IR Reciever under Human Interface Devices.
Select "Browse my computer for driver software".
Select "Let me pick from a list of device drivers on my computer".
Select "USB Input Device".
11. Download libusb-win32 from http://sourceforge.net/projects/libusb-w...-releases/. Select the latest version, then select libusb-win32-bin-x.x.x.x.zip. The latest version at the time of writing was 1.2.6.0.
12. Open download, go to bin folder, select inf-wizard.
13. Click Next, Select IR Receiver, then click Next twice. Click Save. Click Install Now. If Windows can't verify the publisher, click "Install this driver software anyway". Click Okay.
14. Add c:/cygwin/bin to your path variable, see http://www.computerhope.com/issues/ch000549.htm#0 for more details.
15. Now run c:/cygwin/usr/local/sbin/atvclient.exe.
Warning: May need to restart computer to save environment variables. If you get an error saying missing cygwin1.dll, you need to restart.
Note: add "-d" argument when running via command prompt to enable debugging.
Optional: Create shortcut to c:/cygwin/usr/local/sbin/atvclient.exe and put it in your startup folder.
Any ideas?
