Jump to content


Photo

EPGImport latest changes: explanation


  • Please log in to reply
17 replies to this topic

#1 Pr2

  • PLi® Contributor
  • 2,719 posts

+111
Excellent

Posted 15 September 2018 - 23:43

Hi,
 
Here are a few explanation about the latest changes in EPGImport:
 
For IPTV:
 
You now need to match the service reference between the userbouquet and the channels.xml file.
So if your IPTV channel are properly added using the #SERVICE 4097:.... now in the channels.xml this MUST also be 4097!
 
 
LastUpdate.txt:
 
We have faced several times the following problem, Doglover/Rytec can no longer upload newest file to EPG mirror servers but servers still distribute obsolete EPG data files to client. Result was no EPG even if data was downloaded because data where obsolete.
 
To prevent this it was decide in accordance with Rytec/Doglover to add a control file:  LastUpdate.txt, this file must only be set with the last update date when all the files are properly uploaded to it. (date format is YYYY-mm-dd)
So if we have again a server in this bad state it will be rejected by the checkValidServer.
 
 
But people that define there own sources.xml file that point to there own server can decide not to use this check (LastUpdate.log) by adding the attribute  nocheck="1"
 
 
Be careful:
First implementation uses LastUpdate.log but a mirror was unable to provide .log file so we need to change to LastUpdate.txt
 
 
IPTV or custom sources.xml: file custom.channels.xml
 
When defining sources.xml file it was mandatory to define again all the servers URL.
 
So for people that use IPTV and create there own sources.xml file and also channels.xml file this create a double donwload from EPG data mirror.
 
To avoid this an ease the creation of personal .channels.xml files it is now possible to just create one file:
 
custom.channels.xml
 
You include in this file all you self created service reference (the same as in your bouquets files).
Just place this file into /etc/epgimport/ folder, it will be readed and processed for every downloaded EPG data file.
 
 No more case sensitive for channel id into channels.xml file:
 
To ease maintainer life Doglove/Rytec it has been decided to have the channel id=" "  no more case sensitive.
 
So TF1.fr tf1.fr Tf1.fr will now be considered as the same channel for EPG data sources.
 
 
Pr2

Edited by Pr2, 16 September 2018 - 18:52.

NO SUPPORT by PM, it is a forum make your question public so everybody can benefit from the question/answer.

If you think that my answer helps you, you can press the up arrow in bottom right the answer.

 

Octagon SF-4008: Hotbird 13.0E, Astra 19.2E, Eutelsat5A 5.0W (+DVB-C)
VU+ Solo 4K: 2*DVB-S2 + 2*DVB-C/T/T2 (used in DVB-C)
Zgemma H5: 1*DVB-S2 + 1*DVB-C

Zgemma H7C: 1*DVB-S2 + 2*DVB-C


Re: EPGImport latest changes: explanation #2 Abu Baniaz

  • Senior Member
  • 656 posts

+16
Neutral

Posted 15 September 2018 - 23:53

Can the service type be omitted or treated the same whether 1, 19, 4097, 5001, 5002?



Re: EPGImport latest changes: explanation #3 doglover

  • Rytec EPG Team
  • 11,840 posts

+335
Excellent

Posted 16 September 2018 - 08:18

Can the service type be omitted or treated the same whether 1, 19, 4097, 5001, 5002?

 

 

Can you explain this a bit more pls.

I am not sure, I can answer this.

 

Willy


~~Rytec Team~~
Xtrend ET6000 OpenPli (used as mediaplayer)
Mutant HD2400 OpenPli
Vu+ Duo OpenPli (backup)

Synology NAS

Sat: 13E, 19.2E, 23.5E and 28.2E
*Pli/Rytec EPG POWERED*


Re: EPGImport latest changes: explanation #4 Pr2

  • PLi® Contributor
  • 2,719 posts

+111
Excellent

Posted 16 September 2018 - 08:57

Can the service type be omitted or treated the same whether 1, 19, 4097, 5001, 5002?

 

I understand your question, this needs to be checked in code and tested.


