644 replies to this topic

[littlesat]

We know that these newer drivers are worser....

[Erik Slagter]

Worser...

 

Anyway. As said, I've reported it (again) to VU+. And I also added a suggestion to make power management optional, to work around issues that can't be solved in a simple fashion.

[veravera]

Hi,

Do you know if ci+ modules will be supported. I am getting pixelated picture trying ci+ module.

 

Thank you and BR

[Erik Slagter]

CI+ is not supported on VU+. At least not in open images.

[veravera]

Hi!

 

I am using CI+ in VU+ Solo2 and it is working perfect with VTi, OpenPli and OpenATV. But the same module in VU+ Solo4K does not work. The picture is pixelated.

[Erik Slagter]

That's possible, then the card is not CI+-activated. The issue you describe must be a hardware or driver issue.

[veravera]

Hi! Thank you!

 

So this is good news if "the card is not CI+-activated".

 

The question is how can I fix this. I have tried the module to more than one VU+ Solo4K and it does not work. Probably, because of the new processor type in VU+ Solo4K. So I presume this is a driver issue.

 

When I switch ci menu on the image to High Bit Rate, I see there is an improvement of the picture. Some parts of the picture are ok. I can even recognize what is going on. But somehow it is not enough.

 

Is it possible to change the driver in order to get "More" High Bit Rate?  

 

Thank you!

Edited by veravera, 18 March 2016 - 10:48.

[Erik Slagter]

@Erik,

 

Just built OpenPLi5 right now. OE core branch master-next. E2 branch master.

 

Config:

Tuner A for Unicable, SCR1.

Tuner C for Unicable, SCR2, linked to tuner A

 

Test:

Start recording on tuner A.

Zap to a different service.

Tuner C is now in use for currently playing service.

Stop the recording.

Picture on tuner C is broken up.

 

Tested with the older driver and the problem is gone.

Now having a unicable switch myself I can dive into this issue. You're completely right Huevos. It's even worse than you describe. Try starting two streams from standby, so tuner A and B are occupied. Then switch on the receiver. Active watching video will come from tuner C now. Stop the streams and the root tuners will be released. From this moment on, the video will break up and keep breaking up, until a zap is done and a root tuner is selected again.

 

Actually it fails even earlier. At the point where the two streams are running and the receiver is in standby, when you wake the receiver, the stream from tuner B will stop instantly! Reproducable!

 

Unfortunately, it appears not to be a power saving issue, because my switch is self-powered and it still happens.

 

As a first step I will add some debug information to the tuner configuration screen, for unicable FBC tuners, just like we did for looped through (normal) FBC tuners. I think that will be interesting, because at some point enigma insisted remaining using tuner C even though tuner A and B where inactive (so maybe still internaly active, which might be good).

[Huevos]

Erik, using the new drivers:

 

"echo on > /proc/stb/frontend/0/force_lnbon"
"echo enable > /proc/stb/frontend/0/force_toneburst"

 

Or you can use the "4K Misc. Plugin" to do the same thing at boot.

Edited by Huevos, 15 April 2016 - 21:29.

[littlesat]

Csn someone please give me a link where Imcan download the drivers... So I can add the new proc configs in a smooth way... .?

[athoik]

Here:

libgles: http://archive.vuplu...60412.r0.tar.gz
platform-util: http://archive.vuplu...60412.r0.tar.gz
vuplus-dvb-proxy: http://archive.vuplu...60412.r0.tar.gz

[Erik Slagter]

Erik, using the new drivers:

 

"echo on > /proc/stb/frontend/0/force_lnbon"
"echo enable > /proc/stb/frontend/0/force_toneburst"

 

Or you can use the "4K Misc. Plugin" to do the same thing at boot.

I am aware of the new proc entries in the new drivers. Do they actually cure the problems? If it does, I can explicitly request VU+ to update the BSP.

 

I understand the name vs. of the first entry, but I don't understand the relation of toneburst to the problems. Maybe they actually mean all sorts of signalling, including tone burst and DiSEqC.

 

Anyway, it looks like in Unicable mode the root tuners can get released at some point, when leaf tuners are still active, so that should be fixed as well.

Edited by Erik Slagter, 16 April 2016 - 10:01.

[Huevos]

Erik, which drivers are you using now?

 

If you are still on 20160119 I can pull the drivers off my STB for you to test.

 

For me, using the new drivers and both the /proc commands satfinder is stable on all tuners including links.

 

From my contact with Vu, they believe the problem is hardware specific, which must be why they have chosen a plugin as the "fix".

 

So far I don't know of any Unicable hardware that doesn't suffer from this condition to some degree.

[Erik Slagter]

I am using our version of the drivers, because I need to be able to reproduce problems that other users experience. If you say the new drivers are good, then I will request VU+ to include them. Not especially for me, but for all our solo4k users.

 

And yes, like you, I think it's actually just a bug, given the same problem occurs on so many different hardware.

 

