[mythtv-users] [US] Switching from built-in schedules direct to the XMLTV-JSON schedules direct?

[David Engel]

On Thu, May 18, 2017 at 02:56:50PM +0000, Gary Buhrmaster wrote:
> On Thu, May 18, 2017 at 2:54 AM, Jason Zarin <jason at zarin.org> wrote:
> 
> > Should I switch to the XMLTV grabber to use the JSON feed? Are there any
> > advantages to the JSON feed other than having 20 days vs. 14 days of data?
> 
> FD 0: I am biased
> FD 1: I run using (one of) the XMLTV JSON grabbers
>           and I prefer it.
> FD 2: I am very biased

I think you're biased! :)

> [...]
> A disadvantage is that the xmltv load in mythfilldatabase is
> not memory efficient, which can result in the need for the
> system to either have much more memory, or performance
> will turn to crap (swapping) for those with large channel
> lineups (typical with cable systems).  There is a mitigation
> for that, but it requires the latest MythTV fixes, and it requires
> one to configure filling with the appropriate arguments.
> 
> The latest upstream upstream (not yet released) versions
> of at least one of the JSON grabbers also requires the
> latest MythTV fixes for proper season number calculation.
> 
> The latest upstream upstream (not yet released) version
> of at least one of the XMLTV JSON grabbers has improved
> data accuracy by merging series with episode information.
> 
> There was at least one feature that has not been cherrypicked
> into 0.28 (any) from v29, which involves genres.

Which change is that and why hasn't it been backported yet?

> [...]
> MythTV allows one to create quite complex recording rules.
> Because the data may be slightly different, those rules may
> need to be altered.  In particular, "this channel" or "this series"
> are especially problematic ("this channel" uses the internal
> chanid, which will be changing, and "this series" is influenced
> by a seriesid that may be different from the datadirect and
> the XMLTV JSON calculations (or they may be the same)).

How is "this channel" affected?  It uses channel.callsign not chanid
unless someone else changed it and I didn't notice.

David
-- 
David Engel
david at istwok.net