Opened 16 years ago
Closed 14 years ago
#5013 closed defect (Won't Fix)
Constant PESPacket CRC check failure
| Reported by: | anonymous | Owned by: | Janne Grunau |
|---|---|---|---|
| Priority: | trivial | Milestone: | 0.24 |
| Component: | MythTV - DVB | Version: | unknown |
| Severity: | medium | Keywords: | |
| Cc: | Ticket locked: | no |
Description
I'm getting constant: "PESPacket: Failed CRC check 0x12173536 != 0xca3d9fdb for StreamID = 0x70" failure reports.
Though everything seems to be working OK, (EIT scanning, watching live TV). Attached mythbackend log showing the issue.
Attachments (1)
Change History (9)
comment:1 Changed 16 years ago by
comment:2 Changed 16 years ago by
I discovered that my signal booster had packed up and was receiving very weak signals. Once replaced this error went away, so this more than likely isn't a bug.
comment:3 Changed 16 years ago by
| Owner: | changed from Isaac Richards to Janne Grunau |
|---|---|
| Status: | new → assigned |
It might not even be signal related, we are at one place checking the CRC before we could decide if the table has a CRC.
The Time and Date Table which has table_id (stream_id) 0x70 has no CRC.
comment:4 Changed 15 years ago by
| Component: | mythtv → MythTV - DVB |
|---|
comment:5 Changed 14 years ago by
same PESPacket error here on DVB-C with EIT (without EIT there was no errors)
livetv and backend works fine here.
comment:6 Changed 14 years ago by
| Milestone: | unknown → 0.23 |
|---|
comment:7 Changed 14 years ago by
| Milestone: | 0.23 → 0.24 |
|---|---|
| Priority: | minor → trivial |
comment:8 Changed 14 years ago by
| Resolution: | → Won't Fix |
|---|---|
| Status: | assigned → closed |
Closing this long-neglected ticket as nobody seems willing to work on it, and because the message appears purely cosmetic.
I also get this:
2008-04-11 13:55:41.709 DTVSM(1): Time Offset: -1.7094 2008-04-11 13:55:41.981 PESPacket: Failed CRC check 0x27125541 != 0xca3d9fdb for StreamID = 0x70
I'm using EIT in the Uk with DVB-T
However I'm unable to watch liveTV because the backend just hangs but doesn't crash. Not sure if that is releated to this.