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 1
Support
General Support
TV Guide screen bug and usability
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="CyberSimian" data-source="post: 1096782" data-attributes="member: 141969"><p>I have not been able to identify the cause of the problem, but I have been able to devise a work-around that will give a usable system until such time as the problem is fixed. Unfortunately, the work-around requires the use of additional software and additional hardware. Luckily, I already had the additional hardware, so this work-around has cost me nothing.</p><p></p><p>The Microsoft MCE remote control uses RC6 infra-red protocol. MCE-compatible remote controls from other manufacturers may or may not use RC6 protocol. You can tell if they do by plugging in the infra-red receiver, and then going to "Device Manager" in Windows "Control Panel", and looking at the entry for the IR receiver; if it is described as "eHome Infrared Transceiver", it uses RC6 protocol.</p><p></p><p>One of the MCE compatible remotes that <em>does not</em> use RC6 protocol is the Ortek VRC-1100. This is also sold under other brand names, such as the Adesso ARC-1100, the Gmyle, and the Hama 00052451. I have the Hama version. If you plug in the Ortek IR receiver, you will find that it appears to Windows as a keyboard plus a mouse. So the Ortek remote sends Ortek IR protocol to the Ortek receiver, which then converts the button presses into keyboard short-cuts, and passes those keystrokes to the operating system.</p><p></p><p>The problem with this is that the MCE short-cuts are (mostly) different from the MP short-cuts, so MP (mostly) ignores the keystrokes. A few short-cuts are the same, such as the ones corresponding to the OK, LEFT, RIGHT, UP, DOWN, VOL-UP, VOL-DOWN buttons on the remote. To get MP to respond to all of the buttons on the Ortek remote, you have to use some additional software, and I used AutoHotKey.</p><p></p><p>I tested this by creating an AutoHotKey script for the FORWARD and REWIND buttons. In MCE, the keyboard short-cuts for these buttons are CTRL+SHIFT+F (for FORWARD) and CTRL+SHIFT+B (for REWIND). So the AutoHotKey script maps these two keystrokes to F6 and F5 respectively (these are the MP keyboard short-cuts for FORWARD and REWIND). This is the script:</p><p></p><p>[code]^+b::f5</p><p>^+f::f6[/code]</p><p></p><p>I am pleased to report that this script solves the problem with the FORWARD and REWIND buttons. When playing recorded TV, if you press the GUIDE button, the EPG appears with recorded TV continuing to play in a thumbnail TV screen. Pressing the FORWARD button on the Ortek remote control now scrolls the EPG to the right by 3 hours, and does not affect the recorded TV playing in the thumbnail TV screen. The REWIND button similarly works correctly.</p><p></p><p>So the Ortek remote control plus Ortek IR receiver plus AutoHotKey provides a work-around for this problem. I am going to create an AutoHotKey script for the complete set of buttons on the Ortek remote, to provide a complete solution; I will post it when I have completed and tested it.</p><p></p><p>One final point: you <em>do</em> need to use the Ortek IR receiver, but you do not have to use the Ortek remote control. I have never used Harmony universal remotes, but I understand that their database includes several different protocols for MCE, so one of them might be Ortek protocol (check this if you are contemplating buying a Harmony). However, I have used One-For-All programmable remotes. I don't think that any OFA remote has Ortek protocol built-in, but by using an appropriate cable and the RMIR tool (free download from <a href="http://www.hifi-remote.com" target="_blank">www.hifi-remote.com</a>), you can load the Ortek protocol into the remote. I have done this with an OFA Xsight Colour remote (the usability of this remote is decidedly indifferent), and I intend loading Ortek protocol into my OFA Xsight Lite remote for longer-term use with MP (the "Lite" has better usability than the "Colour", in my view).</p><p></p><p>-- from CyberSimian in the UK</p></blockquote><p></p>
[QUOTE="CyberSimian, post: 1096782, member: 141969"] I have not been able to identify the cause of the problem, but I have been able to devise a work-around that will give a usable system until such time as the problem is fixed. Unfortunately, the work-around requires the use of additional software and additional hardware. Luckily, I already had the additional hardware, so this work-around has cost me nothing. The Microsoft MCE remote control uses RC6 infra-red protocol. MCE-compatible remote controls from other manufacturers may or may not use RC6 protocol. You can tell if they do by plugging in the infra-red receiver, and then going to "Device Manager" in Windows "Control Panel", and looking at the entry for the IR receiver; if it is described as "eHome Infrared Transceiver", it uses RC6 protocol. One of the MCE compatible remotes that [i]does not[/i] use RC6 protocol is the Ortek VRC-1100. This is also sold under other brand names, such as the Adesso ARC-1100, the Gmyle, and the Hama 00052451. I have the Hama version. If you plug in the Ortek IR receiver, you will find that it appears to Windows as a keyboard plus a mouse. So the Ortek remote sends Ortek IR protocol to the Ortek receiver, which then converts the button presses into keyboard short-cuts, and passes those keystrokes to the operating system. The problem with this is that the MCE short-cuts are (mostly) different from the MP short-cuts, so MP (mostly) ignores the keystrokes. A few short-cuts are the same, such as the ones corresponding to the OK, LEFT, RIGHT, UP, DOWN, VOL-UP, VOL-DOWN buttons on the remote. To get MP to respond to all of the buttons on the Ortek remote, you have to use some additional software, and I used AutoHotKey. I tested this by creating an AutoHotKey script for the FORWARD and REWIND buttons. In MCE, the keyboard short-cuts for these buttons are CTRL+SHIFT+F (for FORWARD) and CTRL+SHIFT+B (for REWIND). So the AutoHotKey script maps these two keystrokes to F6 and F5 respectively (these are the MP keyboard short-cuts for FORWARD and REWIND). This is the script: [code]^+b::f5 ^+f::f6[/code] I am pleased to report that this script solves the problem with the FORWARD and REWIND buttons. When playing recorded TV, if you press the GUIDE button, the EPG appears with recorded TV continuing to play in a thumbnail TV screen. Pressing the FORWARD button on the Ortek remote control now scrolls the EPG to the right by 3 hours, and does not affect the recorded TV playing in the thumbnail TV screen. The REWIND button similarly works correctly. So the Ortek remote control plus Ortek IR receiver plus AutoHotKey provides a work-around for this problem. I am going to create an AutoHotKey script for the complete set of buttons on the Ortek remote, to provide a complete solution; I will post it when I have completed and tested it. One final point: you [i]do[/i] need to use the Ortek IR receiver, but you do not have to use the Ortek remote control. I have never used Harmony universal remotes, but I understand that their database includes several different protocols for MCE, so one of them might be Ortek protocol (check this if you are contemplating buying a Harmony). However, I have used One-For-All programmable remotes. I don't think that any OFA remote has Ortek protocol built-in, but by using an appropriate cable and the RMIR tool (free download from [url="http://www.hifi-remote.com"]www.hifi-remote.com[/url]), you can load the Ortek protocol into the remote. I have done this with an OFA Xsight Colour remote (the usability of this remote is decidedly indifferent), and I intend loading Ortek protocol into my OFA Xsight Lite remote for longer-term use with MP (the "Lite" has better usability than the "Colour", in my view). -- from CyberSimian in the UK [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
General Support
TV Guide screen bug and usability
Contact us
RSS
Top
Bottom