- MP2 Version
Description:
Although all scheduled recordings use the same recording settings (5 minutes before and after a show), two of the seven TV shows I record each week do not follow the rule.
I removed them from the records schedule and add them back as new recordings (every week at the same time) but nothing changed. I double-checked their setting using both TV settings GUI and MP2TVE_3 database but everything seem OK. I provide a copy of schedule and recording tables from MP2TVE_3 database in csv format. Faulty recordings are ...
In provided csv file, you can see that the schedule table seems OK (startTime, endTime, preRecordInterval, postRecordInterval) but the recording table shows that it actually started five minutes after the TV show began (i.e. 20:05 instead of 19:55 for rowid 1323, 19:35 instead of 19:25 for rowid 1328).
My PC is kept up-to-date on a weekly basis.
I have two TV cards.
Steps to Reproduce:
I do not understand why it happens so I can't reproduce the problem on demand :-(
.
Although all scheduled recordings use the same recording settings (5 minutes before and after a show), two of the seven TV shows I record each week do not follow the rule.
I removed them from the records schedule and add them back as new recordings (every week at the same time) but nothing changed. I double-checked their setting using both TV settings GUI and MP2TVE_3 database but everything seem OK. I provide a copy of schedule and recording tables from MP2TVE_3 database in csv format. Faulty recordings are ...
- schedule table: rowid 622 and 623
- recording table: rowid 1323 and 1328.
In provided csv file, you can see that the schedule table seems OK (startTime, endTime, preRecordInterval, postRecordInterval) but the recording table shows that it actually started five minutes after the TV show began (i.e. 20:05 instead of 19:55 for rowid 1323, 19:35 instead of 19:25 for rowid 1328).
My PC is kept up-to-date on a weekly basis.
I have two TV cards.
Steps to Reproduce:
I do not understand why it happens so I can't reproduce the problem on demand :-(
.