Reply to thread

Message

<blockquote data-quote="jacc1234" data-source="post: 424400" data-attributes="member: 72209">So far the new build seems to be working fine. The issue I described is not exactly whats going on. I have a mix of standard and HD channels and I cant get it to recognize some of the HD versions. I solved most of these conflicts by adding the OTA list along with the basic cable but there are still some issues. TBS is a good example. I tried to uncheck the standard version and hoped if the names were identical schedules direct would just associate the HD channel with its listing but this did not happen. I followed a guide that was posted somewhere in this thread. It said to add all of the standard def channels then run schedules direct. After it associated the channels with its listings I then added the HD channels and renamed them to match the standard def versions. I was under the assumption that they would then be recognized. This did not happen at all. Any help would be appreciated.</blockquote>

[QUOTE="jacc1234, post: 424400, member: 72209"] So far the new build seems to be working fine. The issue I described is not exactly whats going on. I have a mix of standard and HD channels and I cant get it to recognize some of the HD versions. I solved most of these conflicts by adding the OTA list along with the basic cable but there are still some issues. TBS is a good example. I tried to uncheck the standard version and hoped if the names were identical schedules direct would just associate the HD channel with its listing but this did not happen. I followed a guide that was posted somewhere in this thread. It said to add all of the standard def channels then run schedules direct. After it associated the channels with its listings I then added the HD channels and renamed them to match the standard def versions. I was under the assumption that they would then be recognized. This did not happen at all. Any help would be appreciated. [/QUOTE]

Verification