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 #461 christophecvr

  • Senior Member
  • 3,131 posts

+140
Excellent

Posted 27 February 2014 - 12:50

You can omit the 13, enum numbering continues after the 12.
But I think we have to wait for betacentauri's comments, he knows the exact reasoning behind the 12, and he can tell you whether 13 is a good idea (or perhaps we should skip even more values to avoid conflicts)

 

Thank's I was not shure what it would have done whitout the =13 behind.

 

But in the mean time I already did experiment and tested with the cDDPPID=13

 

vuduo2 ok also after reboot channel audio stream setting is retained selected and works.

 

For that I have here the patch 3

 

Now it's just waiting on betacentauri's comments if it's ok the 2 patch or the three posted here.

Attached Files



Re: merge requests for PLi's git #462 betacentauri

  • PLi® Core member
  • 7,185 posts

+323
Excellent

Posted 27 February 2014 - 16:39

Thank's I was not shure what it would have done whitout the =13 behind.

 

But in the mean time I already did experiment and tested with the cDDPPID=13

 

vuduo2 ok also after reboot channel audio stream setting is retained selected and works.

 

For that I have here the patch 3

 

Now it's just waiting on betacentauri's comments if it's ok the 2 patch or the three posted here.

 

Version 3 of the patch looks good (I didn't review the whole patch. Only the enum). As pieterg already said the "=13" is not necessary. But it's also no error.

 

Yes, there was a reason why 11 should not be used. Here is the discussion about it:

http://openpli.org/f...db/#entry399570

In short: Dreamboxes use 11 and if we also use it with another meaning, it's not possible for tools to support dreambox images and OpenPli based images at the same time.


Edited by betacentauri, 27 February 2014 - 16:40.

Xtrend ET-9200, ET-8000, ET-10000, OpenPliPC on Ubuntu 12.04

Re: merge requests for PLi's git #463 pieterg

  • PLi® Core member
  • 32,766 posts

+245
Excellent

Posted 27 February 2014 - 17:09

thx, applied (minus the '= 13')

Re: merge requests for PLi's git #464 christophecvr

  • Senior Member
  • 3,131 posts

+140
Excellent

Posted 27 February 2014 - 17:53

Thank's I now make a build for my two boxes from scratch. To check all (for my dm8000 I wel add the extra decoder.cpp patch off athoik)



Re: merge requests for PLi's git #465 theparasol

  • Senior Member
  • 4,157 posts

+198
Excellent

Posted 27 February 2014 - 17:54

Next time better make a comment in the source?
Avoids such situations

@Camping: ZGemma H.2S, Technisat Multytenne 4-in-1 @Home: Edision Mini 4K, Wave Frontier T55, EMP Centauri EMP DiSEqC 8/1 switch, 4x Inverto Ultra Black single LNB


Re: merge requests for PLi's git #466 christophecvr

  • Senior Member
  • 3,131 posts

+140
Excellent

Posted 27 February 2014 - 18:01

Next time better make a comment in the source?
Avoids such situations

What do You mean ?



Re: merge requests for PLi's git #467 theparasol

  • Senior Member
  • 4,157 posts

+198
Excellent

Posted 27 February 2014 - 18:36

If something is not tot be used:

*/ dont use xxx for compatbility with yyyyy */

@Camping: ZGemma H.2S, Technisat Multytenne 4-in-1 @Home: Edision Mini 4K, Wave Frontier T55, EMP Centauri EMP DiSEqC 8/1 switch, 4x Inverto Ultra Black single LNB


Re: merge requests for PLi's git #468 christophecvr

  • Senior Member
  • 3,131 posts

+140
Excellent

Posted 27 February 2014 - 18:52

If something is not tot be used:

*/ dont use xxx for compatbility with yyyyy */

Yes that's I nice idea.



Re: merge requests for PLi's git #469 WanWizard

  • PLi® Core member
  • 70,219 posts

+1,798
Excellent

Posted 27 February 2014 - 19:04

What is this? Documentation? In Enigma? Now that is something new.... :D :P


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: merge requests for PLi's git #470 christophecvr

  • Senior Member
  • 3,131 posts

+140
Excellent

Posted 28 February 2014 - 10:28

All tests done ac3+ caching is now working perfect on my vuduo2 (basic pli4)

and on dm8000 also 100 % perfect with the ac3+ by pass patch applied to enigma2.



Re: merge requests for PLi's git #471 dhwz

  • Senior Member
  • 227 posts

+20
Neutral

Posted 28 February 2014 - 16:00

thx for keeping compatibility (at least partially)  ;)

