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
Considering upgrading and iMON
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: 1286587" data-attributes="member: 141969"><p>I was looking on the Flirc web site and I noticed this statement:</p><p style="margin-left: 20px"><em>flirc acts as a keyboard</em></p><p>That is a significant fact that <em>may</em> point to the source of your problems.</p><p></p><p>A standard Microsoft MCE RC6 remote control transmits signals which are usually received by an MCE RC6 IR receiver that is controlled by the "Microsoft eHome Infrared Transceiver" driver. Your Xsight remote with code set 1272 will be transmitting those signals.</p><p></p><p>The Flirc built-in profile for MCE RC6 should be able to recognise those signals, but because the Flirc appears as a keyboard, it won't be handled by the "Microsoft eHome Infrared Transceiver" driver. Instead it will be handled by the standard Windows keyboard driver. The significance of this is that the Flirc will be generating <strong>WMC keyboard shortcuts</strong>; it won't be generating <strong>MP keyboard shortcuts</strong>. Sadly, although some MP shortcuts are the same as WMC shortcuts, others differ, and so those won't be recognised by MP and the buttons will appear to do nothing.</p><p></p><p>I have just looked at an older post of mine, and according to that post the following buttons use keyboard shortcuts that are common to MP and WMC (so these buttons should work without change):</p><p style="margin-left: 20px"><em>up; down; left; right; ok; channel up; channel down; </em></p> <p style="margin-left: 20px"><em>volume up; volume down; numeric digits.</em></p><p>The other buttons use MP keyboard shortcuts that are different from WMC keyboard shortcuts, so those buttons won't work. I would suggest trying the following, which <em>may</em> work:</p><ul> <li data-xf-list-type="ul">Set your Xsight remote to use code set 1272 (you have probably already done this).</li> <li data-xf-list-type="ul">Use the built-in Flirc profile for Microsoft WMC. Don't learn any of these buttons, as learns are often inferior to pre-defined codes.</li> <li data-xf-list-type="ul">For the buttons on the remote that are absent from the Flirc profile you will have to use learns.</li> <li data-xf-list-type="ul">For the learned buttons, you must <strong>define</strong> the keyboard shortcut that you want Flirc to send to MP.</li> <li data-xf-list-type="ul">For the built-in buttons, you must <strong>redefine</strong> those that differ between MP and WMC so that Flirc sends the MP shortcut instead of sending the WMC shortcut.</li> <li data-xf-list-type="ul">Finally I think that you should <strong>disable HID</strong> in "MP Config". This will cause MP to revert to using the old keyboard interface, which I think has a better chance of working.</li> </ul><p>-- from CyberSimian in the UK</p></blockquote><p></p>
[QUOTE="CyberSimian, post: 1286587, member: 141969"] I was looking on the Flirc web site and I noticed this statement: [INDENT][I]flirc acts as a keyboard[/I][/INDENT] That is a significant fact that [I]may[/I] point to the source of your problems. A standard Microsoft MCE RC6 remote control transmits signals which are usually received by an MCE RC6 IR receiver that is controlled by the "Microsoft eHome Infrared Transceiver" driver. Your Xsight remote with code set 1272 will be transmitting those signals. The Flirc built-in profile for MCE RC6 should be able to recognise those signals, but because the Flirc appears as a keyboard, it won't be handled by the "Microsoft eHome Infrared Transceiver" driver. Instead it will be handled by the standard Windows keyboard driver. The significance of this is that the Flirc will be generating [B]WMC keyboard shortcuts[/B]; it won't be generating [B]MP keyboard shortcuts[/B]. Sadly, although some MP shortcuts are the same as WMC shortcuts, others differ, and so those won't be recognised by MP and the buttons will appear to do nothing. I have just looked at an older post of mine, and according to that post the following buttons use keyboard shortcuts that are common to MP and WMC (so these buttons should work without change): [INDENT][I]up; down; left; right; ok; channel up; channel down; [/I][/INDENT] [INDENT][I]volume up; volume down; numeric digits.[/I][/INDENT] The other buttons use MP keyboard shortcuts that are different from WMC keyboard shortcuts, so those buttons won't work. I would suggest trying the following, which [I]may[/I] work: [LIST] [*]Set your Xsight remote to use code set 1272 (you have probably already done this). [*]Use the built-in Flirc profile for Microsoft WMC. Don't learn any of these buttons, as learns are often inferior to pre-defined codes. [*]For the buttons on the remote that are absent from the Flirc profile you will have to use learns. [*]For the learned buttons, you must [B]define[/B] the keyboard shortcut that you want Flirc to send to MP. [*]For the built-in buttons, you must [B]redefine[/B] those that differ between MP and WMC so that Flirc sends the MP shortcut instead of sending the WMC shortcut. [*]Finally I think that you should [B]disable HID[/B] in "MP Config". This will cause MP to revert to using the old keyboard interface, which I think has a better chance of working. [/LIST] -- from CyberSimian in the UK [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
General Support
Considering upgrading and iMON
Contact us
RSS
Top
Bottom