lexvictory at yahoo
May 22, 2012, 6:24 PM
Post #5 of 8
--- On Wed, 23/5/12, Michael T. Dean <mtdean [at] thirdcontact> wrote:
Re: Is SeriesID field of program used for anything?
[In reply to]
> From: Michael T. Dean <mtdean [at] thirdcontact>
> Subject: Re: [mythtv-users] Is SeriesID field of program used for anything?
> To: "Discussion about MythTV" <mythtv-users [at] mythtv>
> Received: Wednesday, 23 May, 2012, 1:32 AM
> On 05/22/2012 08:16 AM, Xander
> Victory wrote:
> >> The seriesid is automatically generated using an
> ELF hash of the title when importing XMLTV data. It
> must be a unique value for a given title, or--if
> possible--unique for a given series.
> > This is my current situation - the guide data
> (Australian Freeview) supplies a series CRID (much the same
> as the UK), my grabber sends this to mythtv in the xml,
> mythfilfilldatabase uses it with the patch i made for it.
> (I'm still on 0.24 btw)
> >> Note that it's generally not used for scheduling
> > This is mainly what I wanted to know; does ANYTHING
> else use the value?
> >> Note that seriesid is not used for duplicate
> matching. Instead programid is used. See
> > Sorry if I confused, I know that programid is used for
> > Currently, if NO season/episode info is available (and
> it's not a movie), my grabber outputs <episode-num
> - thus removing to issue of them having none generated by
> > Conversely if there IS season/episode info that it
> finds and outputs, the dd_progid element is left out,
> leaving mythfilldatabase to generate the hashed one.
> > The patch I referenced enables mythtv to extend
> recording time based on the current/following info in EIT.
> > It works well enough as is, however it must fall back
> to title (without subtitle) matching for episodes with
> season/episode info (and therefore a mythfilldatabase
> generated programid). This means that e.g. with double
> episodes of The Simpsons, the first episode's recording
> keeps recording until the 2nd ends; THIS is what I want to
> > I want to know if it is safe for me to change the
> seriesID that programs get from
> "crid://network/networks_series_id" to
> "crid://network/networks_series_id/networks_program_id" so
> that the EIT current/following patch always has both IDs to
> work with.
> OK, it sounds like you need the more-detailed answer than
> the "generally not used" I mentioned before. With
> 0.25+, seriesid may be used in non-custom recording rules,
> as explained at https://github.com/MythTV/mythtv/commit/02f646ac
> . (And thanks to David Engel for looking up the
> So, changing seriesid to have different values for different
> showings of the same series would actually break things for
> some users.
Only had a chance to quickly look at the commit this morning, and don't completely understand what breaks with series IDs - also it may end up partially broken anyway in the current situation; the same series is sometimes supplied a different seriesid by the networks (seemingly for repeats, different seasons, etc).
If there are different SeriesIDs, will it break recording rules other than the "this series" filter/rule?
> Can you use programid directly, rather than embedding it in
> the seriesid, to tell the 2 episodes apart?
I had hoped to be able to do this based on "The scheduler now falls back to
title/subtitle/description checking if two programs have non-empty
programids from different authorities." in the commit message.
However from what sense I can make of the code, this appears to strip the authority and match on the last part of the ID?
Or did I miss something? - the SQL is a bit hard to decipher right now at work
Perhaps I should be appending a hashed ProgramID to the one I output?
Matching on subtitle and description would possibly also lead to false negatives anyway - the networks here like to have subtitles that differ in spelling etc. There would need to be matching on the season/episode info too. (it is also feasible that there would be programs with season/episode info but no subtitle)
With some of the changes needing to be made I was thinking of possibly making a fork/branch on github when I make it public to contain the needed Aussie specific patches (EIT cur/fol, seriesid in xmltv, etc), at least whilst they disrupt other regions, so making changes to account for the grabber's quirks might be feasible...
mythtv-users mailing list
mythtv-users [at] mythtv