Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 1121480" data-attributes="member: 82144">Ahhh, I see - okay.Well the issue there is actually probably the design of EPG grabber. Especially the code in TsWriter.First, the grabber only returns data when it thinks it has received all data or timeout is reached. This is probably the single biggest cause of the difference you see between MP and [for example] DVBViewer.Also, the way the grabber detects when the EPG is complete currently is to wait until no new data - detected by CRC comparisons - is seen for at least 60 seconds (hard-coded!!!). I have completely rewritten [most - not quite finished] the EIT parser in TsWriter to use section_number, last_section_number, last_table_id etc. to try to improve the completion detection. However it is difficult because those fields are per-service, and there doesn't seem to be an easy way to know which services actually have EPG. In other words, completion doesn't seem to be deterministic.Having said all that, the only reason I can think of that you could experience this in the first place is if your provider only broadcasts EPG for a few hours, and your PC sleeps for a few hours without a chance to update the data. IMO that isn't (or shouldn't be) a common situation, because [good] providers usually like to broadcast ~7 days of data.So, I wonder whether your grabbing is configured correctly (ie. to get the &quot;long range&quot; guide data) and/or whether your short timeout is actually preventing you from getting the &quot;long range&quot; data that would solve the problem.Hope that makes sense? <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /></blockquote>

[QUOTE="mm1352000, post: 1121480, member: 82144"] Ahhh, I see - okay. Well the issue there is actually probably the design of EPG grabber. Especially the code in TsWriter. First, the grabber only returns data when it thinks it has received all data or timeout is reached. This is probably the single biggest cause of the difference you see between MP and [for example] DVBViewer. Also, the way the grabber detects when the EPG is complete currently is to wait until no new data - detected by CRC comparisons - is seen for at least 60 seconds (hard-coded!!!). I have completely rewritten [most - not quite finished] the EIT parser in TsWriter to use section_number, last_section_number, last_table_id etc. to try to improve the completion detection. However it is difficult because those fields are per-service, and there doesn't seem to be an easy way to know which services actually have EPG. In other words, completion doesn't seem to be deterministic. Having said all that, the only reason I can think of that you could experience this in the first place is if your provider only broadcasts EPG for a few hours, and your PC sleeps for a few hours without a chance to update the data. IMO that isn't (or shouldn't be) a common situation, because [good] providers usually like to broadcast ~7 days of data. So, I wonder whether your grabbing is configured correctly (ie. to get the "long range" guide data) and/or whether your short timeout is actually preventing you from getting the "long range" data that would solve the problem. Hope that makes sense? :) [/QUOTE]

Verification