644 replies to this topic

[littlesat]

And how do you think it does???

[Huevos]

Look in the crash log.

[littlesat]

It does not crash....

[Huevos]

Ok. Different bug then.

[athoik]

MMm with openpli5.0 issues It cannot tune at all (could be something esle)... with Openpli4.0 the tuners are fine....

 

I guess you are using master branch right? Else you need that commit: https://github.com/O...c12c6b696fe3161

[Erik Slagter]

I have no reception at all since using the new drivers (on master-next). I think it's the drivers, but I will investigate more today.

[Erik Slagter]

@Littlesat, the powering is not relevant. On a multiswitch, I believe on a unicable switch as well, the LNB's are powered from the switch, not from the receiver. The issue is the way that FBC tuners work. You cannot use a leaf tuner without a parent root tuner being active. They share some sillicon. You're not having eight tuners, you're having one tuner (!) with two inputs, some shared RF circuitry and six parts of RF circuitry at the end of the chain. It's not the same as eight looped through tuners, even though it represents itself as such.

[Huevos]

@ You cannot use a leaf tuner without a parent root tuner being active.

Erik, In Unicable it is possible to set preferred = C and it works fine (with the old drivers). Theory may say otherwise but in practice this is fact.

 

Anyway the preferred tuner thing is just a distraction from the fact that the drivers are broken.

 

Even just normal zapping with the preferred tuner set to "A" or "Automatic" there are problems obtaining and maintaining tuner lock (in Unicable mode). Signal finder shows this well. No such problem exists with the older drivers.

Edited by Huevos, 19 February 2016 - 13:58.

[Erik Slagter]

I am quite sure "under water" the A tuner is enabled as well and that may also be the actual root cause of the problem.

 

Anyway, if you can make up a good/short explanation of the problem, I can forward it to VU+.

[Huevos]

Erik, here is my bug report.

Vu Solo 4K 20160119 driver bug.

Unicable picture break-up bug.

Tested in:
OpenViX, 
OpenATV,
OpenPLi,
Blackhole.

Setup:
Tuner A, Advanced, Unicable, SCR 1. Tuner A is the root tuner.
Tuner C, Advanced, Unicable, linked to tuner A, SCR 2.
Tuner D, Advanced, Unicable, linked to tuner A, SCR 3.
Tuner E, Advanced, Unicable, linked to tuner A, SCR 4.

Bug:
Picture is broken or there is no picture on tuners C/D/E if the root tuner is inactive.

Method 1:
View a service on tuner A.
Start recording that service.
Zap to a different service.
Stop the recording.
Viewed service is now broken.

Method 2:
View a service on tuner A.
Start recording a different service.
Put box in standby.
Recording is broken.

Method 3:
Set preferred tuner to tuner C.
Zap to a service.
Viewed service is now broken.

Method 4:
Anything else that causes the root tuner to become inactive.

Also, the drivers are generally unreliable even when the root tuner is in use.
Just zapping on tuner A the box often fails to get tuner lock however long you wait.

[littlesat]

And for the time being we need to shift manually the old drivers in the image...

[johnfr]

hello

 

i'm french

how install smargo drivers on solo 4k with openpli ?

thank

[Erik Slagter]

And for the time being we need to shift manually the old drivers in the image...

No we don't. It didn't work me because of a stupid mistake. Now it does.

[Erik Slagter]

Huevos, I have submitted your bug report.

[littlesat]

What did you change to adapt the mistake?

Edited by littlesat, 20 February 2016 - 09:21.

[Erik Slagter]

Stupid mistake = lnb connector that wasn't properly inserted, seemed connected but wasn't. That's the drawback of using quick insert F-connectors.

Edited by Erik Slagter, 20 February 2016 - 09:55.

[littlesat]

Strange.... Here next-master does not tune... And standard image is ok....

[albsky]

I have been following with much interest the discussion about OpenPLi for VU+ Solo 4k, but I cannot give an answer to the following questions.

I hope that someone from the team will clarify (Thanks in advance :-)

 

1. I currently use OpenATV, and I am not able to configure PIP from the same satellite.

I have a Disecq Motor, so one cable connected to Tuner A(DVB-S2). 

Also, I have a dual DVB-T/T2 tuner. PIP DVB-T/DVB-T and DVB-S2/DVB-T2 is fine.

DVB-S2/DVB-S2 works in some combinations but not all. 

How do I configure the second DVB-S2 tuner? Equal to?

 

2. I have seen previously multi stream examples, but I haven't quite understood whether multi stream will be directly supported in STB?

 

3. How difficult is to have a sort of "pass through" for video feature?

I need the same functionality as AutoResolution, meaning that the video is outputted without being processed at all.

Edited by albsky, 20 February 2016 - 13:35.

[littlesat]

Pip does not work good when the output is on 2160p. The pip window is displayed on the incorrect position and size (projected to the left top quater of the screen).

Pip ith UHD channels delivers a complete crash of the drivers...

I suggest work-in-progress... but as far I know this was already reported to VU...

[albsky]

Pip does not work good when the output is on 2160p. The pip window is displayed on the incorrect position and size (projected to the left top quater of the screen).

Pip ith UHD channels delivers a complete crash of the drivers...

I suggest work-in-progress... but as far I know this was already reported to VU...

No, I have a 1080i output, and PIP works as intended in the above mentioned configurations.

I suppose that I have a problem in DVB-S2 dual tuner config.