Springen naar inhoud


Foto

Possibility to set custom pid for parsing epg data


  • Please log in to reply
Er zijn 8 reacties in dit onderwerp

#1 Dimitrij

  • PLi® Core member
  • 10047 berichten

+339
Excellent

Geplaatst op 9 maart 2016 - 08:55



This is very useful if a transponder epg be filed in 2 or more different pids or use non stardart one.
For example, the platform Dolce sent epg data on Romanian language on PID 0x12 and Bulgarian and Serbian on PID 0x12b. If create reader for PID 0x12b, some events are Romanian language, others are Bulgarian because of PID 0x12 no information about the language of epg data.
Usage:
Create a file "/etc/enigma2/epgpids.cusom" and fill in the format

Orbital position | TSID | ONID | Custom pid to use

The values ​​can be decimal or hexadecimal (0x ...), and combined
For orbital position using integers where 1 means 0,1 ° (19,2°E -> 192)
For orbital position can be used as negative numbers (0,8°W -> -8 or 3592)

examples:
390 17 28 299 # 39°E 12688V, epgpid to use: 299
0x186 0x11 0x1c 0x12b # Same, but in hexadecimal format
390 17 28 0x12b # Or combined

 
I ask your support for adding a patch in the image.

 


GigaBlue UHD Quad 4K /Lunix3-4K/Solo 4K


Re: Possibility to set custom pid for parsing epg data #2 littlesat

  • PLi® Core member
  • 56450 berichten

+693
Excellent

Geplaatst op 9 maart 2016 - 09:36

I do not like the format of the epgpid.custom and as far I can see on each zap this file will be parsed...(This is I think we should not do... but please note me when I make a mistake. note that I just looked at the patch)

 

 

I understand it works.... But I think this change needs more smarter 'finetuning...'

 

Consider this...

 

In E2 we already have a EPG language selection...

 

Therefor I think it would be better to somehow add EPG language/PID 'table' in the transponder section of the lamedb... and then arrange that E2 will change to the PID of the selected EPG language.

 

As it is created now it is not flexible and static and a user needs to put it's own epgpid,custom file

 

Or at least we have a lame_epgpid_db file or so.... with 

 

Orbital position | TSID | ONID | LANGUAGE_CODE | Custom pid to use

 

and the language is choosen by EPG prefered language... (this makes it independed from existing lamedb)...

 

And then not parse it any time... store the table somewhere statically in E2...


WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: Possibility to set custom pid for parsing epg data #3 Dimitrij

  • PLi® Core member
  • 10047 berichten

+339
Excellent

Geplaatst op 9 maart 2016 - 12:45

The file is read once when starting E2.
And then stored in E2.

 

Same implemented a similar feature(ONID-based blacklist function):

https://github.com/O...8a83e79265799e1


Veranderd door Dimitrij, 9 maart 2016 - 12:46

GigaBlue UHD Quad 4K /Lunix3-4K/Solo 4K


Re: Possibility to set custom pid for parsing epg data #4 Cofybreak

  • Senior Member
  • 115 berichten

0
Neutral

Geplaatst op 10 maart 2016 - 18:46

The idea of this pach is not to solve the problem with the right choice of language for EPG data.

Its aim is to eliminate the need to write a separate reader for every conceivable pid that an operator chooses to use for send EPG.

This patch makes unnecessary 3 current readers - Viasat, Netmed and Virgin.



Re: Possibility to set custom pid for parsing epg data #5 fen

  • Senior Member
  • 31 berichten

0
Neutral

Geplaatst op 15 maart 2016 - 14:41

@Cofybreak

 

Thx!

openatv 5.2

 

7to48rW.jpg



Re: Possibility to set custom pid for parsing epg data #6 littlesat

  • PLi® Core member
  • 56450 berichten

+693
Excellent

Geplaatst op 15 maart 2016 - 16:16

OpenATV did indeed merged everything that is not "perfect" yet...;)

 

But for now I also just merged it...

 

But please consider to add my comments to this patch that will make it just perfect.... Just list all PIDs with language code in that specific config file and arrange the EPG language configs set the correct language.... 

 

And in addition reading the last comments I'm still hoping it was understood...


Veranderd door littlesat, 15 maart 2016 - 16:23

WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W


Re: Possibility to set custom pid for parsing epg data #7 Dimitrij

  • PLi® Core member
  • 10047 berichten

+339
Excellent

Geplaatst op 16 maart 2016 - 19:34

Please help...

1)
0003:01680000:0136:00fd:1:0
Союз
p:TricolorTV,c:00012f,c:010195,c:03012f,C:0e00

 

2)
29e3:00820000:3cf0:013e:1:0
Soyuz
p:GLOBECAST,c:0000f3,c:0100fd,c:0300f3

 

1) is EPG

2)not EPG

channel is the same, how to add EPG?


GigaBlue UHD Quad 4K /Lunix3-4K/Solo 4K


Re: Possibility to set custom pid for parsing epg data #8 Cofybreak

  • Senior Member
  • 115 berichten

0
Neutral

Geplaatst op 17 maart 2016 - 17:03

OpenATV did indeed merged everything that is not "perfect" yet... ;)

 

But for now I also just merged it...

 

But please consider to add my comments to this patch that will make it just perfect.... Just list all PIDs with language code in that specific config file and arrange the EPG language configs set the correct language.... 

 

And in addition reading the last comments I'm still hoping it was understood...

 

But users will not have the possibility to specify the correct pid.
However, I will think about it.

And thank you for adding this path.

 

Please help...

1)
0003:01680000:0136:00fd:1:0
Союз
p:TricolorTV,c:00012f,c:010195,c:03012f,C:0e00

 

2)
29e3:00820000:3cf0:013e:1:0
Soyuz
p:GLOBECAST,c:0000f3,c:0100fd,c:0300f3

 

1) is EPG

2)not EPG

channel is the same, how to add EPG?

 

This can`t help if no epg data on the transponder.

If you wish to copy epg data from one channel to another - use plugin Buyukbang Panel from feeds.



Re: Possibility to set custom pid for parsing epg data #9 Taapat

  • PLi® Core member
  • 2345 berichten

+121
Excellent

Geplaatst op 17 maart 2016 - 21:56

It seems to me that in your changes is small error: https://github.com/O...nigma2/pull/229

 

I'm surprised that it does not affect the work on the mipsel, but on sh4 it breaks epg in the channel selection.

 

I have read that on sh4 in openatv is exactly the same problem with epg in channel selection.


Veranderd door Taapat, 17 maart 2016 - 21:59



1 gebruiker(s) lezen dit onderwerp

0 leden, 1 bezoekers, 0 anonieme gebruikers