2007-09-18, 03:20 AM
This is kind of a FYI to anyone who comes across this and also a 'bug/feature' report. If it's not appropriate for the support forum, feel free to move it sub.
On Sunday night, I somehow managed to set my PC date to October (I think I touched the scroll-wheel on my mouse after opening the date/time app from the systray). Later that evening I started the gbpvr app. to see what had recorded that day and 'What's New' showed a message saying there was nothing from the past seven days. I checked Pending and it said there was nothing pending. At that point I realised the month was wrong - OK, that explained things - I set the month back to September.
The problem was that it didn't occur to me that all the pending recordings for the next two weeks had been marked in the DB as 'Failed'. Logical, I suppose, as the rec. service had (for a couple of hours) thought it was 4 weeks in the future.
I left things as they were expecting the 7am scheduled EPG update to recreate the pending recordings from my Reoccurring list but it didn't (due to the fact that what should have been created as pending were marked as failed in the DB and thus ignored).
When I worked out what was going on, I went through all of my recordings folders in the 'Ready' section, deleted all the failed recordings, emptied the EPG then did an UpdateEPG from the System plugin. Everything back to normal. Two of my wife's programmes not recorded though. :eek:
So that's the FYI bit.
sub - would it be possible to add some logic to analyse the date/time stamp of apparently failed recordings and identify the fact that they can't possibly have failed because, in this scenario, they weren't due to record for another week (for example)?
If the EPG process thinks it's the 18th Sept., the EPG source says there's a programme to schedule on the 19th (for example) but the DB thinks that programme has already been attempted and failed, the logic should be the EPG and current date override the 'Failed' marker.
Cheers,
Brian
On Sunday night, I somehow managed to set my PC date to October (I think I touched the scroll-wheel on my mouse after opening the date/time app from the systray). Later that evening I started the gbpvr app. to see what had recorded that day and 'What's New' showed a message saying there was nothing from the past seven days. I checked Pending and it said there was nothing pending. At that point I realised the month was wrong - OK, that explained things - I set the month back to September.
The problem was that it didn't occur to me that all the pending recordings for the next two weeks had been marked in the DB as 'Failed'. Logical, I suppose, as the rec. service had (for a couple of hours) thought it was 4 weeks in the future.
I left things as they were expecting the 7am scheduled EPG update to recreate the pending recordings from my Reoccurring list but it didn't (due to the fact that what should have been created as pending were marked as failed in the DB and thus ignored).
When I worked out what was going on, I went through all of my recordings folders in the 'Ready' section, deleted all the failed recordings, emptied the EPG then did an UpdateEPG from the System plugin. Everything back to normal. Two of my wife's programmes not recorded though. :eek:
So that's the FYI bit.
sub - would it be possible to add some logic to analyse the date/time stamp of apparently failed recordings and identify the fact that they can't possibly have failed because, in this scenario, they weren't due to record for another week (for example)?
If the EPG process thinks it's the 18th Sept., the EPG source says there's a programme to schedule on the 19th (for example) but the DB thinks that programme has already been attempted and failed, the logic should be the EPG and current date override the 'Failed' marker.
Cheers,
Brian