644 replies to this topic

[Pr2]

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.

[athoik]

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

[Rob van der Does]

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

[athoik]

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.

[Dimitrij]

transcoding

wakeolan

blind scan

delay decoding

multi rc control

ci+

dual boot

[Pr2]

ci+ is working on some images on the Solo4K 

[littlesat]

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

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

[Huevos]

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.

[Erik Slagter]

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.

[Erik Slagter]

 

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.

[Erik Slagter]

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.

[Rob van der Does]

 

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

[BOSSEB]

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 ...

[Erik Slagter]

 

 

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+.

[Rob van der Does]

 

 

 

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.

[Erik Slagter]

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.

[Rob van der Does]

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

[Erik Slagter]

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.

[Erik Slagter]

 

 

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+.

[Huevos]

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.