Jump to content


Photo

merge requests for PLi's git


  • Please log in to reply
1748 replies to this topic

Re: merge requests for PLi's git #481 mworker

  • Senior Member
  • 51 posts

+2
Neutral

Posted 8 March 2014 - 23:21

These are the logs of my boxes.

Xtrend Et9000,Azbox Elte,Amiko Alien v2.

Attached Files



Re: merge requests for PLi's git #482 simon_ttp

  • Member
  • 7 posts

0
Neutral

Posted 9 March 2014 - 00:26

Please commit following update to encoding.conf in order to display properly polish EPG on TV DISCO channel (Hotbird):

15700 318 #Hotbird 13.0 Belgium Satellite Services - TV DISCO 

 found that other channels distributed on this transponder doesn't transmit EPG, so there are no compatibility issues.

 

It looks also that following entry is no longer needed and can be commented or removed:

12800 318 ISO6937 #Viacom ... MTV / VH1 Polska

 

Thanks a lot!


Edited by simon_ttp, 9 March 2014 - 00:26.


Re: merge requests for PLi's git #483 simon_ttp

  • Member
  • 7 posts

0
Neutral

Posted 9 March 2014 - 01:44

I just found one more transponder with polish EPG issue that require encoding.conf update:

700 318 #Hotbird 13.0 Cyfrowy Polsat



Re: merge requests for PLi's git #484 littlesat

  • PLi® Core member
  • 56,933 posts

+695
Excellent

Posted 9 March 2014 - 08:10

To avoid typos...can you post your complete encoding.conf here?

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


Re: merge requests for PLi's git #485 simon_ttp

  • Member
  • 7 posts

0
Neutral

Posted 9 March 2014 - 09:22

Sure. here it is:

#Fallback encoding when in dvb-text no encoding table is given
#Countycode ISO8859-X or ISO6937
ara ISO8859-6
tur ISO8859-9
gre ISO8859-7
pol ISO8859-2
rus ISO8859-5
bul ISO8859-5
tha ISO8859-11
cze ISO6937
ces ISO6937
slo ISO6937
slk ISO6937
#Sorry for that.. in DVB Spec this is the default behavior 
#when no other encoding is given in dvb-texts..
#but this breaks too much providers yet.. 
#so our default is ISO8859-1 without two char byte encoding
#So all transponders which needs this must be listed here
#TSID ONID
0x447 0x1 # Astra 19.2°E 12.304 H - UPC Direct 
0x427 0x1 # Astra 19.2°E 10.920 H - UPC Direct 
0x44b 0x1 # Astra 19.2°E 12.382 H - UPC Direct
0x4ff 0x1 # Astra 19.2°E 11.992 H - UPC Direct 
0x407 0x1 # Astra 19.2°E 11.671 H - UPC Direct 
0x436 0x1 # Astra 19.2°E 11.973 V - MTV Networks Europe
0x42a 0x1 # Astra 19.2°E 11.739 V - MTV Networks Europe
0xc23 0x3 # Astra 23.5°E 10.803 H - CS Link / SkyLink
0xc85 0x3 # Astra 23.5°E 11.797 H - CS Link / SkyLink
0xc89 0x3 # Astra 23.5°E 11.876 H - CS Link / SkyLink
0xc8f 0x3 # Astra 23.5°E 11.992 H - CS Link / SkyLink
0xc93 0x3 # Astra 23.5°E 12.070 H - CS Link / SkyLink
0xc95 0x3 # Astra 23.5°E 12.109 H - SkyLink
0xbc6 0x3 # Astra 23.5°E 12.525 V - CS Link / SkyLink
0xbc7 0x3 # Astra 23.5°E 12.565 H - SkyLink
200 318 #Hotbird Eutelsat (Eurosport)
300 318 #Hotbird Eutelsat (Eurosport, Animal Pl.HD)
400 318 #Hotbird 13.0 Cyfra+
700 318 #Hotbird 13.0 Cyfrowy Polsat
1000 318 #Hotbird 13.0 Grupa ITI
1100 318 #Hotbird 13.0 Cyfra+
1500 318 #Hotbird 13.0 Cyfra+
1600 318 #Hotbird 13.0 Cyfra+
2800 318 #Hotbird 13.0 MTV Networks (Comedy Central)
7400 113 #Hotbird 13.0 Cyfrowy Polsat
7800 113 #Hotbird 13.0 Cyfrowy Polsat
7900 113 #Hotbird 13.0 Cyfrowy Polsat
8100 113 #Hotbird 13.0 Universal (Cyfra+)
8100 318 #Hotbird 13.0 Eutelsat (Universal)
11000 318 #Hotbird 13.0 Cyfra+
11400 318 #Hotbird 13.0 Cyfra+
11600 318 #Hotbird 13.0 BBC HD, ITI
11700 318 #Hotbird 13.0 Eurosport2
11900 318 #Hotbird 13.0 Cyfra+
12200 318 #Hotbird 13.0 Disney Channel Polska and other
12800 318 #Hotbird 13.0 Viacom ... MTV / VH1 Polska
13000 318 #Hotbird 13.0 BBC Polska and other
13100 318 #Hotbird 13.0 Crime and Investigation
13200 113 #Hotbird 13.0 Cyfrowy Polsat
15700 318 #Hotbird 13.0 Belgium Satellite Services - TV DISCO
#Fallback encoding table for single transponders
#ISO6937 also enables two byte char encoding
#TSID ONID ISO8859-X
#12800 318 ISO6937 #Viacom ... MTV / VH1 Polska
20600 126 ISO8859-9 # Digital Platform 7°E
20700 126 ISO8859-9 # Digital Platform 7°E
20800 126 ISO8859-9 # Digital Platform 7°E
20900 126 ISO8859-9 # Digital Platform 7°E
21000 126 ISO8859-9 # Digital Platform 7°E
21100 126 ISO8859-9 # Digital Platform 7°E
41200 126 ISO8859-9 # Digital Platform 7°E
50100 126 ISO8859-9 # Digital Platform 7°E
50200 126 ISO8859-9 # Digital Platform 7°E
50300 126 ISO8859-9 # Digital Platform 7°E
50400 126 ISO8859-9 # Digital Platform 7°E
50500 126 ISO8859-9 # Digital Platform 7°E
50600 126 ISO8859-9 # Digital Platform 7°E
50700 126 ISO8859-9 # Digital Platform 7°E
50800 126 ISO8859-9 # Digital Platform 7°E
50900 126 ISO8859-9 # Digital Platform 7°E
51000 126 ISO8859-9 # Digital Platform 7°E 


