[art76]

Hi All,
Wonder if anyone has had this issue since going to Dharma Beta 1 or 2. Basically, since upgrading from 9.11 to Dharma Beta I have lost the ability to put my volume up "+" via my remote control.

My harmony remote is setup as an MCE keyboard and so I can open notepad, hit volume up and it types a "+" into notepad, but in xbmc nada. I CAN hit "+" on my pc keyboard and that still puts the volume up as expected.

Just not sure why it's not taking the command from the remote...

Platform: Windows 7, 32-bit build 7600. Built on Sep 13 2010 (SVN:33776, compiler 1500)
HP MCE Remote receiver and Logitich Harmony 525 remote setup for MCE Keyboard (I have tested with the original HP MCE remote too but no go either)
Dharma Beta 1 and Beta 2 now.

[Homerboy]

See my thread here:
http://forum.xbmc.org/showthread.php?p=610213

Though I haven't been able to fix it

[jhsrennie]

See my thread here:
http://forum.xbmc.org/showthread.php?p=610213

Though I haven't been able to fix it

Fortunately my slip-up didn't get into Dharma beta 2. It would only have affected you if you're using an unofficial nightly build, or if you downloaded my mceremote.zip and used my customised keyboard.xml.

Try pressing Windows-R, or Start-Run, and typing:

Code:

%appdata%\xbmc

This should open an Explorer window and there should be a folder called "userdata". Double-click into this folder then double-click into the folder called "keymaps". If there is a file there called keyboard.xml move or delete the file. That should fix the volume control problem.

JR

[Homerboy]

Fortunately my slip-up didn't get into Dharma beta 2. It would only have affected you if you're using an unofficial nightly build, or if you downloaded my mceremote.zip and used my customised keyboard.xml.

Try pressing Windows-R, or Start-Run, and typing:

Code:

%appdata%\xbmc

This should open an Explorer window and there should be a folder called "userdata". Double-click into this folder then double-click into the folder called "keymaps". If there is a file there called keyboard.xml move or delete the file. That should fix the volume control problem.

JR

Ah see there's my prob.
I tried out the last build from http://www.sshcs.com/xbmc/
I guess I should just revert back to the actual beta2 and not mess with nightly builds.

[art76]

Thanks Homerboy but that hasn't helped. For all intents it "should" be working. My remote is sending a valid "+" keyboard key on pressing volume up but for some reason my xbmc just isn't liking it.

Saved some debug logs and found something weird though:-

Pressing volume down on the remote (which sends a "-") I get :-
21:18:41 T:7532 M:1276018688 DEBUG: SDLKeyboard: scancode: 12, sym: 45, unicode: 45, modifier: 0
21:18:41 T:7532 M:1276018688 DEBUG: CApplication::OnKey: 61629 pressed, action is VolumeDown
21:18:41 T:7532 M:1276018688 DEBUG: SDLKeyboard: scancode: 12, sym: 45, unicode: 45, modifier: 0
21:18:41 T:7532 M:1276018688 DEBUG: CApplication::OnKey: 61629 pressed, action is VolumeDown

Pressing volume up on the remote (sends a "+") I get - with nothing after action is :-
21:18:43 T:7532 M:1275830272 DEBUG: SDLKeyboard: scancode: 42, sym: 304, unicode: 0, modifier: 1
21:18:43 T:7532 M:1275830272 DEBUG: CApplication::OnKey: 192672 pressed, action is
21:18:43 T:7532 M:1275830272 DEBUG: SDLKeyboard: scancode: 13, sym: 61, unicode: 43, modifier: 1
21:18:43 T:7532 M:1275830272 DEBUG: CApplication::OnKey: 192699 pressed, action is


And then pressing "+" on my keyboard which does raise the volume gives me an action is item :-
21:18:46 T:7532 M:1277517824 DEBUG: SDLKeyboard: scancode: 78, sym: 270, unicode: 43, modifier: 0
21:18:46 T:7532 M:1277517824 DEBUG: CApplication::OnKey: 61627 pressed, action is VolumeUp
21:18:46 T:7532 M:1277509632 DEBUG: SDLKeyboard: scancode: 78, sym: 270, unicode: 43, modifier: 0
21:18:46 T:7532 M:1277509632 DEBUG: CApplication::OnKey: 61627 pressed, action is VolumeUp

Just weird, not sure if there is something I can delete/clear to reset something to get this going again.
And just doubly weird that I can press plus on the keyboard + or volume up on the remote + and get a + into this post so the same thing but just not being recognised the same within xbmc.

If anyone has any other suggestions please let me know and I'll keep plugging away too.

[art76]

So, looking at it a bit more, is it not working because for some reason the + from me remote and from my keyboard are giving out different ID's?

Remote seems to be sending two id's 192672 and 192699, where as the keyboard is just sending the one 61627. Although not sure how these work yet.

It does seem odd that the remote sends out the "+" in a number range far away from the what my keyboard does. I'm pretty sure my "-" is the same from both remote and keyboard tho..

[jhsrennie]

192699 is hex 2F0BB, which is shift-+. 192672 is 2F0A0, which is a left shift keypress.

So your remote is sending a left shift keydown then a + keydown and this is confusing XBCM. You could try creating a keyboard.xml in your userdata\keymaps folder containing:

Code:

<keymap>
  <global>
    <keyboard>
      <plus mod="shift">VolumeUp</plus>
    </keyboard>
  </global>
</keymap>

Whether this would work I'm not sure. The most effective fix is to use a different remote.

JR

[art76]

Cheers JR will give that a go.

I'll probably have to keep trying to sort this one out as it seems to be the same on two remotes i have, the Harmony 525 and the standard HP MCE remote.

Just weird that it only started having the issue after I installed Dharma...

Have to see if I can fix it via eventghost if nothing else does, which won't be too bad as was going to use it for program switching anyway...

Anyway, will post back if that keyboard.xml fixes it.

A76

[jhsrennie]

Just weird that it only started having the issue after I installed Dharma...

Prior to Dharma XBMC ignored the state of the shift, control and alt keys so shift-plus would be treated as plus and would increase the volume.

I'll probably have to keep trying to sort this one out as it seems to be the same on two remotes i have, the Harmony 525 and the standard HP MCE remote.

Remember it's the IR receiver that matters, not the handset. If the Harmony and HP remote are using the same receiver they will behave in the same way.

JR

[art76]

Adding the modifier to keyboard.xml DID help in the end. Seems the PC needs to be rebooted for it to take effect and not just restarting xbmc..

Thanks for the info JR.