2014-11-05, 06:18 AM
(This post was last modified: 2014-11-05, 06:27 AM by Qwerty2014.)
In the past when I want to schedule something manually, I make use of the command line 'schedule.exe'.
When I want to make use of a specific tuner at the same time and it was already been scheduled / occupied by something else, I received always a failed error message.
But recently when this situation happens, it accepts the added new schedule with the consequence of a scheduled conflict.
When I schedule with the help of the command line 'schedule.exe' a couple of times making use of exactly the same schedule definition, I see straight into the database multiple times the same record lines in table 'scheduled_recording'. Only the field 'oid' (of course) has a unique different number for each record line.
Has something been changed in the NPVR manual scheduling system recently?
When I want to make use of a specific tuner at the same time and it was already been scheduled / occupied by something else, I received always a failed error message.
But recently when this situation happens, it accepts the added new schedule with the consequence of a scheduled conflict.
When I schedule with the help of the command line 'schedule.exe' a couple of times making use of exactly the same schedule definition, I see straight into the database multiple times the same record lines in table 'scheduled_recording'. Only the field 'oid' (of course) has a unique different number for each record line.
Has something been changed in the NPVR manual scheduling system recently?