Having said that, release of tuner A while tuner C is in use is plain wrong and I will correct it.

[nemosince1996]

OpenPLI is my favourite image. I appreciate each step in progress. I have to say that I am only common user.

My configuration is:

Tuner A     - LNB1   SCR1  -     Inverto Unicable IDLB-QUDL42-UNI2L-0PP - 23,5°
Tuner C    - LNB1    SCR2  -    hooked on A
Tuner D    - LNB1    SCR3  -    hooked on A
Tuner E    - LNB1    SCR4  -    hooked on A

Tuner B    - LNB2 - INVERTO RED Extended Quattro - 19°E, DiSEqC 1.1 = input1, DiSEqC 1.0 = A
                 - LNB3 - INVERTO BLACK PREMIUM QUATTRO - rotor 13°E - 5°W, DiSEqC 1.1 = input2, DiSEqC 1.0 = A
Tuner F - not assigned
Tuner G - not assigned
Tuner H - not assigned
        
Inverto Unicable goes directly to tuner A, I use DISEqC EMP CENTAURI S4/1PCT-W2 (2 and 4 switches on) for tuner B.

I do not have problem with recording using tuner A itself or switching between LNB's.

BUT ... when I use PIP starting with LNB2 or I start recording on LNB2 I cannot reach LNB3 and vice versa because it wants to connect to tuner C which is already assigned instead of tuner F which is free. At least it behaved such a way several days ago.I applied update today and possibility to connect to another LNB on tuner B disappeared.

I would like to know some things.

a) is it so difficult to apply changes in configuration of tuners to connect tuners F, G and H? It looks that it could be possible. In such a case Solo 4K could probably operate like Solo2 which I have as well with these three LNB's. It seems to me that everybody is interested in unicable lnb as unique feature of Solo 4K only and connecting universal lnb goes sideways.

different case - probably something has changed in drivers because when I use volume about 5, 10% only I can clearly hear strong noise and the same is when Solo starts and this noise is in the phase of splash screen.

c) when Solo starts after switching on it finishes with strange screen vertically devided by halves and strange colorization. Is it associated with HDMI? Several days ago this did not happen. TV set uses HDMI 4:2:0 which should perfectly suit.
 

 

I wish good luck to everybody who deals with OpenPLI trying to create it perfect.
 

[Huevos]

@nemosince1996, your setup is wrong.

 

Should be:

E connected to D,

D connected to C,

C connected to A.

 

You cannot connect all links to one root tuner in a "many-to-one" config in the way you are. It just will not work properly.

 

Also if tuner B is busy with LNB 2, tuner F will not be able to connect to LNB3.

 

In your config tuner F can only connect to the same satellite and sub-band as is being used by tuner B. Think of tuners F/G/H as loopthrough of tuner B. Tuner B controls the rooting through the DiSEqC switches. Tuners F/G/H are completely passive.

 

Also why are you setting DiSEqC 1.1 AND DiSEqC 1.0 at the same time? Are you running switches in cascade?

 

Lastly your LNBs are quads, not quattros.

Edited by Huevos, 18 April 2016 - 23:12.

[nemosince1996]

@huevos

 

thanks for advice

 

I chained tuners A, C, D and E as you wrote. I will see.

 

Names of LNBs I have taken from the web page of shop where I bought them. It is really quad as I can see on the box. I will remember it. :-)

 

Believe me or not but the only way how to get signal from LNB fully to tuner B in my case is setup which I described. Using only switch with DiSEqC 1.0 did not give me any result, using only DiSEqC 1.1 allowed me to see only some transponders on LNB2 or LNB3.

 

[Erik Slagter]

I agree with Huevos that you might not grasp the concept of FBC tuners completely.

[nemosince1996]

Ok, I can accept it and live with it that Solo 4K is not standard receiver. Anyway thanks for it. Maybe at this moment some kind of overview of OpenPLI team work is missing what is possible what is ongoing and what is a real target. At least some points. Normal user outside the team does not know almost anything.

I have been working  for Koreans for four years and I know that they are very "creative" and they think totally different way than the rest of the world. They hardly accept ideas from anybody else or it takes very long time to enforce them. I wish you luck in this struggle.

Untill I have bought Solo 4K I used to use two Solo's 2 and I was quite happy except recording. Cherchez la femme. This is why I started using unicable LNB because my wife is almost lunatic and she needs to record almost everything what she finds in EPG and she thinks it could be interesting. She is sometimes able to setup up to five six timers concurrently luckily only from sattelite on LNB1. My solution gives me some kind of freedom occassionally to switch to diffrent sattelite via LNB2 or LNB3.

After tuners setup according to Huevos I tried recording on tuners B, F, G and H only as a test. In fact I do not need it. It seems to me that this has probably similar problems in occupying and releasing tuners as team has already started to solve with tuner A and so on.

A question in the end which is not probably related to OpenPLI team job. What about HbbTV?

[Huevos]

I don't think any team has HbbTv working on the Solo 4K.