iMon remote control broken after june 1st?
#1
Hello

Is anyone else having problems with remote controls in recent builds? For me, the June 1st build (XBMCSetup-20120601-cdd9c64-master.exe) is the last one which will respond to remote control commands. From XBMCSetup-20120602-512d1d9-master.exe and onwards (I've tried most, including today's build), only keyboard input is working.

Reinstalling the june 1st build (no uninstalling, cleaning out userdata or anything like that, just plain install) reenables remote control support.

My setup is
- Windows 7
- Harmony remote set up as a Windows Media Center remote in iMon
- iMon is sending keyboard commands to XBMC (afaik)

Best regards,
Durniplot



Reply
#2
I believe I'm experiencing something similar. I lost the iMon remote some time ago, but I do still have the iMon LCD /receiver on my HTPC case. On all the builds after June 1st, Windows periodically (every 5 seconds or so) plays an alert like I have plugged in a USB device, and when I check in device manager one of my HID devices shows up with an exclamation point.
Reply
#3
I have the same problem too (iMon LCD w/ remote). went back to the april merge of XBMC HD audio.
@durniplot: can you upload the June 1st build of XBMC?, theres no build older than June 9th in the nightlies section.
Reply
#4
I have the same problem, funny I thought it was just me and not loading the right drivers Smile

Is this something that can be captured in a log? I noticed that the device manager only starts to complain when XBMC is running.
Reply
#5
Same here! Sad

I've googled the issue a bit and found something that describes this exact behavior. It turns out its a non-XBMC yet a known issue.

Here is the official FAQ from SoundGraph website: http://www.soundgraph.com/forums/faq.php...nager_g_01 (Scroll down till you reach the section named "The iMon Device Disconnection problem with Game Controller")

Basically, they state that "the problem occurs because Windows DirectInput Device Enumeration API function requests the ‘device description string’ of iMon hardware even it talks to Windows that it does not support the description string.Apparently no iMon drivers can or are planned to fix the issue."

They suggest that "iMon device should be disabled before the Windows DirectInput Device Enumeration API function is called". Well, such an approach sucks for those who use iMon for the remote control as you would lose it if you disable the device.

I hope this would help somebody with more profound programming knowledge than mine and eventually turn into a bug fix.
Reply
#6
(2012-06-27, 10:13)gregnukem Wrote: Same here! Sad

I've googled the issue a bit and found something that describes this exact behavior. It turns out its a non-XBMC yet a known issue.

Here is the official FAQ from SoundGraph website: http://www.soundgraph.com/forums/faq.php...nager_g_01 (Scroll down till you reach the section named "The iMon Device Disconnection problem with Game Controller")

Basically, they state that "the problem occurs because Windows DirectInput Device Enumeration API function requests the ‘device description string’ of iMon hardware even it talks to Windows that it does not support the description string.Apparently no iMon drivers can or are planned to fix the issue."

They suggest that "iMon device should be disabled before the Windows DirectInput Device Enumeration API function is called". Well, such an approach sucks for those who use iMon for the remote control as you would lose it if you disable the device.

I hope this would help somebody with more profound programming knowledge than mine and eventually turn into a bug fix.

but why does this error occur according to durniplot only with xbmc builds newer than June 1st Huh
Reply
#7
(2012-06-27, 11:15)spooky Wrote: but why does this error occur according to durniplot only with xbmc builds newer than June 1st Huh

They (developers) must have changed something in the code that keeps polling devices in a manner that causes errors. Probably this was done to solve some other bug.
Reply
#8
What version of Windows 7 are you running? I did not have this problem when I was running the 32 bit version, when I rebuilt my HTPC I went with 64 bit.

Just trying to pair down is it the OS or version of XBMC.
Reply
#9
I have exactly the same problem. After updating to a newer nightly I cannot use the Imon manager anymore because it disables itself. Really anyoing. Maybe some developers can shed a light on this issue?
Reply
#10
@jhusch I'm on 64 bit also
@spooky Will try to drop the June 1st build somewhere for you

I'm sort of happy I''m not the only one with this problem - thought I was the one doing something wrong Smile Let's hope it is fixable. Someone with a clue could perhaps review code changes committed from 31/5 to 2/6?

http://trac.xbmc.org/timeline?from=06%2F...ate=Update

I think there was something about removing some old SDL joystick controller code that might be related...?

https://github.com/xbmc/xbmc/commit/a553...4bda381f45
https://github.com/xbmc/xbmc/commit/0cbb...d7d9013113
https://github.com/xbmc/xbmc/commit/7ce8...ab64ed2770

Best regards,
Durniplot
Reply
#11
Yep, the XBMC Dev team are the only ones who can fix it. Soundgraph said it could be fixed but they don't support firmware update:

http://www.soundgraph.com/forums/showthread.php?t=10536

We're at the mercy of the dev's here.
Reply
#12
Did anyone submit a bug report yet?
Reply
#13
yes,

http://trac.xbmc.org/ticket/13146

Reply
#14
(2012-06-29, 13:10)ZFLaSH76 Wrote: yes,
http://trac.xbmc.org/ticket/13146
And it's not only bug report, but is a patch too.

Reply
#15
I saw that Smile Let's hope they merge it. Good work Karlson!
Reply

Logout Mark Read Team Forum Stats Members Help
iMon remote control broken after june 1st?1