Mailing List Archive

New York PBS WNET channel 13 pid mess
Wow....The New York PBS channel, WNET apparently moved and changed
their PIDs or something. I first noticed this because an American
Masters show that was supposed to record was a a foreign language show
clearly from the wrong mult-cast.

I rescanned that transport (VHF frequency 13), which did change things
around. However how I have a mess where the listings are using the
wrong channel ids. Actually the listings are using the original
chanids that have now changed. I've tried fetching the channel line
up as well which doesn't seem to have fixed anything.

Here are some key fields from the channel table before the rescan etc:

select chanid, channum, sourceid, callsign, xmltvid from channel where
channum like '13%';;
+--------+---------+----------+----------+---------+
| chanid | channum | sourceid | callsign | xmltvid |
+--------+---------+----------+----------+---------+
| 1131 | 13.1 | 1 | WNET-HD | 26182 |
| 1132 | 13.2 | 1 | WNET-SD | 31780 |
| 1133 | 13.3 | 1 | WNET-13 | 44667 |
+--------+---------+----------+----------+---------+

Here's what they updated to after the rescan:

select chanid, channum, sourceid, callsign, xmltvid from channel where
channum like '13%'

+--------+---------+----------+----------+---------+
| chanid | channum | sourceid | callsign | xmltvid |
+--------+---------+----------+----------+---------+
| 1132 | 13.1 | 1 | WNET-HD | 31780 |
| 1133 | 13.2 | 1 | KIDS | 44667 |
| 1131 | 13.3 | 1 | V-Me | 26182 |
+--------+---------+----------+----------+---------+

You can see that they've switched things around in a really nasty
manner...no clue why.

When I tune to channum 13.1 in live tv now it does in fact tune to the
main WNET-HD multi-cast, which is good. However the guide data from
Schedules Direct is still getting mapped to the old chanids. For
scheduled program that should be on 13.1 still uses chanid 1131.

What does mythfilldatabase etc use to tie the listing data to the
channels? If I remember correctly, I thought it was the xmltvid If
that's the case, that would explain things, as they are still pointing
to the old channel table chanids.

As I mentioned, I tried fetching the channel line up and that changed
nothing. Are the xmltvid fields the problem? If so can I fix them,
even if it's manually in the database?

Quite the mess...

Thanks in advance.
Tom
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: New York PBS WNET channel 13 pid mess [ In reply to ]
On Sat, Jun 21, 2014 at 2:03 AM, Tom Dexter <digitalaudiorock@gmail.com> wrote:

Here's a little more on those channels before and after the rescan:

select chanid, channum, sourceid, callsign, xmltvid, atsc_major_chan,
atsc_minor_chan, freqid from channel where channum like '13%'
+--------+---------+----------+----------+---------+-----------------+-----------------+--------+
| chanid | channum | sourceid | callsign | xmltvid | atsc_major_chan |
atsc_minor_chan | freqid |
+--------+---------+----------+----------+---------+-----------------+-----------------+--------+
| 1131 | 13.1 | 1 | WNET-HD | 26182 | 13 |
1 | 13 |
| 1132 | 13.2 | 1 | WNET-SD | 31780 | 13 |
2 | 13 |
| 1133 | 13.3 | 1 | WNET-13 | 44667 | 13 |
3 | 13 |
+--------+---------+----------+----------+---------+-----------------+-----------------+--------+

select chanid, channum, sourceid, callsign, xmltvid, atsc_major_chan,
atsc_minor_chan, freqid from channel where channum like '13%'
+--------+---------+----------+----------+---------+-----------------+-----------------+--------+
| chanid | channum | sourceid | callsign | xmltvid | atsc_major_chan |
atsc_minor_chan | freqid |
+--------+---------+----------+----------+---------+-----------------+-----------------+--------+
| 1132 | 13.1 | 1 | WNET-HD | 31780 | 13 |
1 | 13 |
| 1133 | 13.2 | 1 | KIDS | 44667 | 13 |
2 | 13 |
| 1131 | 13.3 | 1 | V-Me | 26182 | 13 |
3 | 13 |
+--------+---------+----------+----------+---------+-----------------+-----------------+--------+

Now that I've thought about this a bit more, I'm tempted to try and
actaully juggle the chanids back to what they were (with the backend
stopped). I know that'll take a little jumping though hoops because
it's the primary key (changing things to temporary unused ids etc),
but it occurred to me that things like oldrecorded still have the
original ids...that is where 1131=13.1, and I don't want stuff
happening like re-runs recording etc. For now I have all rules for
this channel deleted anyway.

I'd like to understand exactly what happened there in any case. What
does the channel scan use to find an existing channel based on a
specific multi-plex within that transport? The freqid and mplexid etc
are all the same.

What an ugly fricking mess.

Tom
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: New York PBS WNET channel 13 pid mess [ In reply to ]
On 06/21/2014 02:03 AM, Tom Dexter wrote:
> What does mythfilldatabase etc use to tie the listing data to the
> channels? If I remember correctly, I thought it was the xmltvid If
> that's the case, that would explain things, as they are still pointing
> to the old channel table chanids.

