Jump to content


Photo

VU Solo 4k support


  • Please log in to reply
644 replies to this topic

Re: VU Solo 4k support #481 Pr2

  • PLi® Contributor
  • 6,166 posts

+261
Excellent

Posted 7 March 2016 - 19:25

We have it all this "pixel storm" it gives me the feeling that the console messages are sent to the front display when we issue a reboot.

This is, so far, a purely cosmetic problem, but indeed if VU+ can fix it, it will gives a better feeling to the end-user.


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 of the answer.

Wanna help with OpenPLi Translation? Please read our Wiki Information for translators

Sat: Hotbird 13.0E, Astra 19.2E, Eutelsat5A 5.0W
VU+ Solo 4K: 2*DVB-S2 + 2*DVB-C/T/T2 (used in DVB-C) & Duo 4K: 2*DVB-S2X + DVB-C (FBC)

AB-Com: PULSe 4K 1*DVB-S2X (+ DVB-C/T/T2)
Edision OS Mio 4K: 1*DVB-S2X + 1*DVB-C/T/T2
 


Re: VU Solo 4k support #482 athoik

  • PLi® Core member
  • 8,458 posts

+327
Excellent

Posted 7 March 2016 - 19:36

I prefer to see blindscan support on FBC tuners also MIS/PLS cabalilities and several exotic modulations.

Additionally extended cw would be a great plus.

Finally some find really nice the delayed decoding feature a must.

If all/most of the above would implemented it would make solo4k an excellent STB.


Now it still lacks some features that doesn't make that box "the king" ;)

The "pixel storm", it's just nice effect :)
Wavefield T90: 0.8W - 1.9E - 4.8E - 13E - 16E - 19.2E - 23.5E - 26E - 33E - 39E - 42E - 45E on EMP Centauri DiseqC 16/1
Unamed: 13E Quattro - 9E Quattro on IKUSI MS-0916

Re: VU Solo 4k support #483 Rob van der Does

  • Senior Member
  • 7,766 posts

+184
Excellent

Posted 7 March 2016 - 19:42

Are this driver-related issues? And if so: how does VU+ think about these wishes?



Re: VU Solo 4k support #484 athoik

  • PLi® Core member
  • 8,458 posts

+327
Excellent

Posted 7 March 2016 - 19:54

Some are hardware related, eg the mis/pls/modulation, so only vu+ might know what fbc tuners are capable of.. Or any one that has the hw reference.

The extended cw/delay decoding is driver feature.

Edited by athoik, 7 March 2016 - 19:55.

Wavefield T90: 0.8W - 1.9E - 4.8E - 13E - 16E - 19.2E - 23.5E - 26E - 33E - 39E - 42E - 45E on EMP Centauri DiseqC 16/1
Unamed: 13E Quattro - 9E Quattro on IKUSI MS-0916

Re: VU Solo 4k support #485 Dimitrij

  • PLi® Core member
  • 10,275 posts

+347
Excellent

Posted 7 March 2016 - 20:26

transcoding

wakeolan

blind scan

delay decoding

multi rc control

ci+

dual boot


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


Re: VU Solo 4k support #486 Pr2

  • PLi® Contributor
  • 6,166 posts

+261
Excellent

Posted 7 March 2016 - 22:26

ci+ is working on some images on the Solo4K  ;)


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 of the answer.

Wanna help with OpenPLi Translation? Please read our Wiki Information for translators

Sat: Hotbird 13.0E, Astra 19.2E, Eutelsat5A 5.0W
VU+ Solo 4K: 2*DVB-S2 + 2*DVB-C/T/T2 (used in DVB-C) & Duo 4K: 2*DVB-S2X + DVB-C (FBC)

AB-Com: PULSe 4K 1*DVB-S2X (+ DVB-C/T/T2)
Edision OS Mio 4K: 1*DVB-S2X + 1*DVB-C/T/T2
 


Re: VU Solo 4k support #487 littlesat

  • PLi® Core member
  • 57,064 posts

+698
Excellent

Posted 7 March 2016 - 22:45

But with a bad work-a-round.... It is voilancing the e2 license...

Edited by littlesat, 7 March 2016 - 22:45.

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


Re: VU Solo 4k support #488 Huevos

  • PLi® Contributor
  • 4,624 posts

+161
Excellent

Posted 9 March 2016 - 14:28

