172 replies to this topic

[Erik Slagter]

 

We could consider al least to re-add the support in the e2 binary.... at this moment the patches are reverted *but they do not harm)... Maybe "someone" could help to get the plugin running...

No, the code I had to add to workaround the incompatibilities is ugly.

[littlesat]

At least I could prepare it's working on 1080p which is doesn't also (yet)

[Erik Slagter]

You can go ahead, but don't the use plugin (at least not one-to-one). Either add additional PiPses to enigma in the usual way, or adapt the plugin so it doesn't the ugly workarounds in enigma. I am quite sure that's possible.

Edited by Erik Slagter, 8 September 2017 - 20:52.

[littlesat]

Additional pipses to e2 is not really possible... it beats on all places... this means breaking a lot of plugins etc. but making vu's plugin much better is easy....

Edited by littlesat, 8 September 2017 - 21:00.

[Erik Slagter]

But the result will be quite less flexible. But whatever you want. As long as it doesn't include ugly workaround code in enigma.

[littlesat]

Do you really think I put that dirty work-a-round in... even offi vu's plugin doesn't do it...

[nor50]

 

Is this on a 4K-TV?

[littlesat]

Only with possible with dirty work-a-round.... If vu and output in 4k then doublethe pip positions... Some kind of not done! In addition the way you select channels is not user friendly.

Edited by littlesat, 10 September 2017 - 21:57.

[Satpal]

Sorry littlesat, but I didn't get most of what you were trying to say in your last posting, smartphone autocorrect acting up, maybe?

 

I don't understand your comment about the way to select channels not being user friendly. What other (better) way would you suggest?

 

I'm just wondering whether it is possible with the original plugin to use the HDMI-IN as a source for the QuadPiP? As it is working without problem in PiP mode I guess that should be possible as well or am I missing something?

[mrvica]

original code is here, you have to have a look at the source code
http://code.vuplus.c...po&repos=dvbapp

[колбаскин]

Black Hole 3.0.4 Quad PiP - On September 10 already worked

One person already himself has attached to ATV image, but hasn't dealt with a sound yet. The picture is.

[колбаскин]

 

 

Is this on a 4K-TV?

 

On FullHD

[nor50]

Will 4 x PIP be available here soon...?

[littlesat]

I'm afraid first Vu needs to fix the normal pip and 2160p 'bug' which is already in there for years...

[nor50]

I'm afraid first Vu needs to fix the normal pip and 2160p 'bug' which is already in there for years...

 

So how can other images have quad pip?

[littlesat]

By adding a dirty if Vu then do something else patch instead of don't support it until Vu solves their ugly bug. We prefer that bugs should be solved where they belong...

Edited by littlesat, 14 September 2017 - 06:04.

[колбаскин]

While you are afraid, others have already made!!!
The team Black Hole doesn't need nothing, they have just made.

In the nearest future and other teams will make.
Only you want to do nothing

[Trial]

Hi,

VTi and BlackHole are based on the original image so THEY MADE NOTHING.

 

ciao

[littlesat]

We want to do it right!!! It is a shame that other teams don't do it right and some of them -those where Q-PIP currently works- are even violating the GPL license by being closed source... so they are not helpfull at all.

 

As far we can see the original image of VU+ does also not have the fix for 2160p output mode and PIP...

 

And actually the work-a-round is simple... But not the place and a way this kind of bug should be solved...

 

So please instead of bothering us.... Please goto VU+ and tell them they should solve the bug...

 

Only you want to do nothing

Edited by littlesat, 14 September 2017 - 08:21.

[Frenske]

I guess that both sides have mentioned how they feel concerning this matter so IMHO there's no further need keeping arguing why this isn't yet implemented in OpenPLi.