Opened 19 years ago

Closed 19 years ago

#2286 closed defect (invalid)

Excessive Unknown PID 0x11/0x12 errors when both exist in stream

Reported by: Mark.Buechler@… Owned by: danielk
Priority: minor Milestone: 0.21
Component: dvb Version: head
Severity: medium Keywords:
Cc: Ticket locked: no

Description

Running v10968 getting excessive "Unknown PID 0x12" and some "Unknown PID 0x11" when both PIDs are available in the stream. Backend log and dvbsnoops attached.

Attachments (3)

backend3.txt​ (54.8 KB ) - added by Mark.Buechler@… 19 years ago.
Backend log
sample_pid_0x11.txt​ (24.0 KB ) - added by Mark.Buechler@… 19 years ago.
DVBsnoop PID 0x11
sample_pid_0x12.txt​ (44.3 KB ) - added by Mark.Buechler@… 19 years ago.
DVBsnoop PID 0x12

Download all attachments as: .zip

Change History (8)

by Mark.Buechler@…, 19 years ago

Attachment: backend3.txt​ added

Backend log

by Mark.Buechler@…, 19 years ago

Attachment: sample_pid_0x11.txt​ added

DVBsnoop PID 0x11

by Mark.Buechler@…, 19 years ago

Attachment: sample_pid_0x12.txt​ added

DVBsnoop PID 0x12

comment:1 by Isaac Richards, 19 years ago

Milestone: 0.20

comment:2 by Mark.Buechler@…, 19 years ago

Just as a side note, this problem prevents me from picking up EIT in passive mode while active EIT mode works just fine.

comment:3 by danielk, 19 years ago

Milestone: → 0.21

The code that determines which EIT pids we listen on is AdjustEITPIDs(), somehow this must be enabled without us listening on the PID for the "Unknown PID 0x12" messages.

For the "Unknown PID 0x11", we must not be listening to SDTs this is a seperate problem using unrelated code.

comment:4 by danielk, 19 years ago

(In [11007]) Refs #2286. Moves "Unknown PID" message from VB_IMPORTANT to VB_RECORD. (temp fix for filtering problem, underlying problem means EIT takes longer to collect).

comment:5 by Janne Grunau, 19 years ago

Resolution: → invalid
Status: new → closed

Mark, does it still happen?

Does it happen with unpatched MythTV or since it won't work at all unpatched only with my psifixup proof of concept patch?

I'll close the ticket since I suspect, that your tuning patches was the cause of this error.

Note: See TracTickets for help on using tickets.