Mailing List Archive

Re: [mythtv-commits] Ticket #13470: When a recording is started late due to a just restarted or unresponsive backend, it is not marked failed eligible for re-recording
On 07/20/2019 06:42 AM, MythTV wrote:
> #13470: When a recording is started late due to a just restarted or unresponsive
> backend, it is not marked failed eligible for re-recording
> --------------------------------------+----------------------------
> Reporter: wispfrog | Owner: JYA
> Type: Bug Report - General | Status: new
> Priority: minor | Milestone: needs_triage
> Component: MythTV - Recording | Version: v29.1
> Severity: medium | Keywords: late recording
> Ticket locked: 0 |
> --------------------------------------+----------------------------
> Was also with v0.28... both versions from ubuntu lts, so not a new thing.
> (And 0.29.1 starts many fewer recordings late)
>
> The recording gets a filename that shows the start time being minutes
> /after/ the scheduled time, so could be driven off whenever that is
> generated.

Are you saying the recording is not marked as damaged? It should be
marked to allow re-record (duplicate = 0), as MythTV has done that since
forever (long before we even had damaged recording detection). IMO, it
is correct to not mark it as damaged--what recording is there is not
damaged and if it re-airs, it will be re-recorded.

Mike
_______________________________________________
mythtv-dev mailing list
mythtv-dev@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-dev
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org