Mailing List Archive

On Sunday 19 February 2023 02:33:41 PM (-06:00), Ian Evans wrote:

> New to using xmltv with Schedules Direct.
>
> When I run mythfilldataase (and yes, as the mythtv user) I get about
> 40 of these for my OTA listings:
>
> 2023-02-19 15:21:31.439935 N Unknown xmltv channel identifier:
> I99248.json.schedulesdirect.org - Skipping channel.
>
> Here's the thing I used the channel editor in mythtv-setup to enter
> the xmltv ids from SD. I'm getting the correct guide info inserted
> into my guide.
>
> So where are these errors coming from?

mythfilldatabase has just called a method that did this (near the
beginning):

SELECT chanid FROM channel WHERE deleted IS NULL

AND sourceid = SomeID AND xmltvid = SomeXMLTVID;

And the chanid is empty. This is MFDB handling the data generated
by the grabber. I've 'turned' these IDs off in SQLite in the past.

They're harmless, but fixable.
--
Bill
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On Sun, Feb 19, 2023 at 8:35 PM Ian Evans <dheianevans@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
XMLTVIDs.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On Sun, Feb 19, 2023 at 3:59 PM Gary Buhrmaster
<gary.buhrmaster@gmail.com> wrote:
>
> On Sun, Feb 19, 2023 at 8:35 PM Ian Evans <dheianevans@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
> XMLTVIDs.

No translators in the area.

I'll stop noticing the notices. :-)
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On Sun, Feb 19, 2023 at 9:13 PM Ian Evans <dheianevans@gmail.com> wrote:

> No translators in the area.

Another possibility is if you are in one
of those "in between" locations, where
depending on which direction your
antenna is pointed, and if you have a
deep fringe enough antenna, you might
be able to receive broadcasts from
multiple markets, and Schedules Direct
includes both markets OTA channels[0]

If you share your specific lineup
name I might be able to take a look
at some point (no guarantees).


[0] Some people in parts of NJ may be able
to receive some of both of the NYC and PHL
stations. There are other examples, of
course, as the actual signals do not stop on
the FCC DMA designated boundaries.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On Sunday 19 February 2023 02:33:41 PM (-06:00), Ian Evans wrote:

> New to using xmltv with Schedules Direct.
>
> When I run mythfilldataase (and yes, as the mythtv user) I get about
> 40 of these for my OTA listings:
>
> 2023-02-19 15:21:31.439935 N Unknown xmltv channel identifier:
> I99248.json.schedulesdirect.org - Skipping channel.
>
> Here's the thing I used the channel editor in mythtv-setup to enter
> the xmltv ids from SD. I'm getting the correct guide info inserted
> into my guide.
>
> So where are these errors coming from?

