[mythtv] Status of Schedules Direct SD-JSON grabbers

Nick Morrott knowledgejunkie at gmail.com
Thu Jul 28 17:22:02 UTC 2016

On 28 July 2016 at 17:10, Peter Bennett <pgbennett at comcast.net> wrote:
> On 07/27/2016 08:25 PM, Gary Buhrmaster wrote:
>> One Observation: If I do channel selection on a new setup, the channels
>> are presented in random order without channel numbers. If I do --days 0
>> after initializing the database, the channels are presented in channel
>> number order with channel numbers, names and call signs, which is a lot
>> better.
> I will have to think a bit.  Stations have no specific order in
> xmltv, but humans seem to have this habit of wanting the
> derived channel number to be in order (but, note, it is not
> a simple sort order, but a "channel" order (as a channel,
> channel 2.4 is before 2.10, but not as a number sort,
> as 2.10 is lower than 2.4), and not as a character sort
> where you get into issues where channels such as
> 1 2 3 10 11 20 turn into 1 10 11 2 20 3, which is not what
> you want either).  Adding in a custom parse and sort will
> require some thought, and whether it can even be done
> efficiently in the current code constructs is unknown.
> It seems unnecessary to make any change. As I mentioned above it already
> appears to sort in channel sequence if you do a dummy data retrieval first
> (tv_grab_na_sd --days 0).
> More useful would be a better way of channel selection, instead of the
> current method where the user has to go through all 500 channels answering
> yes, no or default if the user needs to change anything.
> I think the other grabbers also use this method of channel selection, we
> should really have a nice method of selection that works for all grabbers.

I added the xmltv-lineups.xsd and working lineup support to XMLTV 4
years ago. The uk_rt and uk_atlas grabbers both used it until the
cessation of the RT data service and changes to Atlas terms,

It is up to each grabber (or upstream source) to determine *what* to
include in each lineup it presents to the user; *how* to present the
data is already there.

If the current xsd is not flexible enough for current needs, it can be
enhanced (let's discuss on xmltv-dev).


More information about the mythtv-dev mailing list