Yes. Just edit the XMLTV ID as appropriate

>
> As I mentioned, I tried fetching the channel line up and that changed
> nothing. Are the xmltvid fields the problem? If so can I fix them,
> even if it's manually in the database?

in the mythtv-setup or MythWeb channel editor.

Mike
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: New York PBS WNET channel 13 pid mess [ In reply to ]
On 06/21/2014 02:29 AM, Tom Dexter wrote:
> On Sat, Jun 21, 2014 at 2:03 AM, Tom Dexter wrote:
>
> Here's a little more on those channels before and after the rescan:
>
> select chanid, channum, sourceid, callsign, xmltvid, atsc_major_chan,
> atsc_minor_chan, freqid from channel where channum like '13%'
> +--------+---------+----------+----------+---------+-----------------+-----------------+--------+
> | chanid | channum | sourceid | callsign | xmltvid | atsc_major_chan |
> atsc_minor_chan | freqid |
> +--------+---------+----------+----------+---------+-----------------+-----------------+--------+
> | 1131 | 13.1 | 1 | WNET-HD | 26182 | 13 |
> 1 | 13 |
> | 1132 | 13.2 | 1 | WNET-SD | 31780 | 13 |
> 2 | 13 |
> | 1133 | 13.3 | 1 | WNET-13 | 44667 | 13 |
> 3 | 13 |
> +--------+---------+----------+----------+---------+-----------------+-----------------+--------+
>
> select chanid, channum, sourceid, callsign, xmltvid, atsc_major_chan,
> atsc_minor_chan, freqid from channel where channum like '13%'
> +--------+---------+----------+----------+---------+-----------------+-----------------+--------+
> | chanid | channum | sourceid | callsign | xmltvid | atsc_major_chan |
> atsc_minor_chan | freqid |
> +--------+---------+----------+----------+---------+-----------------+-----------------+--------+
> | 1132 | 13.1 | 1 | WNET-HD | 31780 | 13 |
> 1 | 13 |
> | 1133 | 13.2 | 1 | KIDS | 44667 | 13 |
> 2 | 13 |
> | 1131 | 13.3 | 1 | V-Me | 26182 | 13 |
> 3 | 13 |
> +--------+---------+----------+----------+---------+-----------------+-----------------+--------+
>
> Now that I've thought about this a bit more, I'm tempted to try and
> actaully juggle the chanids back to what they were (with the backend
> stopped). I know that'll take a little jumping though hoops because
> it's the primary key (changing things to temporary unused ids etc),
> but it occurred to me that things like oldrecorded still have the
> original ids...that is where 1131=13.1, and I don't want stuff
> happening like re-runs recording etc. For now I have all rules for
> this channel deleted anyway.
>
> I'd like to understand exactly what happened there in any case. What
> does the channel scan use to find an existing channel based on a
> specific multi-plex within that transport? The freqid and mplexid etc
> are all the same.
>
> What an ugly fricking mess.

Do not change your channel ID's. They are MythTV-internal, irrelevant,
and (most-importantly) not-user-editable values.

Just fix your XMLTV ID's. In mythtv-setup channel editor it's the 2nd
page or so.

Oh, and rescanning channels and mythtv-setup (with or without
--do-channel-updates (which you should really never use) and/or
--only-update-channels) will never change XMLTV ID's. So, the /only/
way (and the designed way) to change XMLTV ID is to edit it manually in
mythtv-setup or MythWeb channel editor.

Mike
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org
Re: New York PBS WNET channel 13 pid mess [ In reply to ]
On Sat, Jun 21, 2014 at 7:19 AM, Michael T. Dean
<mtdean@thirdcontact.com> wrote:
> On 06/21/2014 02:29 AM, Tom Dexter wrote:


> Do not change your channel ID's. They are MythTV-internal, irrelevant, and
> (most-importantly) not-user-editable values.
>
> Just fix your XMLTV ID's. In mythtv-setup channel editor it's the 2nd page
> or so.
>
> Oh, and rescanning channels and mythtv-setup (with or without
> --do-channel-updates (which you should really never use) and/or
> --only-update-channels) will never change XMLTV ID's. So, the /only/ way
> (and the designed way) to change XMLTV ID is to edit it manually in
> mythtv-setup or MythWeb channel editor.
>
>
> Mike

Thanks Mike. I finally got everything right, but it wasn't easy and
now I understand why:

What the station did was this: The original serviceids for 13.1,
13.2, and 13.3 were 5, 3 and 4 respectively. Apparently the decided
to reorder ("fix") things so 13.1, 13.2, and 13.3 are now 3, 4, and 5
respectively.

This meant that the channel scan found the existing channels, and
reassigned things on what essentially were the wrong channels. This
then meant that the icons and xmltvid fields were all out of whack.
Ugly.

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