Suddenly lost channel mapping

Channels been working great for long time. Now in the past couple of months it's wrecked a couple of recordings where it has recorded from the wrong channel. I've found the problem but don't know what is causing it.

My local fox station (1017) has a DT2 station on (1186) that is the CW. For some reason the guide mapping is wrong where 1186 and 1017 are showing the same content. So the dvr has chosen to record from 1186 when it should record from 1017. I've tried rescanning my primes, reloading the guide data, resyncing the guide, and manually mapping. So far nothing has worked. The guide is still showing the same content between the two and my scheduled recordings are showing 1186 and 1017 as "equivalent"

when I try to do manual mapping channel I type in 1186 which is my CW station and the only option it gives me is FOX, which is 1017.

Have no idea what is going on.

Type the callsign of the correct station

I tried. I've attached a couple of screenshots showing the issue.


The first one shows the channel 1186 (WZTVDT2) is mapped to tuner WZTVTV (which is wrong). In the second you see that trying to type WZTVDT2, which is the correct call sign, shows that 1186 is mapped to WZTVDT (which is totally wrong). 1186 is the CW (WZTVDT2) but it's mapped wrong interrnally.

select 236 CW WZTVDT2 from the list?

you see that WZTVDT2 is connected to 236 (which is the SD version of the channel)

I did that. not optimal as that is the SD version of the channel. It seemed to "fix" the scheduled recordings as my Fox recordings do now appear to be using 1017 but clearly this thing is jacked up. the guide data should have that 1186 is the CW but it doesn't.

You can check what it shows on zap2it.com and use the Contact link at the bottom of the page to report problems.

The best solution on the DVR is what you just did, map the channel to the correct logo/guide data

yup. that's the issue. zap2it has wrong data. it is showing the same guide data for 1186 that appears on 1017 which is incorrect. Sorry for assuming there is a problem with the dvr. Problem reported.

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.