104 replies to this topic

[pluizebol]

For people too lazy ....

 

I think (hope) that you meant "for people not knowing where to search"

[Lost in Space]

I didn't know that we have political correctness day ... but yes

[doglover]

My Mod is fully downward compatible with the current EPG Importer code as in case of DreamOS it uses an epgdb.py and for the old enigma2 it stays with epgdat.py

 

epgdb.py is just 2 pages of code, so it is NOTHING to be scared of, as using a database makes the whole live much easier and flexible then the 10 year old epg.dat which is fully of bugs and patches needed to keep it running.

 

I did also some minor enhancements to the existing code like kicking out the idiotic way to check if a channel is available by duoing a dummy recording and I added also the possibility to extract EPG Language form the xmls , as this is also a new feature that epg Database supports.

 

All this was done without doing harm to the existing code - it still runs for example in an OpenATV Image on my dm7080 and dm820. But this would need some testing to be confirmed.

 

 

Most people do not care about all of this.  They just wanted it to work.

 

Is this the thread?

http://www.dream-multimedia-tv.de/board/index.php?page=Thread&threadID=19447&pageNo=2

But is it really necessary to insult users which are not that knowledgeable in net searches. 

And yes some features could be better programmed.  But if we are all co-operating things will move faster as when we trying to insult each other.

So work together and solve the problems, instead of spending time and efforts on blaming each other.

 

Willy

[doglover]

I have added the threads url to our FAQ's

 

Willy

[Lost in Space]

I'm not blaming you or anybody but the plugin has more try:/except: as I've ever seen - and belive me as I'm en expert in ugly code

 

But yes this is the original thread but it is mainly in German.

 

The *.debs are at the end of the thread but the necessary infos from the DMM devs are on the first 5 pages if I remember right.

 

If you or the users have further questions feel free to ask there or in OoZooN's board - which would be this Thread:

 

http://www.oozoon-bo...27990#post27990

 

But I'm always unsure how tolerant this board is to threads to others ....

Edited by gutemine, 4 January 2015 - 13:39.

[pluizebol]

I didn't know that we have political correctness day ... but yes

I am sure that you meant politeness instead of political.

[doglover]

Also this thread is in German.  Most of the users are not that fluent in German, contrary what German citizens seems to believe.  So these people end up here.

 

And I do not know either how this ref to another board is to be treated here.

But, these threads are about the workings of the XMLTV plug-in on the OE2.2 images.  Which has nothing to do with OpenPli.

So if there are questions about it, the discussion belongs on the other boards.  So at least we can refer to it, and help people find the way.

 

Willy

Edited by doglover, 4 January 2015 - 13:45.

[Lost in Space]

Well we all have to take the clientel we get ... somehow ...

 

PS: At OoZooN I posted also *.ipks if you want to test it on your non-DreamOS boxes or on old Dreamboxes not capable of running OE2.2, just if you want to verify that my enhancements didn't do any harm

Edited by gutemine, 4 January 2015 - 13:48.

[pluizebol]

I think that I solved my problem as follows.

 

Since I use only the XMLTV EPG

Since I do a daily import of EPG with XMLTV

I think that I do not need the file epg.dat and I deleted it from my HDD

 

As long as I do not restart Enigma2, the EPG.dat file is not created again.

This way I don't have old EPG data and thus no more double events.

 

Am I right about this ?

Edited by pluizebol, 5 January 2015 - 10:20.

[doglover]

No.

 

The import will add them daily.

 

Willy

[MiLo]

Everyone is focused at "removing all EGP will solve my problem". If I understand correctly, "the problem" here is simply that overlapping programs don't replace eachother properly, so you end up with duplicate entries if a program changes start time by a few minutes.

Killing all EPG is a rather drastic measure to fix that, and it won't even solve the problem.

The XMLTV data is processed like any other EPG data.

It would make more sense to solve the problem: If a new entry overlaps an existing entry, remove that old entry. I suspect the current implementation only relaces events that have the exact same start time.

[doglover]

It would make more sense to solve the problem: If a new entry overlaps an existing entry, remove that old entry. I suspect the current implementation only relaces events that have the exact same start time.

 

 

Yes.

The XMLTV file does not contain overlapping entries. But when the starting time is not exactly the same the old entry is overwritten in the box.

 

Killing all EPG is a rather drastic measure to fix that

 

 

Yes it is a drastic measure, but the only one if you cannot live with a few double entries.

 

Willy

[pluizebol]

OK

 

Maybe this is not the right place to post my question - sorry for that on beforehand.

 

Is there a programmer amongst us who can write an application/extension to clear the EPG following a programmable recurring time.

 

Let me explain :

 

If I would be able

- to clear the EPG every morning at 08:00 with the new application/extension

- and do a daily XMLTV EPG import at 08:15 (which I already do)

The problem would be solved

Edited by pluizebol, 5 January 2015 - 13:22.

[littlesat]

That is a work-a-round... I suggest it is better to find a way to solve the real issue...
In row 598 in epgcache.cpp there exists an overlapping check and as far I can see it does not check for each epg type...

Edited by littlesat, 5 January 2015 - 14:19.

[MiLo]

It would make more sense to solve the problem: If a new entry overlaps an existing entry, remove that old entry. I suspect the current implementation only relaces events that have the exact same start time.

 
Yes.
The XMLTV file does not contain overlapping entries. But when the starting time is not exactly the same the old entry is overwritten in the box.

I think you meant to write "when the starting time is not exactly the same the old entry is not overwritten in the box"?

[doglover]

That is a work-a-round... I suggest it is better to find a way to solve the real issue...

 

That is exactly what is being asked.  However is not good stating the obvious and doing nothing.

The answer to this problem seems to be deeply embedded in enigma2, and the real solution can only be given by dev's of enigma2.  It is not good saying do it yourself, because this is way above the head of most amateur programmers who can write a bit of spaghetti code (to which I count myself).

 

Willy

[doglover]

 

 

It would make more sense to solve the problem: If a new entry overlaps an existing entry, remove that old entry. I suspect the current implementation only relaces events that have the exact same start time.

 
Yes.
The XMLTV file does not contain overlapping entries. But when the starting time is not exactly the same the old entry is overwritten in the box.

 

I think you meant to write "when the starting time is not exactly the same the old entry is not overwritten in the box"?

 

 

Milo, exactly.  Typo.

However in this case very severe, because suddenly the sentence means the complete opposite as supposed to.

 

Willy

[doglover]

In enigma1 there was the SQlite (an OpenPli development) database for the EPG.

Could this be a starting point for the EPG rewrite?

 

Willy

[WanWizard]

The problem is not where the data is stored (preferably an external DB like we introduced in E1, yes), but the logic around it that needs a complete rewrite.

[doglover]

The problem is not where the data is stored (preferably an external DB like we introduced in E1, yes), but the logic around it that needs a complete rewrite.

 

I understand, hence my remark.  This not something anybody can achieve, except for the dev's

 

Willy