NO SUPPORT by PM, it is a forum make your question public so everybody can benefit from the question/answer.

If you think that my answer helps you, you can press the up arrow in bottom right the answer.

 

Octagon SF-4008: Hotbird 13.0E, Astra 19.2E, Eutelsat5A 5.0W (+DVB-C)
VU+ Solo 4K: 2*DVB-S2 + 2*DVB-C/T/T2 (used in DVB-C)
Zgemma H5: 1*DVB-S2 + 1*DVB-C

Zgemma H7C: 1*DVB-S2 + 2*DVB-C


Re: EPGImport latest changes: explanation #5 Robinson

  • Senior Member
  • 2,371 posts

+26
Good

Posted 16 September 2018 - 10:34

I think it would be good to update pinned topics when the new improvements have been finalized.

Thanks. :)


ET9000, OpenPLi 4.0, 75E - 30W

HD51, OpenPLi 6.1, 13E, 19E


Re: EPGImport latest changes: explanation #6 Pr2

  • PLi® Contributor
  • 2,719 posts

+111
Excellent

Posted 16 September 2018 - 12:15

For people concerned with fake SERVICE 1: for IPTV please test this:

 

https://github.com/p...e38ce66ba19acaf

 

I will wait for your feedback before creating the Pull Request.

 

Pr2


NO SUPPORT by PM, it is a forum make your question public so everybody can benefit from the question/answer.

If you think that my answer helps you, you can press the up arrow in bottom right the answer.

 

Octagon SF-4008: Hotbird 13.0E, Astra 19.2E, Eutelsat5A 5.0W (+DVB-C)
VU+ Solo 4K: 2*DVB-S2 + 2*DVB-C/T/T2 (used in DVB-C)
Zgemma H5: 1*DVB-S2 + 1*DVB-C

Zgemma H7C: 1*DVB-S2 + 2*DVB-C


Re: EPGImport latest changes: explanation #7 Pr2

  • PLi® Contributor
  • 2,719 posts

+111
Excellent

Posted 16 September 2018 - 18:58

Be careful: a mirror was unable to return file with .log extension, so we decide to change the file from LastUpdate.log to LastUpdate.txt.

 

Sorry for this late change for people using there own EPG data server please update the creation of your LastUpdate.txt file accordingly or use the nocheck="1" option.


NO SUPPORT by PM, it is a forum make your question public so everybody can benefit from the question/answer.

If you think that my answer helps you, you can press the up arrow in bottom right the answer.

 

Octagon SF-4008: Hotbird 13.0E, Astra 19.2E, Eutelsat5A 5.0W (+DVB-C)
VU+ Solo 4K: 2*DVB-S2 + 2*DVB-C/T/T2 (used in DVB-C)
Zgemma H5: 1*DVB-S2 + 1*DVB-C

Zgemma H7C: 1*DVB-S2 + 2*DVB-C


Re: EPGImport latest changes: explanation #8 Abu Baniaz

  • Senior Member
  • 656 posts

+16
Neutral

Posted 16 September 2018 - 21:05

 

Can the service type be omitted or treated the same whether 1, 19, 4097, 5001, 5002?

 

 

Can you explain this a bit more pls.

I am not sure, I can answer this.

 

Willy

 

 

For picons, we allow all service types to work with a picon. Whether 1, 19, 4097, 5001, 5002. I was hoping the same could be done for EPG.



Re: EPGImport latest changes: explanation #9 Abu Baniaz

  • Senior Member
  • 656 posts

+16
Neutral

Posted 16 September 2018 - 21:43

It looks like I mixed up the terminology. The point I was trying to make is below

 

https://github.com/O...icon.py#L78:L80



Re: EPGImport latest changes: explanation #10 humaxboy

  • Senior Member
  • 50 posts

+1
Neutral

Posted 17 September 2018 - 20:45

Guys what i am doing wrong ? still using my rytec.sources.xml and channels.xml.

Sources can be seen (import.jpg), checking Manual brings error (import2.jpg), log shows that (import3.jpg).

