XMLTV giving recording times 10 minutes early - and then the correct time too!!!!!

[jonmck]

I have lastest GBPVR and use UK Radio Times xml grabber for my listings.

It wokrs perfectly, but every Saturday (and only Saturday) I get teh following lisitings...

11.20 - 1200 Popworld
11.30 - 1200 Popworld

And so on for nearly all the programmes during the day. I have tried using the xmltv DOS program, but it does the same . I have unistalled and put its all back together again, but it still goes mad on a Saturday.

It obviosuly makes recording very hard - any one else found this? Any advice?

[birty]

this is probably due to the guide not being emptied before new listings are imported, this means that if a schedule change takes place then you get programs from both the old and new schedules

[jonmck]

Surely you don't havwe to empty EPG before updating the EPG - you would lose all your recordings?

[jonmck]

Surely you don't havew to empty EPG before you can update it? Would I not lose all my recordings?

[bgowland]

The problem occurs because once a programme is entered into the gbpvr database, it isn't removed again. This means that if the TV company reschedule it, the new timeslot in the XML file is treated by gbpvr as a different programme and gets added without removing the first. This can happen indefinately - I've seen four instances of programmes although just two are most common.

Emptying the EPG won't lose existing recordings or season recording entries but it will, I think, lose pending one-off recordings - not sure about pending recordings that have been set with manual timeslot info.

If you have more than one cap. source that use the same XMLTV file, using the Empty EPG button on the cap. source page won't fix it unless you do this for each cap. source. The easier way is the command-lines...

gbpvr -onlyemptyepg
gbpvr -onlyupdateepg

Remember, I 'think' anything set as a 'Record Once' recording will be lost but Season Recordings will be rebuilt.

I've written an EPG 'scrubber' to clean out anything which doesn't match an entry in the XMLTV file - I haven't yet tested it on a 'live' gbpvr.mdb so I'm not prepared to release it to the public in case it trashes the database. I'll try and get it tidied up and tested in the near future (hmmm, said that before ).

Cheers,
Brian

[bgowland]

Remember, I 'think' anything set as a 'Record Once' recording will be lost...

Nah, sorry - talking out of my ear. Tested this and a 'Run once' recording I have pending wasn't touched. I should've known that. :o

[MaBo]

If you start gbpvr from the command line with the emptyepg(only) switch, scheduled recordings will not be cleared. I do this every day. However, if you press the empty epg button in the config app, you WILL lose any scheduled recordings. This difference used to be called a bug, but I prefer to call it a feature

Greetz,
MaBo

[stefan]

If you start gbpvr from the command line with the emptyepg(only) switch, scheduled recordings will not be cleared. I do this every day.

Is this true? I thought I would be able to do an -emptyEPGOnly, and then immediately afterwards do an update of the epg, and in that way accomplish a refresh of the recordings that have been moved (an update of the epg forces the recordings to get readded, right?)

[pknighton67]

Emptying the EPG won't lose existing recordings or season recording entries but <snip>.

<snip>The easier way is the command-lines...

gbpvr -onlyemptyepg
gbpvr -onlyupdateepg

I've written an EPG 'scrubber' to clean out anything which doesn't match an entry in the XMLTV file - I haven't yet tested it on a 'live' gbpvr.mdb so I'm not prepared to release it to the public in case it trashes the database. I'll try and get it tidied up and tested in the near future (hmmm, said that before ).

Cheers,
Brian

Hi Brian,

1. I would be willing to test your "EPG 'Scrubber'" utility as I am regularly suffering this problem.

Could I please have a copy with instructions to test this ?


2. It is true that scheduled recordings persist - whether they are excluded during a "-onlyemptyEPG" operation, or simply re-added after it, I don't know.

My particular problem here is that I have reoccurring scheduled recordings on items that are sometimes rescheduled in time, e.g. "Farscape".

So I find myself with items automatically marked for recording both in the original timeslot and the revised timeslot. As they are marked for recording, they are not removed by a "-onlyemptyEPG".

I have even tried to deleted such recordings (see GBPVR/Recordings/Reoccurring), then do a "gbpvr -onlyemptyEPG" & a "gbpvr -updateEPG", but the original (now incorrect) timeslot persisted.

I know I can overcome this by doing a Empty EPG operation (the one from Configure utility, not "gbpvr -onlyemptyEPG"), but then that means I would have to re-enter all my scheduled recordings all over again.

Your utility to purge EPG items not present in the XMLTV file seems a sensible solution.

Any other solutions welcome too, e.g. a utility to import/export all details of your one-off/reoccurring scheduled recordings - those in the future (not the meta info of past recordings already done, as available in the Config utility).

Thanks
Paul Knighton

[bgowland]

Hi Paul,

I'll be ready to let it loose in the next day or so. I'll post something up on the Community Announcements forum asking for beta testers. It's working OK for me so far - it identifies all my invalid pending recordings and hasn't trashed my mdb (yet!).

Cheers,
Brian