55 replies to this topic

[GT8k]

PiPSetup.py

-MAX_W, MAX_H = BoxInfo.getItem("MaxPIPSize")
+MAX_W = MAX_X * 3 // 4
+MAX_H = MAX_Y * 3 // 4

If I edit this one am I gaining smth here?!

[Erik Slagter]

Actually I can shed some light here, as apparently the issue not quite understood by many people.

 

To start with, this issue is not specific for picture-by-picture PiP, but it may show there as it requires both outputs to be quite large, whilst in "normal" PiP mode, the PiP video output is usually quite small.

 

Then, this issue is not VU+ specific, it's not even model-specific. It's just that VU+ uses other SoC types then most other manufacturers (more expensive, less basic), so they have their own limitations.

 

So yes, this is a limitation, not a bug. The SoC from the VU+ Solo4k and probably Uno4k(SE) too is limited in the PiP size that can be shown. Furthermore the actual size of the PiP depends on the position on the screen. So the window can be quite large when it's in the upper-left corner, but needs to be smaller gradually when moving to the lower-right corner. VU+ "solved" this issue in the drivers by accepting all possible coordinates, but apply a "correction" so the PiP window's size and position never get invalid.

 

IIRC GigaBlue or QViart have receivers with the same SoC and they're not applyting this correction. The result is garbage on the screen and possibly crashing. So what VU+ is doing, isn't that bad actually.

 

The interesting thing is that the SoC's of the Duo4k and the Duo4kSE/Ultimo4k (same SoC) do not have this limitation, they have really high end SoC's, that include four completely independent video decoders, which are also used for the QuadPiP feature. In theory it would be possible to use all of these as independent PiP sources, but we never looked into it, as it's not really interesting for the end user.

 

So we asked VU+ to lift the limitations for the SoC's that don't need it and they did. So the Duo4k, Duo4kSE and Ultimo4k do offer random positioning of the PiP and I can confirm that picture-by-picture really works.

 

So the bottom line is: if you want random positioning of PiP, you need a high-end SoC, so a more expensive receiver. For PiP you need (an) extra video decoder(s), which are expensive if added with full functionality.

[Erik Slagter]

 

 

only having the sound of the main screen and the full video of the PiP.

So how you achieved this? There is no audiopip plugin in the feed available, and for some events like f1 I just need the audio from another channel while watching other ch on full screen...

 

On VU+ you can only gets audio from the main screen and not from the PiP. I have been told that there is no audio decoder in the chipset that handle PiP so it is not possible to have PiP audio.

This was possible on my Xtrend ET-9000.

 

Over here it works (Ultimo4k), try it with QuadPiP. So I guess it's possible, it's just not implemented in Enigma right now. I hear a feature request coming there 

[Pr2]

Erik,

 

Sorry but I have a VU+ Solo4K and a VU+ Duo4K and PiP is behaving exactely the same on both boxes.

Also QuadPIP is also working on both boxes.

 

So the VU+ Duo4K is not capable to display the PiP window into full screen, the max size is always 1/4 of the screen size.  People report that other images don't have this limitation, so why only OpenPLi has it?

 

Sometimes I would like to display a channel on the "main" screen to get the sound out of it and being able to increase the image from the selected PiP TV Shows leading in having audio from main screen and video from PiP.

 

On the Duo4K and on the Solo4K you can place the PiP windows everywhere that you want on screen (max size 1/4 screen), you can no longer move it when you increase it too much (for OpenPLi or the driver) then juste press P- to virtually reduce the size until the move is working again.

[littlesat]

Likely when output is 4K the maxsize is 1/4 th…. And maybe when the output is hd then it can be full screen ? So I’m afraid it is not that simple.

Edited by littlesat, 7 March 2024 - 22:09.

[DimitarCC]

As i wrote before...On Duo4KSE i can put the PiP on full screen and hdmi output is 2160p....So its possible.

[littlesat]

And we have now indeed limitations in SystemInfo.py...

[Dimitrij]

Why doesn't anyone check this?

-MAX_W, MAX_H = BoxInfo.getItem("MaxPIPSize")
+MAX_W = MAX_X * 3 // 4
+MAX_H = MAX_Y * 3 // 4

/usr/lib/enigma2/python/Screens/PiPSetup.py develop image

 

[Pr2]

Hi Dimitrij,

 

I have just tested your PiPSetup.py:  on the VU+ Solo4K and on the Duo4K nothing changed.

 

Pr2

[DimitarCC]

Maybe it works on SE versions...Or maybe only on Duo4KSE?!

[GT8k]

/usr/lib/enigma2/python/Screens/PiPSetup.py develop image

 

On uno4kse there is only PiPSetup.pyc file...

[WanWizard]

Source is not installed by default, on any box. Install the package with "-src" if you want the source too.

[GT8k]

Source is not installed by default, on any box. Install the package with "-src" if you want the source too.

I don't quite understand this one. Could be more specific please?

[WanWizard]

If you need the source of a python file, you need to install the source package (ipk).

 

In this case, it is part of enigma2, so you need to install the "enigma2-src" package.

[GT8k]

Guys check this out, after an update of the pli-9 image there are some changes:
but still the second picture stays unchanged though...  IMG_20240326_2.jpg   60.31KB   17 downloads

[GT8k]

2day I made the mistake to update my stb...
What the heck is going on here?! The left screen again is this small in pip!
Is this gonna be fixed or I should flash the older version?? (luckily I downloaded the img from 25/03/24)  IMG_20240509_220802.jpg   12.68KB   6 downloads