I've seen this too. The problem (for me) is, that the data in the XML-TV changes.
For example:
I have 7 days of EPG-data, so let's say the show shows up on monday, the start-time in the EPG is then 22:00.
Then, on wednesday the schedule changes, it's now scheduled for 22:10.
Because the show is already scheduled (by Season recordings), it won't delete the original entry. The show is now scheduled twice....
This is the reason I have switched to "PriorityRecordings", and I have added the "DeleteSchedule" utility. Now, each day "PriorityRecordings" delete's all scheduled shows, then (after the EPG update) it reschedules them...
I'm not sure this is what's happening on your end, but that's what I had...
I am working on an "EPGDiff" tool that should solve this problem once and for all...
When you have the 'complete epg reload' option enabled, this is the steps that occur during the overnight automated update:
1) Retrieve show listings (and just hold in memory)
2) Delete all pending recordings that are part of a season recording (they'll be recreated at later in the update process)
3) Delete all show listing from the database that arent referenced by a pending recording
4) Save new show listings to database
5) Check for any season recordings that need to be scheduled.
This logic should take care of the situation that your describe.
I wonder if the recordings created by "PriorityRecordings" arent correctly setting the recording group, so GB-PVR has no idea the recordings are part of a 'season recording'. This would cause this to happen.
Just wanted to add my $0.02 - i get this every week recording Dancing On Ice (UK, ITV1 Sat) also.
I end up with 2 recordings, 1 in which half the show is missing and the other "failed"
the-warriners Wrote:Just wanted to add my $0.02 - i get this every week recording Dancing On Ice (UK, ITV1 Sat) also.
I end up with 2 recordings, 1 in which half the show is missing and the other "failed"
I'm surprised you've missed half the show. It's only a 5 minute overlap and so I would have thought that pre and post padding would have made up for that either way?
What I did check today was that the xml data was correct and it is, the correct timing is 7:15.
I also looked into the database and there are definately two instances being recorded for the saturday, 7:10 and 7:15. I couldn't find where the original season recording was anymore, I thought I had deleted it and started again.
Quote:When you have the 'complete epg reload' option enabled, this is the steps that occur during the overnight automated update:
1) Retrieve show listings (and just hold in memory)
2) Delete all pending recordings that are part of a season recording (they'll be recreated at later in the update process)
3) Delete all show listing from the database that arent referenced by a pending recording
4) Save new show listings to database
5) Check for any season recordings that need to be scheduled.
This logic should take care of the situation that your describe.
Was this added with the "complete epg reload" switch? I'm sure I tested in version 94 and then it was happening.....
Means I need to take another look at season-recordings
All I can offer is that my PROGRAMME table contains the two time slots, 7:10 and 7:15 instances of Dancing on Ice on the same date, now in this case the 25th Feb, (and others that show the same problem) and yet the xml file contains only the 7:15, i'm doing a daily xml update with a full reload.
I'm not clear how the other one is popping up?
I have 3 tuners, all updating using the same xml file.
I don't know if you want any more info or in which direction I should look next?
2006-03-01, 08:06 AM (This post was last modified: 2006-03-01, 08:30 AM by HtV.)
Sub Wrote::o
Quote:
When you have the 'complete epg reload' option enabled, this is the steps that occur during the overnight automated update:
1) Retrieve show listings (and just hold in memory)
2) Delete all pending recordings that are part of a season recording (they'll be recreated at later in the update process)
3) Delete all show listing from the database that arent referenced by a pending recording
4) Save new show listings to database
5) Check for any season recordings that need to be scheduled.
This logic should take care of the situation that your describe.
Ton:
Was this added with the "complete epg reload" switch? I'm sure I tested in version 94 and then it was happening.....
Means I need to take another look at season-recordings
Could this also be done by a commandline-switch. I guess -OnlyEmptyEpg + -OnlyUpdateEpg does not do all this.
EDIT: I'll try with UpdateEpg.bat first.
What happens if you are recording or watching a show (or both) during this "complete Epg reload"?
I want to do this during daytime because I shut off my computer during the night.