Problems with Xmltv import

[WouterC]

Hi,

I have a liitle problem with the tv listings.

Here in Belgium, they have the annoying habbit to change the starting and end time of a show at the last moment. With the last moment I mean a few hours before the show starts.
Every night at 4AM I grab the xmltv listing for the next 7 days and import it in gbpvr. Every day at 4PM I grab the listing for only 1 day (today) to update the latest changes. This way I hope to avoid the problem.
But it isn't working. I get overlapping schedules.
I don't know if it's caused by the fact that at night it gets data for 7 days and during the day it only gets data for 1 day. It's obvious that I use the same xml file for the data.

I took some screenshots and attached it in a zipfile to my post.

Any help?

Thanks in advance

Wouter

[sub]

This is a known problem, that has been present since the start of the projects. Once a show is in the database - its never changed.

[jasjol]

is it possible to change this?

1) for example when updating EPG - the update replaces all EPG data with the sema name if it is NOT marked as recorded?

2) or by having an option that automatically first empty EPG (which leaves only those marked as recorded?)
and then add the new EPG?

(in case 2 you need to add for example 14 days every update of EPG - but it is very fast to update 14 days EPG so that should not be a problem)

[sub]

Maybe in a later release, it doesnt happen here oftens so it's not high on my priority list. Its not as straight forward as you might think, particularly if you've already scheduled recordings.

[bgowland]

Quote[/b] (jasjol @ Mar. 09 2005,17:24)]1) for example when updating EPG - the update replaces all EPG data with the sema name if it is NOT marked as recorded?

To clean up the EPG, the following commands work for me when run manually from the command line...

gbpvr -OnlyEmptyEPG
gbpvr -OnlyUpdateEPG

I do this manually when I spot too many "To Be Announced" slots in the EPG. I intend to start scheduling a batch file at some time after 5am each day (that's when my XMLTV grabber runs) to clean it up automatically. jimh has written a command line utility which will allow me to postpone the batch job if a recording is in progress, or due within a specified time, to prevent things getting messed up (see Community Announce,ents for RecStatus.exe).

The only way to fix the ghost recordings that I've found is to regularly check manually in 'Pending' then delete the duplicates and do the empty/update operation.

Cheers,
Brian

[jasjol]

Quote[/b] (bgowland @ Mar. 10 2005,03:37)]To clean up the EPG, the following commands work for me when run manually from the command line...

gbpvr -OnlyEmptyEPG
gbpvr -OnlyUpdateEPG

I did try to empty EPG via config for both of my capture sources - restarted GBPVR and the TV guide still shows info for programs. and ghost programs still there.

then I tried gbpvr -OnlyEmptyEPG, now in the TVguide ther is noting - totally blank, - so far so good.
But when I tried gbpvr -OnlyUpdateEPG the TV guide gets the EPG data but the Ghost listings still exists - and a recording for today disappeared - the reoccuring ones came back though.

bgowland - do you actually get rid of ghost listings?

what I mean with ghost listings is that I have 2 shows in the same channel of 24, one starts 0010 the other starts 0015 both are 1 hour.

Only the 0015 is present i the XMLTV file.

[bgowland]

Quote[/b] (jasjol @ Mar. 12 2005,17:45)]But when I tried gbpvr -OnlyUpdateEPG the TV guide gets the EPG data but the Ghost listings still exists - and a recording for today disappeared - the reoccuring ones came back though.

Ugh - sorry. I should have remembered that any one-off recordings will be cleared out with the emptying of the EPG. I don't have many one-off recordings but I normally make note of them before I clear the EPG.

Quote[/b] ]bgowland - do you actually get rid of ghost listings?

The only way to do it is to make a note of which reoccuring recordings are doing this, delete the recourring recording entry, then do the -OnlyEmptyEpgy etc. then re-create the reoccurring recording. It's a bit of a pain but it works.