Re: merge requests for PLi's git #486 littlesat

  • PLi® Core member
  • 56,933 posts

+695
Excellent

Posted 9 March 2014 - 09:24

And as attachment (zip it and then post it, see more reply options on bottom right)

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


Re: merge requests for PLi's git #487 simon_ttp

  • Member
  • 7 posts

0
Neutral

Posted 9 March 2014 - 12:19

zipped encoding.conf in attachment

Attached Files



Re: merge requests for PLi's git #488 littlesat

  • PLi® Core member
  • 56,933 posts

+695
Excellent

Posted 9 March 2014 - 12:22

I just did commit it...


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


Re: merge requests for PLi's git #489 mirakels

  • Forum Moderator
    PLi® Core member
  • 7,602 posts

+62
Good

Posted 14 March 2014 - 21:34

These are the logs of my boxes.

Xtrend Et9000,Azbox Elte,Amiko Alien v2.

Thanks mworker. The data in your logs for axbox en amiko seems a bit limited...

From the info given they need no extra entries in rc_models.cfg file as they only have a info/model file.


Geen wonder... Had slechts een dm7000, maar wel ook een rotor. eigenlijk al een tijdje ook een dm600 en dm7025. Maar nu kijkend met een et9000 en vuduo

Re: merge requests for PLi's git #490 Persian Prince

  • Senior Member
  • 1,982 posts

+247
Excellent

Posted 14 March 2014 - 23:07

a question about "CONFIG_DVB_FE_CUSTOMISE=y"

 

why do we need this ?


Open Vision sources: https://github.com/OpenVisionE2


Re: merge requests for PLi's git #491 Persian Prince

  • Senior Member
  • 1,982 posts

+247
Excellent

Posted 16 March 2014 - 00:06

is "config.subtitles.pango_subtitles_yellow" obsolete ?


Open Vision sources: https://github.com/OpenVisionE2


Re: merge requests for PLi's git #492 littlesat

  • PLi® Core member
  • 56,933 posts

+695
Excellent

Posted 16 March 2014 - 08:20

Why?


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


