OTA Stations Program Guide Issue After Repack

pacmantech

New Member
Original poster
Feb 4, 2006
4
0
Several OTA stations in my market recently repacked. For example, our Fox affiliate now technically broadcasts on the same frequency as the PBS station.

Since the repack, the repacked stations now show incorrect data in my program guide on my Hopper 3.

So, I’m seeing programs twice for my PBS station in my grid. One under their correct call letters, and the other is under the call letters of the Fox affiliate.

Any known way to fix this?
 
The program guide in the DC area has been inaccurate for months now---ever since WJAL and WUSA started channel sharing.. It has shown 68.0 correctly for some time but a 68.1 it shows the programming of the CBS affiliate (WUSA)
 
  • Like
Reactions: navychop
Several OTA stations in my market recently repacked. For example, our Fox affiliate now technically broadcasts on the same frequency as the PBS station.

Since the repack, the repacked stations now show incorrect data in my program guide on my Hopper 3.

So, I’m seeing programs twice for my PBS station in my grid. One under their correct call letters, and the other is under the call letters of the Fox affiliate.

Any known way to fix this?

This is frustrating to say the very least. I am going to try and call WPMT tomorrow and see if I can talk to anybody that would care. Maybe they can work with Dish from their end to get it fixed. I would like to send them a picture so they have a better understanding of what we are seeing but I cannot find a good email address for their management.
 
  • Like
Reactions: Tampa8
Used to be dishquality@echostar.com for all audio/video complaints , but I stopped writing to them for new sub channel guide data since they said they won't support it any longer.
New sub channel guide data is one thing. There is no excuse for not fixing problems with the guide data that Dish had already been providing, though, especially if it is for a station that they actually carry as part of the local package, and provide correct guide data for on the satellite-delivered version of that channel.
 
The program guide in the DC area has been inaccurate for months now---ever since WJAL and WUSA started channel sharing.. It has shown 68.0 correctly for some time but a 68.1 it shows the programming of the CBS affiliate (WUSA)

Well today WDCW and WFDC started channel sharing and a similar thing happened 50-1 which should be the CW affiliate here shows program info for WFDC's main channel. I know report it to DISH>
 
On the subject of OTA guides, is there are difference on how the Vip 211K receives the OTA guide compared to a Hopper and dangle? The reason I ask, is we just had a change in a local translator that went from a regular OTA 12.1/12.2/12.3 to now 12.1/49.1 out of Portland OR. I get no guide for either, where I used to for 12.1 in the past. but a friend with a Hopper and dangle claims he gets the OTA guide for these two channels? Anyone know?
 
On the subject of OTA guides, is there are difference on how the Vip 211K receives the OTA guide compared to a Hopper and dangle? The reason I ask, is we just had a change in a local translator that went from a regular OTA 12.1/12.2/12.3 to now 12.1/49.1 out of Portland OR. I get no guide for either, where I used to for 12.1 in the past. but a friend with a Hopper and dangle claims he gets the OTA guide for these two channels? Anyone know?

Have you rescanned?
 
  • Like
Reactions: pattykay
Have you rescanned?
I agree. It sounds like the person who is still receiving the guide data did not re-scan. Here is a link to the thread with the guide data issue for my market: Dish OTA EPG issues Discussion
I did not re-scan, so I still have guide data for a now-useless 043-01 and 043-02. Of course, as I said later in that thread, I would not be able to actually receive those stations on their new frequency, even if I had re-scanned.
 
Have you rescanned?

Yes. IF I had not I would be unable to receive 50.1 at all but the guide data would likely be correct. I suspect that anyone with a HWS who receives OTA and lives in an area with channel sharing will experience the same issue.

BTW I tried to report it to DISH but got nowhere. I was told that 50.0 and 50.0 should be totally different. It was clear that the reps I spoke to had no knowledge of channel sharing and even when they took control of my receiver and said they could see my screen insisted I was faking what was being shown.
 
  • Like
Reactions: pattykay
Yes. IF I had not I would be unable to receive 50.1 at all but the guide data would likely be correct. I suspect that anyone with a HWS who receives OTA and lives in an area with channel sharing will experience the same issue.

BTW I tried to report it to DISH but got nowhere. I was told that 50.0 and 50.0 should be totally different. It was clear that the reps I spoke to had no knowledge of channel sharing and even when they took control of my receiver and said they could see my screen insisted I was faking what was being shown.
Did you try the thread I linked above in post number 11? DIRT members do occasionally respond there, and if enough people report the issue, it might get escalated to engineering. Speaking with a CSR about this is completely useless.
 
Did you try the thread I linked above in post number 11? DIRT members do occasionally respond there, and if enough people report the issue, it might get escalated to engineering. Speaking with a CSR about this is completely useless.


I will as soon as I can. thanks.
 
  • Like
Reactions: pattykay

Users Who Are Viewing This Thread (Total: 0, Members: 0, Guests: 0)

Who Read This Thread (Total Members: 1)

Top