c:13 will also be added to the upcoming dreamboxEDIT release.



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

  • PLi® Core member
  • 57,062 posts

+698
Excellent

Posted 28 February 2014 - 16:22

(at least partially)

Is there still an incompatebility?


Edited by littlesat, 28 February 2014 - 16:22.

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


Re: merge requests for PLi's git #473 christophecvr

  • Senior Member
  • 3,131 posts

+140
Excellent

Posted 28 February 2014 - 18:39

(at least partially)

Is there still an incompatebility?

I think he means the ac3+ by pass with partially. :P

 

Just one question.

 

I noticed it would be A nice thing to also have the choice into the menu in Dutch it is called Automatische taalkeuzeselectie gues Automatic Languageselcetion in English.

To have by ac3 preference now it's no or yes,

 

But modifie it into (I will now only show the dutch part as I do have ducth setup)

 Ac3 voorkeur                                            nee/ja (as choice)

Ac3 of Ac3+(ddp) voorkeur                      nee/ac3/ddp  (as choice) ddp is the ec3+ stream.

 

I now that I have to add an  extra else if into the pmt.cpp  so that config parameter into enigma2/settings :

config.autolanguage.audio_defaultddp=true is followed as the config.autolanguage.audio_defaultac3=true

 

But I can't find the file where to modifie the menu Automatische taalkeuzeselectie



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

  • Senior Member
  • 1,982 posts

+247
Excellent

Posted 1 March 2014 - 18:49

regarding this commit http://sourceforge.n...08386ed67f43c8/

 

we have 3 more :

 

/proc/stb/info/hwmodel

/proc/stb/info/gbmodel

/proc/stb/info/gmmodel

 

and that's all for current brands/models


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


Re: merge requests for PLi's git #475 Taapat

  • PLi® Core member
  • 2,345 posts

+121
Excellent

Posted 1 March 2014 - 21:33

And after this commit http://sourceforge.n...4c3303b6167e05/
please remove import os in 23 line in http://sourceforge.n...rtWizard.py#l23

It is also no longer necessary.



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

  • PLi® Core member
  • 57,062 posts

+698
Excellent

Posted 1 March 2014 - 21:52

Thanks!


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


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

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

+62
Good

Posted 1 March 2014 - 22:18

regarding this commit http://sourceforge.n...08386ed67f43c8/

 

we have 3 more :

 

/proc/stb/info/hwmodel

/proc/stb/info/gbmodel

/proc/stb/info/gmmodel

 

and that's all for current brands/models

 

Will add.

What brands are these?

Do these files describe full model name (like et boxes) or only the subtypes (like vu boxes)?

 

Would be useful to collect more data from such boxes.

The following would collect usefull info:

$ cd /proc/stb
$ grep  -r  ""  *

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 #478 mirakels

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

+62
Good

Posted 7 March 2014 - 15:28

Bump. No intetest in gathering data?
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 #479 Persian Prince

  • Senior Member
  • 1,982 posts

+247
Excellent

Posted 8 March 2014 - 11:24

regarding this commit http://sourceforge.n...08386ed67f43c8/

 

we have 3 more :

 

/proc/stb/info/hwmodel

/proc/stb/info/gbmodel

/proc/stb/info/gmmodel

 

and that's all for current brands/models

 

Will add.

What brands are these?

Do these files describe full model name (like et boxes) or only the subtypes (like vu boxes)?

 

Would be useful to collect more data from such boxes.

The following would collect usefull info:

$ cd /proc/stb
$ grep  -r  ""  *

 

sorry for late answer , i didn't check the thread

 

"hwmodel" is for some brands like technomate - iqon - edision - jepssen - sogno

 

example : tmtwinoe - ios100hd - optimussos1 - mediabox - sogno-8800hd

 

"gbmodel" is only for gigablue

 

example : gb800se - gbquad

 

"gmmodel" is only for golden media hypercube which gives "su980" the model name


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


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

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

+62
Good

Posted 8 March 2014 - 13:07

Thanks,

But please lets try collect the /proc/stb info for all these (anmd other)  boxes. We can put them in the wiki for everybody to see.

 

So run these commands on the specific box and copy paste the result her (or capture it in a file and post as an attachment):

 

 

$ cd /proc/stb
$ grep  -r  ""  *
 

 

We already have info for the following boxes (not yet in the wiki yet. thinking about how to do that...)

 

dm8000 (using drivers with 2.6.18 kernel)
dm800se
et4000
et6500
et9000
vuduo
vuduo2
vusolo2
vuultimo
vuuno
xp1000
 

Please add your contributions...


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


30 user(s) are reading this topic

0 members, 30 guests, 0 anonymous users