home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 2
General
Pause and Play do not work with remote
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="sridharb" data-source="post: 1242410" data-attributes="member: 58216"><p>I do not see eHome Infrared Transceiver in my Human Interface Devices section (see attached image).</p><p></p><p>If that means that it is not compatible, it is probably not.</p><p></p><p>My hope that it would be easy to fix came from the fact that Windows recognizes the commands that MP2 doesn't. More importantly MP1 does. So, isn't it just a matter of adding support for the command that is probably being ignored at the moment? And we know how it is to be done?</p><p></p><p>How does one go about know where the ball is dropped? That is - how to identify whether the remote command is reaching MP2 and then being ignored? How to identify what other commands are reaching MP2? Is there a command logger (like the Debug Client of IRSS) that will tell me what commands are reaching MP2? Is it then a matter of mapping something new in DefaultRemoteMap.xml?</p></blockquote><p></p>
[QUOTE="sridharb, post: 1242410, member: 58216"] I do not see eHome Infrared Transceiver in my Human Interface Devices section (see attached image). If that means that it is not compatible, it is probably not. My hope that it would be easy to fix came from the fact that Windows recognizes the commands that MP2 doesn't. More importantly MP1 does. So, isn't it just a matter of adding support for the command that is probably being ignored at the moment? And we know how it is to be done? How does one go about know where the ball is dropped? That is - how to identify whether the remote command is reaching MP2 and then being ignored? How to identify what other commands are reaching MP2? Is there a command logger (like the Debug Client of IRSS) that will tell me what commands are reaching MP2? Is it then a matter of mapping something new in DefaultRemoteMap.xml? [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 2
General
Pause and Play do not work with remote
Contact us
RSS
Top
Bottom