On Sun, 12 Dec 2010 16:19:00 +0100
Klaus Schmidinger <klaus.schmidin...@tvdr.de> wrote:

> On 09.12.2010 07:59, Steffen Barszus wrote:
> > On Wed, 08 Dec 2010 23:22:05 +0100
> > Klaus Schmidinger <klaus.schmidin...@tvdr.de> wrote:
> >> On 08.12.2010 20:25, Jochen Dolze wrote:
> >>> To be able using other epg sources with other event ids as from
> >>> the broadcaster. Today i cannot add 14 days of external epg
> >>> without patching.
> >>
> >> Why would you have to patch VDR for that?
> >> External event's by default have a "table id" if 0, which means
> >> they will never be overwritten by data from the transponder.
> > 
> > You will get duplicate EPG entries if the time doesn't match 
> Hmm, I see.
> So how about changing cEIT in such a way that it never overwrites
> any events in a schedule if the first existing event in that schedule
> has a table id of 0?

If we can be sure that between clre and adding the external epg no
event comes into vdr by cEIT, means it can be ensured that this holds
true for any stations external epg is used. 

On a side note to this, slightly OT: 
Thinking: What if a plugin could provide the EPG functionality for vdr ?

In the long run it might be more useful if a more advanced merge from
the different epgs source could happen at submission of the epg. 
The processing should happen in a seperate thread ( Having external epg
for 18 days sums up to approx. 70MB, where vdr runs into emergency
exit at the moment, if processed at once.) 
Current starting time from DVB might still be interesting, even if
external epg is a lot better.

Having epg in a DB (sqlite,mysql) might also be nice. 

vdr mailing list

Reply via email to