Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 998937" data-attributes="member: 82144">Okay, so obviously MP has no relation to EPG Collector, and neither EPGC or MP have any control over what is in the broadcast stream.If EPGC is creating tags that way and you don't think they're reasonable then you should take it up with Steve.<a href="http://sourceforge.net/p/epgcollector/discussion/1125945" target="_blank">http://sourceforge.net/p/epgcollector/discussion/1125945</a>&nbsp;Having said that, the first number is the series number, second number is the episode number and third number is the episode part number. I wouldn't have thought episode parts would be all that common?Maybe it would help to read the XMLTV spec (this comes out of the dtd file, which can be opened in any text editor):[collapse]&lt;!-- Episode numberNot the title of the episode, its number or ID.&nbsp; There are severalways of numbering episodes, so the 'system' attribute lets you specifywhich you mean.There are two predefined numbering systems, 'xmltv_ns' and'onscreen'.xmltv_ns: This is intended to be a general way to number episodes andparts of multi-part episodes.&nbsp; It is three numbers separated by dots,the first is the series or season, the second the episode numberwithin that series, and the third the part number, if the programme ispart of a two-parter.&nbsp; All these numbers are indexed from zero, andthey can be given in the form 'X/Y' to show series X out of Y seriesmade, or episode X out of Y episodes in this series, or part X of aY-part episode.&nbsp; If any of these aren't known they can be omitted.You can put spaces whereever you like to make things easier to read.(NB 'part number' is not used when a whole programme is split in twofor purely scheduling reasons; it's intended for cases where therereally is a 'Part One' and 'Part Two'.&nbsp; The format doesn't currentlyhave a way to represent a whole programme that happens to be splitacross two or more timeslots.)Some examples will make things clearer.&nbsp; The first episode of thesecond series is '1.0.0/1' .&nbsp; If it were a two-part episode, then thefirst half would be '1.0.0/2' and the second half '1.0.1/2'.&nbsp; If youknow that an episode is from the first season, but you don't knowwhich episode it is or whether it is part of a multiparter, you couldgive the episode-num as '0..'.&nbsp; Here the second and third numbers havebeen omitted.&nbsp; If you know that this is the first part of a three-partepisode, which is the last episode of the first series of thirteen,its number would be '0 . 12/13 . 0/3'.&nbsp; The series number is just '0'because you don't know how many series there are in total - perhapsthe show is still being made!The other predefined system, onscreen, is to simply copy what theprogramme makers write in the credits - 'Episode #FFEE' wouldtranslate to '#FFEE'.You are encouraged to use one of these two if possible; if xmltv_ns isnot general enough for your needs, let me know.&nbsp; But if you want, youcan use your own system and give the 'system' attribute as a URLdescribing the system you use.--&gt;[/collapse]&nbsp;Trust me, it is reading all three numbers (if present):[code]&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; if (nodeEpisodeNumSystem == &quot;xmltv_ns&quot;)&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; serEpNum = ConvertHTMLToAnsi(nodeEpisodeNum.Replace(&quot; &quot;, &quot;&quot;));&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; int dot1 = serEpNum.IndexOf(&quot;.&quot;, 0);&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; int dot2 = serEpNum.IndexOf(&quot;.&quot;, dot1 + 1);&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; seriesNum = serEpNum.Substring(0, dot1);&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; episodeNum = serEpNum.Substring(dot1 + 1, dot2 - (dot1 + 1));&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; episodePart = serEpNum.Substring(dot2 + 1, serEpNum.Length - (dot2 + 1));&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; //xmltv_ns is theorically zero-based number will be increased by one&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; seriesNum = CorrectEpisodeNum(seriesNum, 1);&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; episodeNum = CorrectEpisodeNum(episodeNum, 1);&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; episodePart = CorrectEpisodeNum(episodePart, 1);&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; }&nbsp;[/code]&nbsp;The entries you're seeing in the logs are effectively errors saying the numbers are too big to be held in a 4 byte signed integer.&nbsp;&nbsp;Hopefully the above info is useful to you. Short of checking the database nothing that you've said here confirms the XMLTV plugin is not storing the data (when possible). I get the feeling there is a disconnect between your expectations and what is actually happening, and your expectations still aren't entirely clear to me. If you're used to using DJBlu's or miroslav22's custom builds for Sky EPG then it is entirely possible that things will be very different to what you're used to. $ky episode numbers may be intended to be interpreted in ways that the EPG Collector is not aware of...</blockquote>

[QUOTE="mm1352000, post: 998937, member: 82144"] Okay, so obviously MP has no relation to EPG Collector, and neither EPGC or MP have any control over what is in the broadcast stream. If EPGC is creating tags that way and you don't think they're reasonable then you should take it up with Steve. [url]http://sourceforge.net/p/epgcollector/discussion/1125945[/url] Having said that, the first number is the series number, second number is the episode number and third number is the episode part number. I wouldn't have thought episode parts would be all that common? Maybe it would help to read the XMLTV spec (this comes out of the dtd file, which can be opened in any text editor): [collapse][/collapse] Trust me, it is reading all three numbers (if present): [code] if (nodeEpisodeNumSystem == "xmltv_ns") { serEpNum = ConvertHTMLToAnsi(nodeEpisodeNum.Replace(" ", "")); int dot1 = serEpNum.IndexOf(".", 0); int dot2 = serEpNum.IndexOf(".", dot1 + 1); seriesNum = serEpNum.Substring(0, dot1); episodeNum = serEpNum.Substring(dot1 + 1, dot2 - (dot1 + 1)); episodePart = serEpNum.Substring(dot2 + 1, serEpNum.Length - (dot2 + 1)); //xmltv_ns is theorically zero-based number will be increased by one seriesNum = CorrectEpisodeNum(seriesNum, 1); episodeNum = CorrectEpisodeNum(episodeNum, 1); episodePart = CorrectEpisodeNum(episodePart, 1); } [/code] The entries you're seeing in the logs are effectively errors saying the numbers are too big to be held in a 4 byte signed integer. Hopefully the above info is useful to you. Short of checking the database nothing that you've said here confirms the XMLTV plugin is not storing the data (when possible). I get the feeling there is a disconnect between your expectations and what is actually happening, and your expectations still aren't entirely clear to me. If you're used to using DJBlu's or miroslav22's custom builds for Sky EPG then it is entirely possible that things will be very different to what you're used to. $ky episode numbers may be intended to be interpreted in ways that the EPG Collector is not aware of... [/QUOTE]

Verification