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
Hauppauge PVR150, IR driver issue ??
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="Lawrence" data-source="post: 38345" data-attributes="member: 18495"><p>I have the exact same problem. In order to save you some time I'll explain a few things here that happen on my system.</p><p></p><p>1. If you have MCE installed and it works with the Hauppage remote (i.e. changes channels on the STB) it's probably using the MS eHome Infrared driver, not the Hauppage driver. Go to Control Panel / Hardware / USB Devices and click on the eHome receiver. If it's using the eHome driver the Hauppauge driver won't work.</p><p></p><p>2. With that said the red text in the remote setup apparently is displayed because the Hauppauge drive cannot see the hardware. Even though the remote input works fine with MP (because the eHome driver is setup for receiving MCE remote commands) you may not (I and many others don't) get any IR output because MP's output doesn't communicate with the MS eHome driver.</p><p></p><p>3. As of yet I've found not way to make MP pass data to the MS eHome driver so there is no IR output.</p><p></p><p>4. If you run the Hauppauge IR setup program and it says "Can't detect hardware" then you are in the same boat as I am, the MS eHome driver apparently has exclusive control over the hardware.</p><p></p><p>5. If 4 is true for you then the My Blaster app probably won't work either since it can't talk to the hardware either in my case. The buttons on the app that allow learning commands and such never get "enabled" for use.</p><p></p><p>So there you have it. Your remote (my remote) can do everything in MP but change channels on a STB. I'm sure other systems configured differently don't have this problem but many do.</p><p></p><p>You can use HIP to change channels on your STB via blaster but when you change channels inside of MP using the guide those commands don't get sent to the eHome driver. I'm currently considering ways to permanently disable the eHome driver to see if the Hauppage driver works then. </p><p></p><p>If you find a solution let me know. Hope this saved you a little time. MP is an awesome program... hopefully some ambitious proggie will address this.</p><p></p><p>Lawrence</p></blockquote><p></p>
[QUOTE="Lawrence, post: 38345, member: 18495"] I have the exact same problem. In order to save you some time I'll explain a few things here that happen on my system. 1. If you have MCE installed and it works with the Hauppage remote (i.e. changes channels on the STB) it's probably using the MS eHome Infrared driver, not the Hauppage driver. Go to Control Panel / Hardware / USB Devices and click on the eHome receiver. If it's using the eHome driver the Hauppauge driver won't work. 2. With that said the red text in the remote setup apparently is displayed because the Hauppauge drive cannot see the hardware. Even though the remote input works fine with MP (because the eHome driver is setup for receiving MCE remote commands) you may not (I and many others don't) get any IR output because MP's output doesn't communicate with the MS eHome driver. 3. As of yet I've found not way to make MP pass data to the MS eHome driver so there is no IR output. 4. If you run the Hauppauge IR setup program and it says "Can't detect hardware" then you are in the same boat as I am, the MS eHome driver apparently has exclusive control over the hardware. 5. If 4 is true for you then the My Blaster app probably won't work either since it can't talk to the hardware either in my case. The buttons on the app that allow learning commands and such never get "enabled" for use. So there you have it. Your remote (my remote) can do everything in MP but change channels on a STB. I'm sure other systems configured differently don't have this problem but many do. You can use HIP to change channels on your STB via blaster but when you change channels inside of MP using the guide those commands don't get sent to the eHome driver. I'm currently considering ways to permanently disable the eHome driver to see if the Hauppage driver works then. If you find a solution let me know. Hope this saved you a little time. MP is an awesome program... hopefully some ambitious proggie will address this. Lawrence [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
General Support
Hauppauge PVR150, IR driver issue ??
Contact us
RSS
Top
Bottom