Back To Back recordings fail on DVB-T (1 Viewer)

SciDoctor

Retired Team Member
  • Premium Supporter
  • February 2, 2005
    1,465
    139
    England
    I think the problem only occurs with 'always' schedules.

    When 'always' schedules start two actual schedule handlers exist, 'the parent' which spawns the 'child'.

    The 'child' schedule is the one that is recording the stream

    If the 'child' schedule is stoped at anytime within the schedule time then 'the parent' will respawn a new 'child'.

    SO when a schedule clash occurs with respect to time then the first schedule is stoped and the next actioned, the logs show this.

    BUT with an 'always' schdule only the 'child' is stoped and then the 'parent' respawns another child which is causing the conflicting clash with the next already actioned schedule.

    What is needed is that both the 'child' and 'parent' are removed form the schedule queue.
     

    SciDoctor

    Retired Team Member
  • Premium Supporter
  • February 2, 2005
    1,465
    139
    England
    Checking through some new logs my above conclusions may be partialy true. Logs attached.

    What may be happening is that the 'parent' is stoped and removed form the schedule queue (this would be normal for both 'single' schedules and 'always' schedules') but the 'child' isn't and restarts .
     

    Users who are viewing this thread

    Top Bottom