Opened 13 years ago

Closed 11 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


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)

myth3.log (84.3 KB) - added by anonymous 13 years ago.

Download all attachments as: .zip

Change History (9)

Changed 13 years ago by anonymous

Attachment: myth3.log added

comment:1 Changed 13 years ago by david.morris@…

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.

comment:2 Changed 13 years ago by David.Morris@…

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 13 years ago by Janne Grunau

Owner: changed from Isaac Richards to Janne Grunau
Status: newassigned

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 12 years ago by stuartm

Component: mythtvMythTV - DVB

comment:5 Changed 11 years ago by simons.philippe@…

same PESPacket error here on DVB-C with EIT (without EIT there was no errors)

livetv and backend works fine here.

comment:6 Changed 11 years ago by Stuart Auchterlonie

Milestone: unknown0.23

comment:7 Changed 11 years ago by Janne Grunau

Milestone: 0.230.24
Priority: minortrivial

comment:8 Changed 11 years ago by robertm

Resolution: Won't Fix
Status: assignedclosed

Closing this long-neglected ticket as nobody seems willing to work on it, and because the message appears purely cosmetic.

Note: See TracTickets for help on using tickets.