[mythtv-users] tv_grab_zz_sdjson_sqlite - Unknown xmltv channel identifier

Ian Evans dheianevans at gmail.com
Sun Feb 19 21:11:48 UTC 2023

On Sun, Feb 19, 2023 at 3:59 PM Gary Buhrmaster
<gary.buhrmaster at gmail.com> wrote:
> On Sun, Feb 19, 2023 at 8:35 PM Ian Evans <dheianevans at gmail.com> wrote:
> > So where are these errors coming from?
> They are from mythfilldatabase, but they are
> notices, and not errors.
> In the case of OTA, do you have translators in
> your area?  For better or worse[0], there can
> be (and often are for at least a subset of the
> channels) different XMLTVIDs for each
> translator.  So, depending on your specific
> location, you might get channel 2.1 from
> one tower, or channel 2.1 from the other
> tower, and they have different XMLTVIDs,
> so the Schedules Direct data provides both
> schedules (and, if you dig deeper, each
> translator has a different FCC callsign, and
> typically different name).  However, even
> though they have different XMLTVIDs, the
> actual schedule is the same.
> The easiest solution is just stop watching
> for notices.
> [0] I have previously asked that the upstream
> use the same XMLTVID for all translators
> (or none, rather than being miss or hit), but
> the upstream was convinced that there was
> no reason to change.  FWIW, they do the
> same thing for (some) cable channels, where
> the SD version and the HD version of the
> channel may (or may not) have different

No translators in the area.

I'll stop noticing the notices. :-)

More information about the mythtv-users mailing list