[mythtv-users] HDHomeRun Channel Scan Issue
ryanb at packetpub.net
Tue Sep 2 22:11:52 UTC 2008
On Mon, September 1, 2008 2:24 pm, greg wrote:
> Ryan Belcher wrote:
>> Hi All,
>> I've seen lots of Google results regarding channel scanning issues with
>> the HDHR and MythTv. I recently got a HDHR and I'm running into the
>> problem full force when connected to my cable provider (Charter Atlanta
>> -- Gwinnett county). I've tried increasing the scan timeouts (up to 45
>> seconds) and there's only one channel that gets the right
>> identification, on and off, out of about 47 channels it detects as being
>> non-encrypted. Otherwise, it marks the channels as "91#[stream number]"
>> (ex. 91#33). These channels start at 91#4 and go up to 91#51
>> The HDHR software does detect the channel info properly when used
>> The two most prevalent workarounds I've seen are increasing the scan
>> timeouts (seemingly ineffective for me), and scripting a DB fix with the
>> correct info.
>> I'm using the most recent SVN trunk 18240.
>> Does anyone have a fairly robust way of getting this to work right?
>> I've got no problem trying to tweak the DB, but I'm at a loss as to how
>> one goes about getting the right channel frequency, and ID information
>> collected and synchronized to fix the database by hand.
>> Thanks all!
>> mythtv-users mailing list
>> mythtv-users at mythtv.org
> If you need the freq id you can get them from Schedules Direct, if you
> are a subscriber... Here is an example of mine....You find this info
> under Report...
> 1806 34968 WRGBDT WRGBDT (WRGB-DT)
> 1808 45777 WXXADT WXXADT (WXXA-DT)
> 1810 32470 WTENDT WTENDT (WTEN-DT)
> 1811 32464 WMHTDT WMHTDT (WMHT-DT)
> 1813 36085 WNYTDT WNYTDT (WNYT-DT)
> 1815 34986 WCWNDT WCWNDT (WCWN
> mythtv-users mailing list
> mythtv-users at mythtv.org
Hmm... I thought that was the actual problem though, the information that
MythTv collects from the HDHR stream versus what SD has in their database
being different or non-matching. I could be way off here because my
memory is a bit fuzzy and I'm not @home, but I thought that was the
general problem as a whole...
More information about the mythtv-users