Thanks for the hint: I've taken a trace-log from tvheadend when listening to an audio-only channel with "performance" enabled (btop shows clock at 1 GHz all of the time) and there are indeed continuity errors at a rate of more than one a second:
Question is, with hardly any CPU used, good signal strength and quality, what can be causing so many continuity errors?
Code:
Nov 29 10:45:02 PiTV tvheadend[657]: tbl-pass: pass-eit: -: PID 0012 CC error 12 != 10Nov 29 10:45:02 PiTV tvheadend[657]: tbl-pass: pass-eit: -: PID 0012 CC error 8 != 7Nov 29 10:45:02 PiTV tvheadend[657]: tbl-pass: pass-eit: -: PID 0012 CC error 14 != 9Nov 29 10:45:02 PiTV tvheadend[657]: tbl-eit: eit: 522MHz in DVB-T Network: PID 0012 CC error 12 != 10Nov 29 10:45:02 PiTV tvheadend[657]: tbl-eit: eit: 522MHz in DVB-T Network: PID 0012 CC error 8 != 7Nov 29 10:45:02 PiTV tvheadend[657]: tbl-eit: eit: 522MHz in DVB-T Network: PID 0012 CC error 14 != 9Statistics: Posted by Rob Meades — Fri Nov 29, 2024 10:51 am