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
Installation, configuration support
Setting up Hauppauge Colossus IR blaster blues...
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="mm1352000" data-source="post: 879870" data-attributes="member: 82144"><p>Hi again Steve</p><p> </p><p>To me it looks like the blaster is/was trying to work. Part of the problem seems to be that at least some of your channels are/were not configured correctly. The last two channels that you tried to tune in the logs did this:</p><p></p><p>Then an error before the blaster got a chance to do the real work:</p><p></p><p>For the Colossus (and HD-PVR), PMT timeouts/errors occur when the video stream is not detected by the driver... which indicates that the wrong input is selected. The Colossus obviously doesn't have a tuner input. The re-import that you did from SD after that should help with this - looks like you set the video and audio inputs in there correctly...</p><p>Previous to that, you tried some other channels which seem to have been closer to working, but then you really did get blaster errors:</p><p></p><p>...</p><p></p><p>That UIR thing is critical - if that doesn't work then nothing will work. There is absolutely zero documentation about what the error code might mean. Apparently the value that is meant to be returned is 0, but beyond that I don't know what is going on there...</p><p>Might pay to have a read --><a href="https://forum.team-mediaportal.com/threads/using-hauppauge-ir-blaster-with-mp.49578/reply?quote=349346" target="_blank">here</a><--. That thread seems to be where this Hauppauge option was added to the blaster, and ralphy (the coder I assume) was quite good with responding to people. He suggests you need to close other applications including BlastCfg and restart after that error occurs. His setup instructions are --><a href="https://forum.team-mediaportal.com/threads/using-hauppauge-ir-blaster-with-mp.49578/page-2#post-342913" target="_blank">here</a><--.</p><p>(Maybe you saw that thread before and thought the info was obsolete - I would say it is probably still relevant.)</p><p>Previous to that again, when I look at the blaster loading I see:</p><p></p><p>...</p><p></p><p>I can't comment on whether any of that is correct - perhaps you are able to check it against the configuration that you set when loading BlastCfg. I do note the minimum digits there is 3 and on quite a few occasions you've tried to blast to channel 11, 12 etc. - that could be an issue. I note that ralphy explicitly mentions that --><a href="https://forum.team-mediaportal.com/threads/using-hauppauge-ir-blaster-with-mp.49578/reply?quote=346326" target="_blank">here</a><--.</p><p>Does that help?</p><p>mm</p></blockquote><p></p>
[QUOTE="mm1352000, post: 879870, member: 82144"] Hi again Steve To me it looks like the blaster is/was trying to work. Part of the problem seems to be that at least some of your channels are/were not configured correctly. The last two channels that you tried to tune in the logs did this: Then an error before the blaster got a chance to do the real work: For the Colossus (and HD-PVR), PMT timeouts/errors occur when the video stream is not detected by the driver... which indicates that the wrong input is selected. The Colossus obviously doesn't have a tuner input. The re-import that you did from SD after that should help with this - looks like you set the video and audio inputs in there correctly... Previous to that, you tried some other channels which seem to have been closer to working, but then you really did get blaster errors: ... That UIR thing is critical - if that doesn't work then nothing will work. There is absolutely zero documentation about what the error code might mean. Apparently the value that is meant to be returned is 0, but beyond that I don't know what is going on there... Might pay to have a read -->[URL='https://forum.team-mediaportal.com/threads/using-hauppauge-ir-blaster-with-mp.49578/reply?quote=349346']here[/URL]<--. That thread seems to be where this Hauppauge option was added to the blaster, and ralphy (the coder I assume) was quite good with responding to people. He suggests you need to close other applications including BlastCfg and restart after that error occurs. His setup instructions are -->[URL='https://forum.team-mediaportal.com/threads/using-hauppauge-ir-blaster-with-mp.49578/page-2#post-342913']here[/URL]<--. (Maybe you saw that thread before and thought the info was obsolete - I would say it is probably still relevant.) Previous to that again, when I look at the blaster loading I see: ... I can't comment on whether any of that is correct - perhaps you are able to check it against the configuration that you set when loading BlastCfg. I do note the minimum digits there is 3 and on quite a few occasions you've tried to blast to channel 11, 12 etc. - that could be an issue. I note that ralphy explicitly mentions that -->[URL='https://forum.team-mediaportal.com/threads/using-hauppauge-ir-blaster-with-mp.49578/reply?quote=346326']here[/URL]<--. Does that help? mm [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
Installation, configuration support
Setting up Hauppauge Colossus IR blaster blues...
Contact us
RSS
Top
Bottom
