8 replies to this topic

[rtzhjgg0]

@Milo & Rytec
During a day of zapping often the epg-file contains the EPG of unneeded providers. But we need only the EPG of providers we chose to import nightly, without the unwonted EPG/images/smiley/wink.gif

Is it possible to add this option to EPG-Import Configuration?
Delete old(existing) EPG before importing - yes/no

Thanks!

[MiLo]

And is it your intention that this option deletes all EPG data? (as if you did "init 4;rm /hdd/epg.dat/;init 3")

[rtzhjgg0]

Yes, same as manually delete of epg.dat

In this way the user can have a clean EPG with only the imported providers/images/smiley/wink.gif

[doglover]

This option could be usefull.

It certainly will make the need to use the init 4 / rm epg.dat / init 3 method redundand. If to resort very often to this, during testing of xmltv files.

Willy

[PaphosAL]

But hang on a minute- if you simply delete your epg.dat file, then try to retrieve epg, won't the script fail, with 'epg.dat not found' error?

Or is this aspect different in E2 to what I see in E1 with epg.db ?? In E1, OpenPLi always creates a new 80kb 'basic' epg.db after a reboot in the chosen storage folder on the mount, if none is found.

Hence my daily cron method of doing a similar thing (deleting epg.db on the mount, then rebooting, a few minutes before cron runs the daily epg download). Explained in more detail here:

http://www.pli-image...thread_id=14137

But it went down like a lead balloon, 0/10, LOL!

Cheers- AL

[doglover]

Dear Paphosal,

e2 and e1 are really different. The importer is not the same. Also how epg is stored is not the same on e1 and e2.

In e1 the epg is stored in epg.db, a sqlite database, and is read from there when needed.

In e2 epg is stored in memory. In order not to lose all the epg when you switch off the box, Gemini and OpenPli stores the epg as epg.dat, which is reloaded when the box is restarted. (maybe this is also the case iother images).
Now in images which do not have the Oudeis patch, the epg.dat is also used to import the epg. The importer creates a new epg.dat from the xmltv files. Enigma is restarted and the normal process of reading the epg.dat is performed. Now the new epg is stored internally in enigma. This proces normally eliminates the epg in memory. Except for the images with the CrossEPG patch where the epg.dat methos is also used, but this epg.dat is read into memory without eliminating the present epg.

However in images with the Oudeis patch (like OpenPli) the epg from the xmltv files is appended to the epg already in enigma.

So the need for deleting the old epg arises sometimes for images with the Oudeis and the Crossepg patch. Especially when testing new xmltv packages and when you f**cked up the epg, by f.i. leaving the EIT and/or MHW epg on, and have nice english epg replaced by some czech epg (no offence intended - just used as example) which you cannot read.

Willy

[PaphosAL]

Apologies, Willy- I didn't realize that EPG in E1 and E2 were two entirely different animals. Thankyou for taking the time to explain this in detail!!

Cheers- AL

[Robinson]

I only wanted to know what happens if there is a recording going when the plugin is about to clear the EPG and, I believe, restart Enigma2?

The recording would be damaged.

[doglover]

OpenPLi, never restarts the receiver when clearing or importing EPG.

So no problem here.

 

I do not know what happens on other images.

Except:  OpenVIX does not restart either

 

Willy