It looks like the first commit is a real fix for FBC tuners (but won't it break other tuners/types), the second is a Q&D workaround. It looks like all frontends are continuously left in "full on" mode after this commit is applied, blech.

 

This looks like:

 

- old FBC tuner driver did not implement frontend off/standby and left it on always

- newer driver implements it but reveals issues

- now the enigma code simply leaves all frontends always on

 

Then reinstating the old driver would actually have my preference, because it breaks FBC the tuners at worst, leaving all other tuner types alone.

 

Is http://code.vuplus.c...26da558fd06da39 related to this bug?

Or http://code.vuplus.c...80d5f4b335ea383 ?

 

 

I've built and tested these commits. Neither cures the 4K tuner lock with later drivers problem.



Re: VU Solo 4k support #489 Erik Slagter

  • PLi® Core member
  • 46,969 posts

+541
Excellent

Posted 9 March 2016 - 15:05

We have it all this "pixel storm" it gives me the feeling that the console messages are sent to the front display when we issue a reboot.

This is, so far, a purely cosmetic problem, but indeed if VU+ can fix it, it will gives a better feeling to the end-user.

No, I simply think the LCD drivers are turned off (HiZ) so the LCD receivers garbage.


* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: VU Solo 4k support #490 Erik Slagter

  • PLi® Core member
  • 46,969 posts

+541
Excellent

Posted 9 March 2016 - 15:07

 

It looks like the first commit is a real fix for FBC tuners (but won't it break other tuners/types), the second is a Q&D workaround. It looks like all frontends are continuously left in "full on" mode after this commit is applied, blech.

 

This looks like:

 

- old FBC tuner driver did not implement frontend off/standby and left it on always

- newer driver implements it but reveals issues

- now the enigma code simply leaves all frontends always on

 

Then reinstating the old driver would actually have my preference, because it breaks FBC the tuners at worst, leaving all other tuner types alone.

 

Is http://code.vuplus.c...26da558fd06da39 related to this bug?

Or http://code.vuplus.c...80d5f4b335ea383 ?

 

 

I've built and tested these commits. Neither cures the 4K tuner lock with later drivers problem.

Good to know. Thanks for testing.


* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: VU Solo 4k support #491 Erik Slagter

  • PLi® Core member
  • 46,969 posts

+541
Excellent

Posted 9 March 2016 - 15:08

Are this driver-related issues? And if so: how does VU+ think about these wishes?

I've mentioned the issue of delayed decoding several times, but it's never acknowledged, so I guess they don't care.


* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: VU Solo 4k support #492 Rob van der Does

  • Senior Member
  • 7,766 posts

+184
Excellent

Posted 9 March 2016 - 15:51

 

Are this driver-related issues? And if so: how does VU+ think about these wishes?

I've mentioned the issue of delayed decoding several times, but it's never acknowledged, so I guess they don't care.

 

They probably will, as soon as CI+ is mandatory for many providers.

But if it's a hardware-design flaw rather then something that can be implemented by the drivers that will be too late :(



Re: VU Solo 4k support #493 BOSSEB

  • Senior Member
  • 43 posts

0
Neutral

Posted 10 March 2016 - 12:10

Hello

i have a PCTV Nano stick DVB-T and when i active AAC downgrade for some 4K channels , there is a bug with dvb-t channels the screen freeze ...



Re: VU Solo 4k support #494 Erik Slagter

  • PLi® Core member
  • 46,969 posts

+541
Excellent

Posted 10 March 2016 - 13:24

 

 

Are this driver-related issues? And if so: how does VU+ think about these wishes?

I've mentioned the issue of delayed decoding several times, but it's never acknowledged, so I guess they don't care.

 

They probably will, as soon as CI+ is mandatory for many providers.

But if it's a hardware-design flaw rather then something that can be implemented by the drivers that will be too late :(

Delayed decoding (through the CA demuxer) is unrelated to CI+.


* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: VU Solo 4k support #495 Rob van der Does

  • Senior Member
  • 7,766 posts

+184
Excellent

Posted 10 March 2016 - 19:50

 

 

 

Are this driver-related issues? And if so: how does VU+ think about these wishes?

I've mentioned the issue of delayed decoding several times, but it's never acknowledged, so I guess they don't care.

 

They probably will, as soon as CI+ is mandatory for many providers.

But if it's a hardware-design flaw rather then something that can be implemented by the drivers that will be too late :(

Delayed decoding (through the CA demuxer) is unrelated to CI+.

 

Not completely: as the use of a(ny) CI allows only limited descrambling, recordings will often be scrambled.



Re: VU Solo 4k support #496 Erik Slagter

  • PLi® Core member
  • 46,969 posts

+541
Excellent

Posted 11 March 2016 - 12:51

But the following delayed decoding is either through the CI module or through the CA demuxer, which are completely different systems. A CA demuxer can never descramble something only supported by the CI module, otherwise you woudn't need the CI in the first place.


* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: VU Solo 4k support #497 Rob van der Does

  • Senior Member
  • 7,766 posts

+184
Excellent

Posted 11 March 2016 - 18:57

So you're saying that CI-support is rather useless in the first place?



Re: VU Solo 4k support #498 Erik Slagter

  • PLi® Core member
  • 46,969 posts

+541
Excellent

Posted 11 March 2016 - 21:01

No.

I say that (delayed) decryption comes in two flavours, one using the CA demuxer (which is used in softcams), one using a CI module and that they're totally unrelated.


* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: VU Solo 4k support #499 Erik Slagter

  • PLi® Core member
  • 46,969 posts

+541
Excellent

Posted 12 March 2016 - 12:35

 

 

It looks like the first commit is a real fix for FBC tuners (but won't it break other tuners/types), the second is a Q&D workaround. It looks like all frontends are continuously left in "full on" mode after this commit is applied, blech.

 

This looks like:

 

- old FBC tuner driver did not implement frontend off/standby and left it on always

- newer driver implements it but reveals issues

- now the enigma code simply leaves all frontends always on

 

Then reinstating the old driver would actually have my preference, because it breaks FBC the tuners at worst, leaving all other tuner types alone.

 

Is http://code.vuplus.c...26da558fd06da39 related to this bug?

Or http://code.vuplus.c...80d5f4b335ea383 ?

 

 

I've built and tested these commits. Neither cures the 4K tuner lock with later drivers problem.

Good to know. Thanks for testing.

I reported this to VU+.


* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: VU Solo 4k support #500 Huevos

  • PLi® Contributor
  • 4,624 posts

+161
Excellent

Posted 14 March 2016 - 20:36

4K with 20160119 drivers. Filmed in OpenViX but happens in all images I've tested including OpenPLi when using Unicable. FTP old drivers to the receiver and reboot completely cures this behaviour.

 


Edited by Huevos, 14 March 2016 - 20:37.



15 user(s) are reading this topic

0 members, 15 guests, 0 anonymous users