Opened 13 years ago
Closed 6 years ago
#11247 closed Bug Report - General (Abandoned)
EIT supplied by provider ignored by mythtv
| Reported by: | Owned by: | Stuart Auchterlonie | |
|---|---|---|---|
| Priority: | minor | Milestone: | unknown |
| Component: | MythTV - EIT | Version: | 0.25-fixes |
| Severity: | medium | Keywords: | |
| Cc: | Ticket locked: | no |
Description
Setup: There is a two DVB providers on one sattelite. One provider's (Original_network_ID 112 in dvbsnoop) EIT shown in myth and worked as expected. Other's (Original_network_ID 65535 - Russian's Tricolor) not displayed at all. Tuning and recording by setting up manual recording work's fine.
SELECT * FROM channel WHERE useonairguide=0; Empty set (0.00 sec)
./dvbsnoop -s sec 0x12 sees EIT for both providers, a little clip of logs attached.
Attachments (6)
Change History (12)
by , 13 years ago
| Attachment: | tricolor.dvbsnoop added |
|---|
by , 13 years ago
| Attachment: | ntv.dvbsnoop added |
|---|
comment:1 by , 13 years ago
the ONID of -1 / 0xffff / 65535 looks fishy, maybe they have other flags set to values that "work by accident"
Transport_stream_ID: 39 (0x0027) Original_network_ID: 65535 (0xffff) [= >>ERROR: not (yet) defined... Report!<<]
vs.
Transport_stream_ID: 280 (0x0118) Original_network_ID: 112 (0x0070) [= BONUM1; 36 Degrees East | NTV+]
can you add a log of
dvbsnoop 0x0,0x11
0x0 being the PAT, 0x11 being the SDT (has the flags that signal EIT presence)
Searching the net led me to http://www.dvbviewer.tv/forum/topic/41859-tricolor-tv-epg/ which hints that #10784 might help
by , 13 years ago
| Attachment: | snoop0x0.dvbsnoop added |
|---|
by , 13 years ago
| Attachment: | snoop0x11.dvbsnoop added |
|---|
comment:2 by , 13 years ago
I'm glad to provide any information I can.
As I see ONID, TransportID, ServiceID are present, but I can make mistake.
But I note that EIT_schedule_flag and EIT_present_following_flag set to zero while for NTV+ both of them set to 1.
comment:3 by , 13 years ago
Digging a little this trac shows that ticket #9592 deals with similar problem. Could the ticket help me?
comment:4 by , 13 years ago
Yes, patching the code as shown in http://code.mythtv.org/trac/ticket/9592#comment:3 might be all it takes. (that ticket is a bad example as it mixes multiple different cases of "no guide" which makes following harder)
comment:5 by , 13 years ago
I applied patch from #9592. Some events appeared in EPG but most of them not.
Then I used patch v2 from #10784. A little more events in EPG but, again, not all.
Meanwhile a lot of such messages appeared in backend log:
2012-11-21 22:59:09.165158 E [28663/29867] DVBRead dtvsignalmonitor.cpp:347 (HandlePMT) - DTVSM(/dev/dvb/adapter3/frontend0): Wrong PMT; pmt->pn(39095) desired(39080) 2012-11-21 22:59:09.165434 E [28663/29867] DVBRead dtvsignalmonitor.cpp:347 (HandlePMT) - DTVSM(/dev/dvb/adapter3/frontend0): Wrong PMT; pmt->pn(39075) desired(39080) 2012-11-21 22:59:09.165519 E [28663/29867] DVBRead dtvsignalmonitor.cpp:347 (HandlePMT) - DTVSM(/dev/dvb/adapter3/frontend0): Wrong PMT; pmt->pn(39105) desired(39080) 2012-11-21 22:59:09.165560 E [28663/29867] DVBRead dtvsignalmonitor.cpp:347 (HandlePMT) - DTVSM(/dev/dvb/adapter3/frontend0): Wrong PMT; pmt->pn(39115) desired(39080)
I made attempt to contact with Tricolor. They say that as I do not use a "recommended receiver" they can't help me. Tricolor sets low recurring fee and sells own receivers with a margin on its. I suspect they broke EIT intentionally to force subscribers to buy "recommended" equipment.
Is it possible to make workaround to get EIT working?
comment:6 by , 6 years ago
| Resolution: | → Abandoned |
|---|---|
| Status: | new → closed |
As per ticket #9592 the checks on the EIT presence as indicated by the SDT are ignored. For some networks that are known to be wrong the EIT presence can be forced. If this problem is still present then please re-open this ticket or create a new one and mention the network ID so that it can be added to the list of exceptions. Given the age of this ticket it is now closed.

DVBsnoop logs