[mythtv] UK EIT problems - CRC errors
Paul Catchpole
paul at paulcatchpole.co.uk
Mon Dec 10 19:07:08 UTC 2007
Hi all,
I'd posted this, initially, to the Users list but don't seem to have
found anyone with similar problems - so I thought I'd see if the devs
have any ideas...?
I'm having some problems with EIT in the UK...
I have the following cards running:
Myth Master:
Kworld DVB-T-100 Cardid: 0 Using EIT
Kworld DVB-T-100 Cardid: 3 Using EIT
Kworld DVB-S-100 Cardid: 2 Using RadioTimes [Astra 28 2B-etc]
Kworld DVB-S-100 Cardid: 4 Using EIT [Astra 19 1E etc]
Myth Slave:
Kworld DVB-S-100 Cardid: 1 Using EIT [Hotbird]
I've been running SVN Trunk since the CVS days, as it were, although I
update infrequently.
The problem I'm seeing is that EIT has (recently) stopped working for
one of the DVB-T cards only, the other is still running fine.
To make things worse, I'm not entirely sure when this started. I do know
it was around the time I brought the slave backend online, which was
around two weeks after adding the two DVB-S cards in the Master backend.
To make it even more difficult to troubleshoot, I updated at that time,
from a March 07ish SVN to a 14xxx build.
*Both* DVB-T cards did work for EIT until sometime in the aforementioned
two-week period.
I've finally gotten around to trying to sort this out today, and hence
I've updated to current SVN15091 - that includes building for both
backends and the diskless frontend base system.
To help eliminate the DVB-S EIT grabbing, I've changed the grabber to
'none' for both of the DVB-S cards which were using it. I've also run a
mythfilldatabase --update, which completed okay.
StreamID is always 0x70, if that matters...
Signal levels to the two DVB-T cards are good, as checked on a Promax,
and empirically confirmed by seeing no signal problems at all with the
output from these cards.
Checking in the program table shows that there's no entries whatsoever
for chanid 2001 [BBC One, card 2] but there are lots and lots for chanid
1001, as expected from the frontend programme guide.
Logs from eit, siparser, important, general, on the master backend are
showing the following:
2007-12-09 17:22:27.199 PESPacket: Failed CRC check 0xab172228 !=
0xcefc826c for StreamID = 0x70
2007-12-09 17:22:27.422 PESPacket: Failed CRC check 0xab172226 !=
0xcefc826c for StreamID = 0x70
2007-12-09 17:22:28.206 PESPacket: Failed CRC check 0xab172229 !=
0xcefc826c for StreamID = 0x70
2007-12-09 17:22:28.432 PESPacket: Failed CRC check 0xab172227 !=
0xcefc826c for StreamID = 0x70
2007-12-09 17:22:29.206 PESPacket: Failed CRC check 0xab172230 !=
0xcefc826c for StreamID = 0x70
2007-12-09 17:22:29.457 PESPacket: Failed CRC check 0xab172228 !=
0xcefc826c for StreamID = 0x70
2007-12-09 17:22:30.197 PESPacket: Failed CRC check 0xab172231 !=
0xcefc826c for StreamID = 0x70
2007-12-09 17:22:30.425 PESPacket: Failed CRC check 0xab172229 !=
0xcefc826c for StreamID = 0x70
2007-12-09 17:22:31.208 PESPacket: Failed CRC check 0xab172232 !=
0xcefc826c for StreamID = 0x70
2007-12-09 17:22:31.447 PESPacket: Failed CRC check 0xab172230 !=
0xcefc826c for StreamID = 0x70
2007-12-09 17:22:32.195 PESPacket: Failed CRC check 0xab172233 !=
0xcefc826c for StreamID = 0x70
2007-12-09 17:22:32.430 PESPacket: Failed CRC check 0xab172231 !=
0xcefc826c for StreamID = 0x70
2007-12-09 17:22:33.205 PESPacket: Failed CRC check 0xab172234 !=
0xcefc826c for StreamID = 0x70
2007-12-09 17:22:33.452 PESPacket: Failed CRC check 0xab172232 !=
0xcefc826c for StreamID = 0x70
2007-12-09 17:22:34.205 PESPacket: Failed CRC check 0xab172235 !=
0xcefc826c for StreamID = 0x70
2007-12-09 17:22:34.429 PESPacket: Failed CRC check 0xab172233 !=
0xcefc826c for StreamID = 0x70
I left my job earlier this year where I had to write DVB-C tables by
hand for Teleste kit and it's amazing how quickly the knowledge has
disappeared from my head - so I'm failing to understand what's going on
here! :-)
Can anyone shed any light on this?
Cheers,
Paul
More information about the mythtv-dev
mailing list