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
HDHomeRun No Longer Detected By MP
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="airxdata" data-source="post: 177744" data-attributes="member: 27642"><p>The information was updated some time ago, yes, but I do have the proper entries in my XML file. I've double-checked them with Silicondust support staff and even ran graphedit to look at the filters for the capture card myself and verified that everything is golden. It's like it doesn't even really look for the card? I really don't know. I reached the limit of what I can do, other than bumping the logging up to the max, running the config app, and then sifting through the log for any clue as to where it might be going wrong. However, I don't think this is a problem that an end user can solve. It feels like something has changed in the code related to ATSC, QAM, or BDA tuners. Any chance a dev might want to take a gander at this and lend a hand?</p></blockquote><p></p>
[QUOTE="airxdata, post: 177744, member: 27642"] The information was updated some time ago, yes, but I do have the proper entries in my XML file. I've double-checked them with Silicondust support staff and even ran graphedit to look at the filters for the capture card myself and verified that everything is golden. It's like it doesn't even really look for the card? I really don't know. I reached the limit of what I can do, other than bumping the logging up to the max, running the config app, and then sifting through the log for any clue as to where it might be going wrong. However, I don't think this is a problem that an end user can solve. It feels like something has changed in the code related to ATSC, QAM, or BDA tuners. Any chance a dev might want to take a gander at this and lend a hand? [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
General Support
HDHomeRun No Longer Detected By MP
Contact us
RSS
Top
Bottom
