Project

General

Profile

Actions
Copy link

Feature #4602

open

Hardcoded max error value will sort out "okayish" recordings

Added by Roland A. over 7 years ago. Updated about 4 years ago.

Status:
New
Priority:
Normal
Assignee:
Adam Sutton
Category:
PVR / DVR
Target version:
4.6
Start date:
2017-09-17
Due date:
% Done:

0%

Estimated time:

Description

Please read this topic to get into the problem: https://tvheadend.org/boards/5/topics/22608?r=28512

We define DVR_MAX_DATA_ERRORS to 10000 in src/dvr/dvr.h.

This will, at least for me, always sort out long recordings of HD 720p streams (german FTA "Das Erste HD"). The error count is at ~13000 for 3h30 of recording time.
I was fighting with myself if I should create this ticket as a bug or a feature. For my personally, it is a too strict default value and my TVheadend regularly sorts out long HD recordings (happens every now and then). If I play them, the error rate seems to be "okayish".

I propose 2 changes:
Idea is to not only make this user configurable, but also not a static value without references. We should make a limit relative to a timeframe, e.g. "Avg 5000 errors per hour". An example - if a recording takes 3h30, the individual "sort out threshold" would be 17500. On a 30 minute recording, it is 2500.

Currently the system will sort out longer recordings with a higher probability because of this.
Also, and this makes it worse, the button "Move to finished" in the "Failed recordings"-tab is not doing anything. (I will file a bug for this).

I'm using HTS Tvheadend 4.2.3-33~ga255d82 from the source "http://dl.bintray.com/mpmc/deb raspbianjessie stable-4.2" on a Raspberry Pi 2 connected to a 4way SAT>IP server Kathrein EXIP414/E. The local path for recordings is a NFS mount from FreeNAS 11. Perhaps this situation, with the Pi as the TVH server, provokes the situation as described as the NIC is limited on that device.

Actions
Copy link

Also available in: Atom PDF