EPG Update doesn't Empty EPG for searched shows?

[jksmurf]

I have update EPG scheduled with EMPTY EPG checked in the config.

The EPG appears to update, but the previous records still appear to be in the database.

e.g. Last Week ABCAsiapacific made a scheduling mistake and had "White Teeth" on at 12:14~1:00PM on Tue 18th July. I scheduled a single record of the show at that program time.

A later EPG update changed the schedule to the corrected time of "White Teeth", 12:00~1:00PM on Tue 18th July. I canceled the 12:14~1:00PM show and re-scheduled the correct time.

The corrected time appears in the TV Guide (see jpg), so I thought, great, the old EPG was emptied and the program schedule updated. However if I do an episode search on "White Teeth" BOTH the new time and the old time appear in the search list? (see other jpg). I checkedthe XML file and that's fine. It seems like the database is not flushing out the old data?

k.

[Koenie]

This might be true. I have seen this before when it caused a tuner conflict in my setup. I had the show programmed as reoccuring and had to delete the reoccuring, reimport the epg and reschedule the recording to fix the conflict.

[jksmurf]

Yes, I can get rid of it by going into the Database and deleting it manually, but I thought this was done automagically.... I now realise it has happened several times, (I thought sub's patch would fix it) but this is the first time I've investigated it a bit more fully.

k.

[jksmurf]

sub, is there any way to force a flush of the database?

k.

[garyeuph]

This is discussed in depth in this thread, but no solution yet

http://forums.nextpvr.com/showthread.php?t=16040

[jksmurf]

This is discussed in depth in this thread, but no solution yet

http://forums.nextpvr.com/showthread.php?t=16040

Just looked at that thread. Goodness me, you are correct, that's EXACTLY my problem...

k.

[sub]

I have update EPG scheduled with EMPTY EPG checked in the config.

The EPG appears to update, but the previous records still appear to be in the database.

e.g. Last Week ABCAsiapacific made a scheduling mistake and had "White Teeth" on at 12:14~1:00PM on Tue 18th July. I scheduled a single record of the show at that program time.

A later EPG update changed the schedule to the corrected time of "White Teeth", 12:00~1:00PM on Tue 18th July. I canceled the 12:14~1:00PM show and re-scheduled the correct time.

The corrected time appears in the TV Guide (see jpg), so I thought, great, the old EPG was emptied and the program schedule updated. However if I do an episode search on "White Teeth" BOTH the new time and the old time appear in the search list? (see other jpg). I checkedthe XML file and that's fine. It seems like the database is not flushing out the old data?

k.

What your describe is the expected behaviour for one-off recordings. GB-PVR does not attempt to remove this type of recording and reschedule it for the new time. While the your example above may seem pretty straight forward to identify the show from the new times, there any many situations where the show has moved beyond the end time, and GB-PVR has no way to tell if it is actually the same show. The title is not enough. Often there are several shows with the same title within a two or three hour period.

Season recordings behave a little differently. After the EPG data has been retrieved, but before it is stored in the database, currently scheduled episodes of season recordings are removed from the database, then the listings are removed, then the new listings are saved followed by the rescheduling of any season recordings. In effect, individual episodes of a season recording should be correctly updated if the it's times change.

[jksmurf]

What your describe is the expected behaviour for one-off recordings.

Cheers sub, thank you for the clear explantion. At least it's not my machine burping bad karma.

GB-PVR has no way to tell if it is actually the same show. The title is not enough. Often there are several shows with the same title within a two or three hour period.

OK, I understand the reason for a one-off show recorded in a certain time slot and to change that behaviour could have GBPVR confused about whether to record an earlier or later episode of the same show, based on name alone.

However, (unless you have set a manual recording where you might, but unlikely, wish to record 1/2 a show), surely if you have committed to a complete EPG reload (in the config), you are already saying "OK, whatever show I scheduled" for that time slot has moved as a whole show, so I'd like GBPVR to record the next closest show (with the same name)? The issue being the show most folks schedule is always a discrete time range (unless it is a manual recording), so would it not be possible (wishlist item?) for GBPVR to recognise you initially wanted to record the whole show, but it has simply shifted it's time slot?

Season recordings behave a little differently. After the EPG data has been retrieved, but before it is stored in the database, currently scheduled episodes of season recordings are removed from the database, then the listings are removed, then the new listings are saved followed by the rescheduling of any season recordings. In effect, individual episodes of a season recording should be correctly updated if the it's times change.

That's great (and I guess the expected) behaviour. I wonder if all those other folks seeing the same problem have it ONLY with one-off shows. I guess only they can answer that!

Cheers again,

k.

[sub]

However, (unless you have set a manual recording where you might, but unlikely, wish to record 1/2 a show), surely if you have committed to a complete EPG reload (in the config), you are already saying "OK, whatever show I scheduled" for that time slot has moved as a whole show, so I'd like GBPVR to record the next closest show (with the same name)? The issue being the show most folks schedule is always a discrete time range (unless it is a manual recording), so would it not be possible (wishlist item?) for GBPVR to recognise you initially wanted to record the whole show, but it has simply shifted it's time slot?

Maybe in a future release. Its not a change I'll be making at the moment. I've already got too much on my plate.

[garyeuph]

That's great (and I guess the expected) behaviour. I wonder if all those other folks seeing the same problem have it ONLY with one-off shows. I guess only they can answer that!

Cheers again,

k.

Unfortunatley, I get this even for shows that have NO recordings scheduled, either manual or scheduled.