Not sure my 1st reply made it to the list, but here's one way to
eliminate the message (or use the 'ignore them' method (which
I've used for months.)


...Unknown xmltv channel identifier: I125045.json.schedulesdirect.org -
Skipping channel.

$ sqlite3 -line SchedulesDirect.DB 'SELECT * FROM channels WHERE
station="125045"'
lineup = USA-OTA-90210
station = 125045
channum = 32.5
selected = 0
details = {"atscMajor":32,"atscMinor":5,"stationID":"125045","uhfVhf":24}

$ sqlite3 -line SchedulesDirect.DB 'UPDATE channels SET selected=0 WHERE
station="125045"'

To look at multiple stations:
$ sqlite3 -line SchedulesDirect.DB 'SELECT * FROM channels WHERE station IN
("124835","124741","125045")'

--
Bill
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On Sun, Feb 19, 2023 at 4:32 PM Gary Buhrmaster
<gary.buhrmaster@gmail.com> wrote:
>
> On Sun, Feb 19, 2023 at 9:13 PM Ian Evans <dheianevans@gmail.com> wrote:
>
> > No translators in the area.
>
> Another possibility is if you are in one
> of those "in between" locations, where
> depending on which direction your
> antenna is pointed, and if you have a
> deep fringe enough antenna, you might
> be able to receive broadcasts from
> multiple markets, and Schedules Direct
> includes both markets OTA channels[0]

I'm in Toronto, so we get channels from here and Buffalo. The lineup
on SD includes Rochester as well because if a) you're in Buffalo or b)
experiencing tropo bounce in Toronto, we may get them.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On Sun, Feb 19, 2023 at 6:16 PM Bill Meek <keemllib@gmail.com> wrote:
>
>
>
>
> On Sunday 19 February 2023 02:33:41 PM (-06:00), Ian Evans wrote:
>
> > New to using xmltv with Schedules Direct.
> >
> > When I run mythfilldataase (and yes, as the mythtv user) I get about
> > 40 of these for my OTA listings:
> >
> > 2023-02-19 15:21:31.439935 N Unknown xmltv channel identifier:
> > I99248.json.schedulesdirect.org - Skipping channel.
> >
> > Here's the thing I used the channel editor in mythtv-setup to enter
> > the xmltv ids from SD. I'm getting the correct guide info inserted
> > into my guide.
> >
> > So where are these errors coming from?
>
> Not sure my 1st reply made it to the list, but here's one way to
> eliminate the message (or use the 'ignore them' method (which
> I've used for months.)
>
>
> ...Unknown xmltv channel identifier: I125045.json.schedulesdirect.org -
> Skipping channel.
>
> $ sqlite3 -line SchedulesDirect.DB 'SELECT * FROM channels WHERE
> station="125045"'
> lineup = USA-OTA-90210
> station = 125045
> channum = 32.5
> selected = 0
> details = {"atscMajor":32,"atscMinor":5,"stationID":"125045","uhfVhf":24}
>
> $ sqlite3 -line SchedulesDirect.DB 'UPDATE channels SET selected=0 WHERE
> station="125045"'
>
> To look at multiple stations:
> $ sqlite3 -line SchedulesDirect.DB 'SELECT * FROM channels WHERE station IN
> ("124835","124741","125045")'

Thanks for the info!
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On Sun, Feb 19, 2023 at 9:13 PM Ian Evans <dheianevans@gmail.com> wrote:

>
> No translators in the area.
>

Actually, a couple of stations in the
greater Buffalo/Rochester market
use translators (for coverage)
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On Mon, Feb 20, 2023 at 12:24 AM Ian Evans <dheianevans@gmail.com> wrote:

> I'm in Toronto, so we get channels from here and Buffalo. The lineup
> on SD includes Rochester as well because if a) you're in Buffalo or b)
> experiencing tropo bounce in Toronto, we may get them.

And the CRTC would likely prefer that the
signals did stop at the FCC DMA limits
(last I knew there were a number of rules
and regulations intended to promote
Canada First content and restrict the stations
that some Canadian residents are officially
allowed to receive). Of course, Canadians
are too smart (and too nice), to try to
demand a change in the laws of Physics.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On Sun, Feb 19, 2023 at 9:23 PM Gary Buhrmaster
<gary.buhrmaster@gmail.com> wrote:
>
> On Mon, Feb 20, 2023 at 12:24 AM Ian Evans <dheianevans@gmail.com> wrote:
>
> > I'm in Toronto, so we get channels from here and Buffalo. The lineup
> > on SD includes Rochester as well because if a) you're in Buffalo or b)
> > experiencing tropo bounce in Toronto, we may get them.
>
> And the CRTC would likely prefer that the
> signals did stop at the FCC DMA limits
> (last I knew there were a number of rules
> and regulations intended to promote
> Canada First content and restrict the stations
> that some Canadian residents are officially
> allowed to receive). Of course, Canadians
> are too smart (and too nice), to try to
> demand a change in the laws of Physics.

lol. The joys of being a border city...all the cable people in Canada
complain they can't see the Super Bowl commercials, while the OTAers
chuckle. Also, we don't have subchannels so when two HD shows are
airing at the same time on a US and Canadian channel we can choose
between a few gigs less of disk space or a full bandwidth slightly
better looking recording.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On 19/02/2023 23:15, Bill Meek wrote:
>
>
>
> On Sunday 19 February 2023 02:33:41 PM (-06:00), Ian Evans wrote:
>
> > New to using xmltv with Schedules Direct.
> > > When I run mythfilldataase (and yes, as the mythtv user) I get about
> > 40 of these for my OTA listings:
> > > 2023-02-19 15:21:31.439935 N  Unknown xmltv channel identifier:
> > I99248.json.schedulesdirect.org - Skipping channel.
> > > Here's the thing I used the channel editor in mythtv-setup to enter
> > the xmltv ids from SD. I'm getting the correct guide info inserted
> > into my guide.
> > > So where are these errors coming from?
>
> Not sure my 1st reply made it to the list, but here's one way to
> eliminate the message (or use the 'ignore them' method (which
> I've used for months.)
>
>
> ...Unknown xmltv channel identifier: I125045.json.schedulesdirect.org - Skipping channel.
>
> $ sqlite3 -line SchedulesDirect.DB 'SELECT * FROM channels WHERE station="125045"'
>   lineup = USA-OTA-90210
>  station = 125045
>  channum = 32.5
> selected = 0
>  details = {"atscMajor":32,"atscMinor":5,"stationID":"125045","uhfVhf":24}
>
> $ sqlite3 -line SchedulesDirect.DB 'UPDATE channels SET selected=0 WHERE station="125045"'
>
> To look at multiple stations:
> $ sqlite3 -line SchedulesDirect.DB 'SELECT * FROM channels WHERE station IN
> ("124835","124741","125045")'
>
I notice that in your SELECT statement response that 'selected' is already 0, before the following
command sets it to zero. Is this a display artifact where 'selected' was actually null previously?
--

Mike Perkins


_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

On Monday 20 February 2023 04:03:48 AM (-06:00), Mike Perkins wrote:

> On 19/02/2023 23:15, Bill Meek wrote:
> > On Sunday 19 February 2023 02:33:41 PM (-06:00), Ian Evans wrote:
> > > New to using xmltv with Schedules Direct.
> > > > When I run mythfilldataase (and yes, as the mythtv user) I get
about
> > > 40 of these for my OTA listings:
> > > > 2023-02-19 15:21:31.439935 N Unknown xmltv channel identifier:
> > > I99248.json.schedulesdirect.org - Skipping channel.
> > > > Here's the thing I used the channel editor in mythtv-setup to
enter
> > > the xmltv ids from SD. I'm getting the correct guide info inserted
> > > into my guide.
> > > > So where are these errors coming from?
> > Not sure my 1st reply made it to the list, but here's one way to
> > eliminate the message (or use the 'ignore them' method (which
> > I've used for months.)
> > ...Unknown xmltv channel identifier: I125045.json.schedulesdirect.org
- Skipping channel.
> > $ sqlite3 -line SchedulesDirect.DB 'SELECT * FROM channels WHERE
station="125045"'
> > lineup = USA-OTA-90210
> > station = 125045
> > channum = 32.5
> > selected = 0
> > details =
{"atscMajor":32,"atscMinor":5,"stationID":"125045","uhfVhf":24}
> > $ sqlite3 -line SchedulesDirect.DB 'UPDATE channels SET selected=0
WHERE station="125045"'
> > To look at multiple stations:
> > $ sqlite3 -line SchedulesDirect.DB 'SELECT * FROM channels WHERE
station IN ("124835","124741","125045")'
> I notice that in your SELECT statement response that 'selected' is
already 0, before the following command sets it to zero. Is this a display
artifact where 'selected' was actually null previously?
It was 1 before, just a poor copy/paste choice.

--
Bill
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org