[mythtv-users] Schedules Direct JSON service changes 2022-05-20

Tom Dexter digitalaudiorock at gmail.com
Sun May 22 19:00:34 UTC 2022

On Sun, May 22, 2022 at 1:47 PM Gary Buhrmaster
<gary.buhrmaster at gmail.com> wrote:
> On Sun, May 22, 2022 at 5:27 PM Tom Dexter <digitalaudiorock at gmail.com> wrote:
> alue."
> >
> > Does anyone know if the numeric portion of that xmltvid is by some
> > chance the same number as the old numeric ID?
> They are (since the data comes from the same
> upstream source), but technically one should
> not depend upon it.
> Somewhere, a long time ago, someone posted
> a one time conversion script (not sure if email,
> or forum, or wiki) to convert the MythTV
> (non-RFC2838 compliant) xmltvids to the
> RFC2838 compliant form zz_sdjson_sqlite emits.
> And for those of a certain persuasion, one
> could modify the variable RFC2838_COMPLIANT
> near the top of the script to create non-compliant
> station IDs that are the bare integer, or run the
> output through a xslt conversion filter to do
> whatever you wish to the xml.

Thanks. Something else that concerns me a bit from the MythTV XMLTV
regarding the sqlite grabber is when it says this:

"Once you have updated all of the xmltvid's, run mythfilldatabase.
Your channel names and icons will be updated to match the values
supplied by schedules direct."

I know that the zz_sdjson grabber updates and downloads icons, but
when they say that "channel names" will be updated, do they mean the
callsign? I don't think the zz_sdjson grabber eer touched those and
I'm concerned as to the issues that might cause.


More information about the mythtv-users mailing list