home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Support
Electronic Program Guide
New Episode recording only
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="mm1352000" data-source="post: 1035933" data-attributes="member: 82144"><p>Ummmm... just a bit confused here as we seem to be talking about two different things.</p><p>Some people are talking about a "new" or "first airing" flag; other people are talking about episode numbers.</p><p></p><p>Let me clear the record.</p><p></p><p>Categorically: we do not have a column in our TV Server database to hold a "new" flag. Therefore, unless you're using a plugin that maintains its own database, adds columns to our database, or uses some other means to only schedule <strong>only </strong>new-by-your-definition programmes it is not possible to only record new programmes.</p><p></p><p>FYI, here is the definition of the relevant table so you can see what we do store:</p><p><a href="https://github.com/MediaPortal/MediaPortal-1/blob/master/TvEngine3/TVLibrary/TVDatabase/Program.cs#L37" target="_blank">https://github.com/MediaPortal/MediaPortal-1/blob/master/TvEngine3/TVLibrary/TVDatabase/Program.cs#L37</a></p><p></p><p>It is not a big issue to add a new column to the table. In fact that is probably the easiest part of adding support for such a feature.</p><p></p><p>TV Server EPG data comes from a variety of different sources (in-band, XMLTV, WebEPG, SchedulesDirect etc.). Each source would have to add support separately because the original data content and format is different, <strong>and</strong> the way the data is imported into TV Server varies.</p><p></p><p>Let's take the XMLTV format as an example because it is so popular.</p><p>Here is the XMLTV spec:</p><p><a href="http://xmltv.cvs.sourceforge.net/xmltv/xmltv/xmltv.dtd?view=markup" target="_blank">http://xmltv.cvs.sourceforge.net/xmltv/xmltv/xmltv.dtd?view=markup</a></p><p></p><p>Is there a "new" flag?</p><p>Well, yes there is (line 490)... but on closer reading of the description you'll see that it doesn't mean "new" in the sense that is discussed here. It means the first episode of the first season of a brand new show.</p><p>Okay, is there an alternative?</p><p>Maybe "premiere" (line 453)? The problem with premiere is that it is ambiguous. As the description says: "different channels have different meanings for this word". It might be equivalent to what you want... or it might not... and that might vary from channel to channel or data source to data source.</p><p>What about "previously-shown" (line 449)?</p><p>Well, this is not really a new flag - it is really the inverse. If every programme that was <strong>not</strong> "new" were marked with this attribute then by definition it still doesn't mean that the unmarked shows are "new". As the description says: "the absence of this element does not say for certain that the programme is brand new".</p><p></p><p>My take on the above is that there is no universally correct and unambiguous way to encode the "new" attribute in an XMLTV file. Therefore, any implementation will be imperfect and subject to per-channel and per-source problems.</p><p></p><p>This is only one example of the problems one would encounter if attempting to implement support for this feature. I hope it helps to illustrate that it is not as easy as you might think.</p><p></p><p>@[USER=123421]Pat Clark[/USER]</p><p>In relation to your comments about episode number...</p><p>Here is the XMLTV plugin code that reads the episode number details:</p><p><a href="https://github.com/MediaPortal/MediaPortal-1/blob/master/TvEngine3/TVLibrary/Plugins/XmlTvImport/XMLTVImport.cs#L618" target="_blank">https://github.com/MediaPortal/MediaPortal-1/blob/master/TvEngine3/TVLibrary/Plugins/XmlTvImport/XMLTVImport.cs#L618</a></p><p></p><p>Succinctly, the points I want to make are:</p><p>1. Of the three episode number attributes in your example, the "onscreen" system is the only system that the TV Server XMLTV plugin supports. The other two episode numbers are ignored.</p><p>2. We support "onscreen" and "xmltv_ns" systems because these are the only two systems specified in the XMLTV specification (refer to the above link). We also try to parse episode numbers where the system is not specified, but this is obviously not standard.</p><p>3. Onscreen is the most ambiguous of the two supported systems (again, read the XMLTV spec). It is basically as good as no standard. We simply take the content of the episode-num tag and try to convert it into a number. If that doesn't work, the data is thrown away.</p><p>4. If onscreen or xmltv_ns episode number details are detected but thrown away, you'll see this logged in your TVService log file ("XMLTVImport::CorrectEpisodeNum, could not parse...").</p><p></p><p>The example above should import fine. From the code, I'd expect it to be interpreted as season 0 episode 118. If you've already recorded season 0 episode 118, the file still exists where TV Server thinks it should be, and you've configured TV Server to not record repeats... then I'd expect TV Server to not record that programme.</p><p></p><p>mm</p></blockquote><p></p>
[QUOTE="mm1352000, post: 1035933, member: 82144"] Ummmm... just a bit confused here as we seem to be talking about two different things. Some people are talking about a "new" or "first airing" flag; other people are talking about episode numbers. Let me clear the record. Categorically: we do not have a column in our TV Server database to hold a "new" flag. Therefore, unless you're using a plugin that maintains its own database, adds columns to our database, or uses some other means to only schedule [B]only [/B]new-by-your-definition programmes it is not possible to only record new programmes. FYI, here is the definition of the relevant table so you can see what we do store: [url]https://github.com/MediaPortal/MediaPortal-1/blob/master/TvEngine3/TVLibrary/TVDatabase/Program.cs#L37[/url] It is not a big issue to add a new column to the table. In fact that is probably the easiest part of adding support for such a feature. TV Server EPG data comes from a variety of different sources (in-band, XMLTV, WebEPG, SchedulesDirect etc.). Each source would have to add support separately because the original data content and format is different, [B]and[/B] the way the data is imported into TV Server varies. Let's take the XMLTV format as an example because it is so popular. Here is the XMLTV spec: [url]http://xmltv.cvs.sourceforge.net/xmltv/xmltv/xmltv.dtd?view=markup[/url] Is there a "new" flag? Well, yes there is (line 490)... but on closer reading of the description you'll see that it doesn't mean "new" in the sense that is discussed here. It means the first episode of the first season of a brand new show. Okay, is there an alternative? Maybe "premiere" (line 453)? The problem with premiere is that it is ambiguous. As the description says: "different channels have different meanings for this word". It might be equivalent to what you want... or it might not... and that might vary from channel to channel or data source to data source. What about "previously-shown" (line 449)? Well, this is not really a new flag - it is really the inverse. If every programme that was [B]not[/B] "new" were marked with this attribute then by definition it still doesn't mean that the unmarked shows are "new". As the description says: "the absence of this element does not say for certain that the programme is brand new". My take on the above is that there is no universally correct and unambiguous way to encode the "new" attribute in an XMLTV file. Therefore, any implementation will be imperfect and subject to per-channel and per-source problems. This is only one example of the problems one would encounter if attempting to implement support for this feature. I hope it helps to illustrate that it is not as easy as you might think. @[USER=123421]Pat Clark[/USER] In relation to your comments about episode number... Here is the XMLTV plugin code that reads the episode number details: [url]https://github.com/MediaPortal/MediaPortal-1/blob/master/TvEngine3/TVLibrary/Plugins/XmlTvImport/XMLTVImport.cs#L618[/url] Succinctly, the points I want to make are: 1. Of the three episode number attributes in your example, the "onscreen" system is the only system that the TV Server XMLTV plugin supports. The other two episode numbers are ignored. 2. We support "onscreen" and "xmltv_ns" systems because these are the only two systems specified in the XMLTV specification (refer to the above link). We also try to parse episode numbers where the system is not specified, but this is obviously not standard. 3. Onscreen is the most ambiguous of the two supported systems (again, read the XMLTV spec). It is basically as good as no standard. We simply take the content of the episode-num tag and try to convert it into a number. If that doesn't work, the data is thrown away. 4. If onscreen or xmltv_ns episode number details are detected but thrown away, you'll see this logged in your TVService log file ("XMLTVImport::CorrectEpisodeNum, could not parse..."). The example above should import fine. From the code, I'd expect it to be interpreted as season 0 episode 118. If you've already recorded season 0 episode 118, the file still exists where TV Server thinks it should be, and you've configured TV Server to not record repeats... then I'd expect TV Server to not record that programme. mm [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
Electronic Program Guide
New Episode recording only
Contact us
RSS
Top
Bottom