[roidy]

Hi there, I need help setting up my new Mele F10 remote. There's a couple of other threads about this remote but they don't seem to solve the problems I'm having. I've tried it with both Windows and OpenELEC version of XBMC and these are my findings.

1. The keyboard works perfectly and is great.
2. The remote contains only one button that generates an IR signal and that is the power button, which I have no interest in as I have no IR reciever.
3. Some of the buttons on the remote side generate key codes and these work fine.
4. Some of the buttons on the remote side generate no key codes and I have no idea how to use these in XBMC.
5. Some of the buttons on the remote side are mouse buttons and I have no idea how to use them in XBMC.

The following image shows which buttons generate which key codes and which don't work:-


I have the mouse turned off in XBMC so that moving the remote dosen't make the mouse pointer appear.

Any help setting up the button that don't return key codes and the mouse buttons would be great. Thanks

[roidy]

Ok so it seems you can rebind the mouse buttons in keyboard.xml using the <mouse> section, however they only work if the mouse in turned on in XBMC and this means that the mouse pointer will be visible and will move all over the screen because of the airmouse part of the remote

The only work around I've found is to replace the images of the mouse pointer in the skin I'm using with blank transparent png files so you can't see the mouse pointer. This poses a problem in that if the skin uses a Textures.xbt file, which I think they all do, then placing new mouse images in the skins media folder wont work. You need to remove the Textures.xbt file and replace with all the uncompressed images for which ever skin it is..... What XBMC really needs is a way to disable the mouse pointer but still read the mouse buttons.

[Novin]

Can help you with one more button, the tv-button. Details here:

http://minixforums.com/threads/mele-f10-...-etc.1323/

[roidy]

Not sure which button you mean, point it out or describe it on the images above.

[jackandjohn]

Not sure which button you mean, point it out or describe it on the images above.

Based on the diagram in the document linked from http://minixforums.com/threads/mele-f10-...-etc.1323/ , I'd say that the "tv-button" mentioned is the button with the arrow coming out of a square that you have marked as returning no keycode.

There's also a discussion on this remote here: http://openelec.tv/forum/103-infared-rem...e?start=12 , and that that discussion ends up with a solution that uses userdata/keymaps/airmouse.xml (which I can't find documentation on, but assume is just a handy name since XBMC loads everything in that folder)

This file is again mentioned here: http://blog.ithasu.org/2013/04/driving-x...air-mouse/ , with the interesting part being this section in airmouse.xml:

Code:

<mouse>
      <leftclick>Select</leftclick>
      <rightclick>PreviousMenu</rightclick>
      <mousedrag>noop</mousedrag>
      <mousemove>noop</mousemove>
</mouse>

This mouse/keyboard/remote combo is SO CLOSE to the ideal XBMC/HTPC remote...

If someone could make a unit like this with rw/play/pause/ff buttons, and the ability to custom program the remote's buttons via firmware (make centre button send the enter key, etc) instead of requiring software changes, and keep the unit under $40, it would be an easy sell for sure.

[camelbl]

hey Roidy

I ran into the same issue like you... concerning the mouse buttons problem I found a sweet solution in this thread here (XBMC on Win 7):

http://forum.xbmc.org/showthread.php?tid=142694 (go straight to the later posts on page 3)

it takes the approach from redefining what keys are sent from the remote on the OS level... the mouse clicks get converted into keyboard keys.. so switch off the mouse in XBMC and all is fine

make sure to run these things right at startup... if needed, make some changes in keyboard.xml too..

otherwise I also have some keys not sending any code to the computer which is annoying... have you found any solution for the dead keys?

cheers

[tekno]

It seems last I tested a mele The ones you have marked as returning no keycode are in fact IR codes. Asxd I recall I tested this with a camera that was sensitive to IR, but not with an actual IR receiver

I also suggest that yes this could be the ultimate HTPC remote and on The Raspberry Pi this is a great compliment to the mele

http://msl-digital-solutions.myshopify.c...epi-board/

Of course if the power off is not important you could also just use a GPIO IR on the raspberry Pi and map those IR buttons to something useful which might be

Aspect Ratio, Subtitles, and Audio track