Attached Files



Re: EPGImport latest changes: explanation #11 doglover

  • Rytec EPG Team
  • 11,840 posts

+335
Excellent

Posted Yesterday, 06:53

I have no idea what is going wrong.

However, it seems that you have a custom made sources file.  The one on the screenshot is definitely not the one from rytec.

So in that file you could have everything changed.  No idea what.

 

Can you show us the files you made?

 

Willy


~~Rytec Team~~
Xtrend ET6000 OpenPli (used as mediaplayer)
Mutant HD2400 OpenPli
Vu+ Duo OpenPli (backup)

Synology NAS

Sat: 13E, 19.2E, 23.5E and 28.2E
*Pli/Rytec EPG POWERED*


Re: EPGImport latest changes: explanation #12 Abu Baniaz

  • Senior Member
  • 656 posts

+16
Neutral

Posted Yesterday, 13:04

That is a picture from OpenATV. The OE-A fork is broken because of the IP6 checks.

Sent from my Moto G (5S) using Forum Fiend v1.3.3.

Re: EPGImport latest changes: explanation #13 humaxboy

  • Senior Member
  • 50 posts

+1
Neutral

Posted Yesterday, 13:38

@doglover - yes I have custom made sources file

@abu Baniaz - yes, that is OpenAtv..so it is their fault ? i just need simple yes or no...



Re: EPGImport latest changes: explanation #14 dsayers2016

  • Member
  • 4 posts

0
Neutral

Posted Yesterday, 19:04

Probably best posting on OpenATV forum. Issue has been opened here https://github.com/o...mport/issues/30

It's been worked on

Re: EPGImport latest changes: explanation #15 Pr2

  • PLi® Contributor
  • 2,719 posts

+111
Excellent

Posted Yesterday, 20:12

The change are made are for EPGImport this one is used only by OpenPLi  from EPGImport there is a fork called XMLTVImport which is used by OE-Alliance images (check dsayers2016 provided link).

So someone port the change I made in EPGImport into XMLTVImport but this porting cause troubles, because XMLTVImport implement a legacy IPv6 download that doesn't work properly.

 

So problem is on the OE-Alliance side, not in OpenPLi one.


NO SUPPORT by PM, it is a forum make your question public so everybody can benefit from the question/answer.

If you think that my answer helps you, you can press the up arrow in bottom right the answer.

 

Octagon SF-4008: Hotbird 13.0E, Astra 19.2E, Eutelsat5A 5.0W (+DVB-C)
VU+ Solo 4K: 2*DVB-S2 + 2*DVB-C/T/T2 (used in DVB-C)
Zgemma H5: 1*DVB-S2 + 1*DVB-C

Zgemma H7C: 1*DVB-S2 + 2*DVB-C


Re: EPGImport latest changes: explanation #16 Rob van der Does

  • Senior Member
  • 7,587 posts

+175
Excellent

Posted Today, 04:12

Correct.

And that ported change has now been reverted.



Re: EPGImport latest changes: explanation #17 Pr2

  • PLi® Contributor
  • 2,719 posts

+111
Excellent

Posted Today, 12:33

Yes funny solution instead a tackling down the bug in the IPv6 implementation.


NO SUPPORT by PM, it is a forum make your question public so everybody can benefit from the question/answer.

If you think that my answer helps you, you can press the up arrow in bottom right the answer.

 

Octagon SF-4008: Hotbird 13.0E, Astra 19.2E, Eutelsat5A 5.0W (+DVB-C)
VU+ Solo 4K: 2*DVB-S2 + 2*DVB-C/T/T2 (used in DVB-C)
Zgemma H5: 1*DVB-S2 + 1*DVB-C

Zgemma H7C: 1*DVB-S2 + 2*DVB-C


Re: EPGImport latest changes: explanation #18 Rob van der Does

  • Senior Member
  • 7,587 posts

+175
Excellent

Posted Today, 13:21

Indeed :(




1 user(s) are reading this topic

1 members, 0 guests, 0 anonymous users