Re: merge requests for PLi's git #493 Persian Prince

  • Senior Member
  • 1,982 posts

+247
Excellent

Posted 16 March 2014 - 10:11

Why?

 

because i can't see it in your python sources anymore or maybe i did a bad search

 

and what about post #490 ? any idea ?


Edited by Persian Prince, 16 March 2014 - 10:12.

Open Vision sources: https://github.com/OpenVisionE2


Re: merge requests for PLi's git #494 Persian Prince

  • Senior Member
  • 1,982 posts

+247
Excellent

Posted 16 March 2014 - 12:06

regarding http://sourceforge.n...tDeviceSetup.py

 

the correct et support is this :

 

class RemoteControlType(Screen, ConfigListScreen):
	rcList = [
			("0", _("Default")),
			("4", _("DMM normal")), ("6", _("DMM advanced")),
			("13", "ET4000"), ("7", "ET5000 / ET6000"), ("5", "ET9000"), ("11", "ET9100 / ET9200"), ("9", "ET6500 / ET9500 / ET8000 / ET10000"),
			("14", "xp1000"),
			("8", "VU+"),
		]

	defaultRcList = [
			("et4000", 13),
			("et5000", 7),
			("et6000", 7),
			("et6500", 9),
			("et8000", 9),
			("et9000", 5),
			("et9100", 11),
			("et9200", 11),
			("et9500", 9),
			("et10000", 9),
			("xp1000", 14),
		]

instead of :

class RemoteControlType(Screen, ConfigListScreen):
	rcList = [
			("0", _("Default")),
			("4", _("DMM normal")), ("6", _("DMM advanced")),
			("11", "et9x00/6500"), ("7", "et5000/6000"), ("13", "et4000"), ("9", "et8000/et10000"),
			("14", "xp1000"),
			("8", "VU+"),
		]

	defaultRcList = [
			("et4000", 13),
			("et5000", 7),
			("et6000", 7),
			("et6500", 11),
			("et8000", 9),
			("et9000", 11),
			("et9200", 11),
			("et9500", 11),
			("et10000", 9),
			("xp1000", 14),
		]

fixed file attached


Open Vision sources: https://github.com/OpenVisionE2


Re: merge requests for PLi's git #495 Persian Prince

  • Senior Member
  • 1,982 posts

+247
Excellent

Posted 16 March 2014 - 12:34

also after ""KEY_VMODE": 227," in http://sourceforge.n.../tree/keyids.py

 

we should have ""KEY_SWITCHVIDEOMODE": 228," for et8/et10


Open Vision sources: https://github.com/OpenVisionE2


Re: merge requests for PLi's git #496 mirakels

  • Forum Moderator
    PLi® Core member
  • 7,602 posts

+62
Good

Posted 16 March 2014 - 12:55

@persionprince: About devicesetup: my et9000 has type 5 by default....


Geen wonder... Had slechts een dm7000, maar wel ook een rotor. eigenlijk al een tijdje ook een dm600 en dm7025. Maar nu kijkend met een et9000 en vuduo

Re: merge requests for PLi's git #497 Persian Prince

  • Senior Member
  • 1,982 posts

+247
Excellent

Posted 16 March 2014 - 13:16

ok so what's the problem in my message/file ?


Open Vision sources: https://github.com/OpenVisionE2


Re: merge requests for PLi's git #498 mirakels

  • Forum Moderator
    PLi® Core member
  • 7,602 posts

+62
Good

Posted 16 March 2014 - 13:37

ah I see, i reversed the two code blocks... sorry


Geen wonder... Had slechts een dm7000, maar wel ook een rotor. eigenlijk al een tijdje ook een dm600 en dm7025. Maar nu kijkend met een et9000 en vuduo

Re: merge requests for PLi's git #499 Persian Prince

  • Senior Member
  • 1,982 posts

+247
Excellent

Posted 16 March 2014 - 14:52

no problem :)

 

feel free to add what you want to your sources , we have them in our OE


Open Vision sources: https://github.com/OpenVisionE2


Re: merge requests for PLi's git #500 ims

  • PLi® Core member
  • 13,737 posts

+214
Excellent

Posted 16 March 2014 - 15:36

Why?

 

because i can't see it in your python sources anymore or maybe i did a bad search

it is used in cpp


Kdo nic nedělá, nic nezkazí!


12 user(s) are reading this topic

0 members, 12 guests, 0 anonymous users