644 replies to this topic

[Erik Slagter]

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.

Your questions one by one.

 

1. OpenATV has the original VU+ code for the FBC tuners (which I think can do with some improvements), we have rewritten most of it. So I can't really give you an answer to that.

 

2. If you mean transport-stream-in-transport-stream, that's not supported by the FBC tuners (nor is it supported by another pluggable or fixed tuner, so no surprise there).

 

3. If you turn off all enhancements, that's what you look for I guess?

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

Your questions one by one.

 

1. OpenATV has the original VU+ code for the FBC tuners (which I think can do with some improvements), we have rewritten most of it. So I can't really give you an answer to that.

 

2. If you mean transport-stream-in-transport-stream, that's not supported by the FBC tuners (nor is it supported by another pluggable or fixed tuner, so no surprise there).

 

3. If you turn off all enhancements, that's what you look for I guess?

 

Thanks a lot for your replies.

1. My question is more generic: is DVB-S2/DVB-S2 PIP supported? With only one cable connected(motor)?

2. I mean channels that are referres as DVB-S2 PLS: Root+8 8PSK ACM/VCM Stream 2

3. I have turned off all enhancements, but in basic video settings I have to set the output resolution. Is it possible to have a setting like for eg "Original"?

[Erik Slagter]

1. Yes, PiP is supported with one input very well. It's just like any other receiver, if you have two services on the same transponder, they can be received by the same tuner and one of them can then serve as input for the second video decoder (= PiP). Also if you setup FBC correctly, with OpenPLi at least, other images I don't know about, you can pick any other transponder (frequency) that has the same polarisation and the same band (hi/lo) and it will be passed to one of the FBC tuners and received from there. This can also serve as input for PiP.

 

2. PLS / ACM / VCM (which is the same, actually) is not supported. It's something that both driver and hardware must support, we can't.

 

3. Then you should use AutoResolution (and ask the author to add UHD )

[littlesat]

With the output set to 4K you actually do not really mean AutoResolution plugin..... The upscaler is working fine!!! And you will keep full-HD 1920x1080 skinning...

[Dimitrij]

littlesat or Erik Slagter

pleasa answer to http://forums.openpl...ndpost&p=530993

[Erik Slagter]

With the output set to 4K you actually do not really mean AutoResolution plugin..... The upscaler is working fine!!! And you will keep full-HD 1920x1080 skinning...

That's what you (and I) say, but there are always others that disagree. The built-in motion adaptive bob & weave deinterlacer (if you properly set the output frame rate to 50 or 60 Hz (progressive)!!!) is really quite good, also for lower resolutions.

[Maksyuha]

littlesat or Erik Slagter

pleasa answer to http://forums.openpl...ndpost&p=530993

 

https://youtu.be/bb_vflMa_Nc

 

Especially pay attention to what happens when you switch to a mode of 1080 (the time of 4m: 40s). Thanks!

Edited by Maksyuha, 23 February 2016 - 21:04.

[littlesat]

I have het permanently on 2160p output... Why switching it back?? In addition I'm afraid this is something that needs to be improved in the drivers...

Edited by littlesat, 23 February 2016 - 22:14.

[Pedro_Newbie]

Could someone test the current, git 92, BackupSuite with the Solo4k? I hear of different results.
Screen-shots of the process and the BackupSuite.log from the folder /tmp would be welcome.

TIA

Nobody? If someone would like to try and report, the BackupSuite.log would be fine

[Erik Slagter]

Huevos, I have submitted your bug report.

And I have a reply.

 

 

There is a problem in tuner setup.

Problem would be solved if setup is as below.

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 C, SCR 3.
Tuner E, Advanced, Unicable, linked to tuner D, SCR 4.

compared to

 

 

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.

I think we should consider automatically assigning the links for unicable as well, but it might be complex.

[Pr2]

 

Huevos, I have submitted your bug report.

And I have a reply.

 

 

There is a problem in tuner setup.

Problem would be solved if setup is as below.

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 C, SCR 3.
Tuner E, Advanced, Unicable, linked to tuner D, SCR 4.

compared to

 

 

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.

I think we should consider automatically assigning the links for unicable as well, but it might be complex.

 

 

It seems that a tuner can only be linked once, so if a tuner is already linked it should no longer be available to link again. This is perhaps the way to implement this.

It is like we have with physical tuners where there is only one "loop out" real or logical. So the same approach can be done both on "virtual" tuners and on "physical" tuners. A tuner can only be linked once.

[Erik Slagter]

I was thinking of proposing to simply link half of the leaves to root A and the other to root B for unicable, but we can't do that, because one might have a unicable system at root A and a normal system at tuner B. In that case all leaf tuners must be selectable to be linked to either root, as usual.

 

The only solution I can think of, is a dynamic check, in the configuration screen, that all adjacent unicable tuners are linked as a chain and not many-to-one, and prevent the latter to be entered.

 

Also I think I do know where this requirement comes from. It's not a hardware requirement, it has to do with the way enigma handles looped tuners. They're organised as a doubly linked list that is traversed both way (depending on the situation). A doubly linked list cannot contain many-to-one or one-to-many references. If you're lucky forward traversal will succeed but backward traversal is broken. And that is, imho, the issue here.

 

To fully implement the capabilities of FBC tuners, in a clean way, another tuner linkage scheme should be introduced into enigma, where one-to-many references are possible, in some sort of tree implementation instead of linked list. That also means only forward traversal is possible, but that's no real issue as long as the root is always available.

[Rob van der Does]

So the least we should have is a list of possible leaf-tuner config options when using Unicable per root tuner?

Edited by Rob van der Does, 26 February 2016 - 13:41.

[Erik Slagter]

Solution:

 

 - for the time being: configure manually as recommended by VU+

 - long time proper solution: change the satellite configuration screen so invalid combinations are not possible

 

Both do not restrict the possibilities, btw. It's still possible to connect any leaf tuner to any root tuner, unicable or not. Just make sure they're linked in a "chain".

Edited by Erik Slagter, 26 February 2016 - 13:52.

[Rob van der Does]

Yes, but this requires a 'tips & tricks' section on the board.

[Frenske]

Yes, but this requires a 'tips & tricks' section on the board.

Basicly we already have that section.
Unfortunately there is little added by the endusers.

[Huevos]

 

Huevos, I have submitted your bug report.

And I have a reply.

 

 

There is a problem in tuner setup.

Problem would be solved if setup is as below.

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 C, SCR 3.
Tuner E, Advanced, Unicable, linked to tuner D, SCR 4.

compared to

 

 

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.

I think we should consider automatically assigning the links for unicable as well, but it might be complex.

 

Erik it is not true.

 

I have tested all linked to A,

And I have tested A linked to C linked to D linked to E, etc

Both combinations work fine with the old drivers.

Both combinations do NOT work with the newer drivers.

[Huevos]

I was thinking of proposing to simply link half of the leaves to root A and the other to root B for unicable, but we can't do that, because one might have a unicable system at root A and a normal system at tuner B. In that case all leaf tuners must be selectable to be linked to either root, as usual.

On this box my setup is tuner A Unicable. Tuner B, motor with Universal LNB.

Current code works well with this setup (with the old drivers).

[Huevos]

And by the way I am not the only person to notice the driver issue. 3 independent setups have tested OpenViX, OpenPLi, OpenATV and Blackhole. All found the same issues with the current drivers. Even if you just set up tuner A and no other tuners a quick flick through transponders on satfinder shows the issue.

[Erik Slagter]

RvdD: Or fix in the code (option 2, but that requires a volunteer ).

Edited by Erik Slagter, 26 February 2016 - 15:45.