Feature #3165

error counters could be more precise

Added by Mario D about 2 years ago. Updated about 2 years ago.

Status:FixedStart date:2015-10-16
Priority:NormalDue date:
Assignee:-% Done:

100%

Category:-
Target version:4.2

Description

The 'errors' and 'data errors' counters for DVR entries are very useful to detect problems caused by adapters or descrambling cards.

The actual method to detect the decoding errors cannot permit to evaluate "how much is damaged" a recording. Late decoding of ECMs causes discontinuity that are correctly counted on 'data errors'. If I stop the oscam reader (to simulate card or oscam connection problems), the errors on the log ("descrambler: cannot decode packets for service") do not increase any counter. When I resume the reader, few discontinuities (2 or 3) are detected but nothing that is proportional to the damages. A frame glitch has the same weight than blackout of 5, 10 or 60 minutes. I can provide logs, but the problem is easily reproducible with any card.

It would be great if the counters could include such "damages" related to the absence of video data: IMHO, it would be more informative for the user.

Associated revisions

Revision 76b23200
Added by Jaroslav Kysela about 2 years ago

descrambler/tsdemux: propagate descramble errors to other layers, fixes #3165

History

#1 Updated by B C about 2 years ago

this would have to be something like a counter for non decrypted ts packages. and then you only have an idea how wrong it went :-)

#2 Updated by Jaroslav Kysela about 2 years ago

  • Target version set to 4.2

#3 Updated by Jaroslav Kysela about 2 years ago

  • Status changed from New to Fixed
  • % Done changed from 0 to 100

Also available in: Atom PDF