XMLTV Schedules Direct JSON (TheTVDB Metadata support)

[sub]

One thing which Xmltv tv handles well is having both the cryptic name for the channel which you're currently using in the drop down list along with a human readable one. You aren't currently - source of the manual mapping torture.

Can you post a screenshot example? I'm not in the UK, and not using Schedules Direct, so there is a bit of guess work involved when I'm trying to understand what a user is seeing.

[sub]

If it's the Schedules Direct call signs that are confusing. I can definitely look to show the full name where they're available.

[mvallevand]

In don't know why Tiny Pop is a problem but you it helps to be mapping with the channel list beside you. It was much worse in v4 with the tiny list box the web browser simplifies things.

If there is a name show it when it is not the same as the callsign.

Martin

[MrGrymReaper]

Can I PM you an Xmltv guide with the human readable names for my region and Schedules Direct Call signs. Though some are missing do appear and disappear at times.

[sub]

I'm happy to take a look at the file and try to make it smoother. I'd probably need both the npvr.db3 and xmltv file.

Is there a specific reason you're not wanting to use the built in json? It should get all the same data as the xmltv, but without the extra steps of having to deal with xmltv grabbers etc.

[MrGrymReaper]

When the channel information changes such as channel names (which occurred on Freeview UK network). In this case from CBS Drama to CBS Justice and then back again. During this time it was necessary to manually map the channel. Along with Schedules Direct JSON not getting updated line up information during this period really creating problems.

If you had released the v5 beta release during this time your short hand callsigns of SD unconverted would have added a lot of complexity to the mapping. Auto mapping wouldn't have worked. Until the line up was updated by Schedules Direct.

[sub]

When you're using the built in Schedules Direct JSON support it doesn't use channel names etc for the underlying mapping, so it's protected from channel name changes in the stream or at the Schedules Direct end. It instead using channel identifiers (like "703133"). It only uses the names at auto mapping time.

Sure the automapping might not work at some time because the channel names don't match, but once you're mapped you're good to go, and don't need to worry about channel name changes etc.

[sub]

If someone wants to supply a npvr.db3 with UK freeview channels scanned in, I'll take a look at the schedules direct mappings, to see if there is a better type of channel name available for the UK, so this automapping happens as smoothly as possible.

[MrGrymReaper]

Also in regards to integration with Schedules Direct may I suggest also have the ability to also perform other line up management functions. So that when users use the integration they can manage their lineup in v5.

[sub]

Also in regards to integration with Schedules Direct may I suggest also have the ability to also perform other line up management functions. So that when users use the integration they can manage their lineup in v5.

You can already do that. In that screen shot above, the 'source' dropdown has a 'add schedules direct lineup' if you need to add another lineup. You can also go to the Settings->Channel page, hit 'Advanced Tools' -> 'EPG Sources' to see the list of your Schedules Direct lineups, and delete a lineup.

In the near future I'm intending to add a new Settings->Guide page, which makes it easier to find.