sadownik Posted December 17, 2018 Share Posted December 17, 2018 Hello, seems that DVBViewer improperly parsing EIT PID in following stream: (165MB 60 seconds of multiplex) https://drive.google.com/file/d/1l_annlpq1BqLn3IegEEsFVsh7dd7niDi/view?usp=sharing Picture - TsReaderLite 2.8.5.3a (transport file stream loop open with above file) and DVBViewer 6.1.2.0 (DVB File device and above file as hardware) I suppose, that this stream is slightly out of ETSI, but hardware receivers: LCD/LED TV and STB DVB-T and TSReader "seeing" all EPG. support.zip Quote Link to comment
Alan_SP Posted December 17, 2018 Share Posted December 17, 2018 It looks like you have similar situation as is in my country. To see solution, check this thread: https://www.DVBViewer.tv/forum/topic/61419-epg-problem-sometimes-theres-no-epg-information/ Quote Link to comment
Griga Posted December 18, 2018 Share Posted December 18, 2018 6 hours ago, sadownik said: (165MB 60 seconds of multiplex) Thanks for the sample. I've downloaded it, and I will have a closer look at it as soon as I find timer for it. Quote Link to comment
Griga Posted December 18, 2018 Share Posted December 18, 2018 P.S. There is something I can see already now in the TransEdit Analyzer. The broadcaster is using the same Event ID for different programs (or more to the point, for the same program at different times). This does not comply with the DVB specifications (Event IDs must be unique and unambiguous) and quite troublesome for software that does not just receive the EPG data, but stores it in a database. Read more about it here. TransEdit (see download area, it's similar to TSReader) just lists the arriving data and doesn't mind. But in DVBViewer it's a different thing, because it does a lot more with the data... Quote Link to comment
Alan_SP Posted December 18, 2018 Share Posted December 18, 2018 16 hours ago, Griga said: The broadcaster is using the same Event ID for different programs Yes, this is exactly problem with my country also, so the same solution should work without problems. Quote Link to comment
Griga Posted December 18, 2018 Share Posted December 18, 2018 6 minutes ago, Alan_SP said: Yes, this is exactly problem with my country Not necessarily. As far as I can see, your broadcaster only re-uses Event IDs on EPG updates for different programs. DVBViewer 6.1.2 and DMS 2.1.2 provide measures against this bad habit, so maybe your solution is not needed anymore. However, in the case described above Event IDs are probably re-used within one set of EPG data, which would be even worse. Quote Link to comment
sadownik Posted December 18, 2018 Author Share Posted December 18, 2018 Thanks for quick clarify. Before sending request to broadcaster ("we are innocent > look at hardware receivers") - where ETSI claims about unique Event IDs? I'm thinking about import EIT from RS service, editing in EPG collect, rename every EVENT_ID to hmm maybe time based logic and send back to RS (for testing - fortunately it is not permanent situation). Quote Link to comment
Griga Posted December 18, 2018 Share Posted December 18, 2018 30 minutes ago, sadownik said: where ETSI claims about unique Event IDs? ETSI EN 300 468 V1.15.1 5.2.4 Event Information Table (EIT) Semantics for the event information section: event_id: This 16-bit field contains the identification number of the described event (uniquely allocated within a service definition). Quote Link to comment
bonifacy Posted March 18, 2019 Share Posted March 18, 2019 Polish DVB-T MUX-3, TVP http://www.sat-charts.eu/dvb-t.php?mux=MUX-3 EPG is also often incomplete too. There are often a few hours of loss. 1. EPG DVBViewer, see pic 1 2. EPG Tuner Golden Media Spark_ONE_TRIPLEX, see pic 2 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.