39 replies to this topic

[dasrax]

please how to get this skin in my pli.  02.info.jpg   95.17KB   16 downloads  03.infobar.jpg   91.98KB   16 downloads  04.2ndinfobar.jpg   99.45KB   16 downloads  05.menu.jpg   82.54KB   16 downloads  06.setup.jpg   82.46KB   16 downloads  07.channelselection.jpg   132.76KB   16 downloads  08.movieselection.jpg   98.95KB   16 downloads

[Rob van der Does]

That skin uses a 1080-framebuffer, which is not supported by PLi-images.

[littlesat]

Not all drivers/hardware do support a 1080-framebuffer.... OpenPLi supports it for ages!!! We were even the first that jump to 1080 when required (for pictures, test screens)....

 

What SatKiekerd mentioned before is not true.

 

It might be the skin needs some (slightly) changes as it is build on the based on OpenPLi OE-A "ViX" image.... 

 

E.g. it needs a adaption of the about screen because they make it about-oe screen or so... It is a non-PIG skin, so I suggest the adaptions for plugins and features etc. should be reduced...

Edited by littlesat, 30 October 2014 - 07:44.

[dsdavidsat]

someboby who knows the name of the skin?

[dasrax]

is called youvix blue

[Rob van der Does]

Not all drivers/hardware do support a 1080-framebuffer.... OpenPLi supports it for ages!!! We were even the first that jump to 1080 when required (for pictures, test screens)....

 

What SatKiekerd mentioned before is not true.

Oh? So you suddenly have the latest VU drivers embedded than?

I can assure you that I very rarely lie (if I ever do at all).

 

And apart from the frame buffer support (that is or is not in the drivers), there's much, much more needed to properly support 1080-OSD. If you only simply apply a skin, much of the contents and many plugins are unusable (unreadable).

This is caused by the fact that much screen contents is not properly skinnable: often the lay-out is hard coded in the py's. That is all based on 720 and/or SD-skins, not on 1080 skins.

Just add a 1080 skin and you'll see what I mean within seconds.

 

So no: I didn't lie, and it would be very much appreciated if you would kindly check the facts before reacting like this.

[blzr]

please how to get this skin in my pli

 

 

That skin uses a 1080-framebuffer, which is not supported by PLi-images.

 

and where it was VU mentioned in this theread?

xtrend boxes have 1080p framebuffer and it is supported by OpenPLi for ages (as @Littlesat said)...

 

so I would advice to read carefully first, and then write...

[WanWizard]

Is that the problem of the skin, or of the idiot that decided to hardcode stuff in py's?

[Rob van der Does]

please how to get this skin in my pli

 
 

That skin uses a 1080-framebuffer, which is not supported by PLi-images.

 

and where it was VU mentioned in this theread?
xtrend boxes have 1080p framebuffer and it is supported by OpenPLi for ages (as @Littlesat said)...
 
so I would advice to read carefully first, and then write...

Well, I think it's quite obvious: VU has the 1080 framebuffer activated in recent drivers, but PLi doesn't have them embedded (and I know why, so no need to go into that).
So I think carefull reading leads to the conclusion that PLi doesn't support 1 1080 skin because of:
1- not using VU drivers that support 1080 OSD
2- a lot of hard-coded lay-out that cannot be used for 1080-OSD.

[blzr]

ok,
 

That skin uses a 1080-framebuffer, which is not supported by PLi-images.

 
and
 

That skin uses a 1080-framebuffer, which is not supported by PLi-images for VU receivers.

and now tell me which statement is actually true...

Edited by blzr, 31 October 2014 - 12:01.

[Rob van der Does]

ok,
 

That skin uses a 1080-framebuffer, which is not supported by PLi-images.

 
and
 

That skin uses a 1080-framebuffer, which is not supported by PLi-images for VU receivers.

and now tell me which statement is actually true...

I think our postings have crossed, as the answer is just above yours:

So I think careful reading leads to the conclusion that PLi doesn't support 1 1080 skin because of:
1- not using VU drivers that support 1080 OSD
2- a lot of hard-coded lay-out that cannot be used for 1080-OSD.

[littlesat]

Pli supports 1920x1080 skins for years... Vu did not support them and there were no skins made yet that were made on 1920x1080

Also Pli introduced scalable skin features that were also never adapted to skinners... This incluses this skin... (That also includes some code that could be made much easier with e.g. position="full")...

And when indeed closed source python code is required for this skin, then it is not done here on this open source minded forum. But t least the licence of this skin mentioned it is free to use... So possibly when someone has some time it likely could be adapted.

Plugins are usually correctly displayed on any resolution platform when the plugin makes the screens right and/or the skin does also support specific screens for the specific plugin. At is no issue at all (as our standard PIG skin demonstrated)

Edited by littlesat, 31 October 2014 - 12:30.

[Rob van der Does]

There is no closed source involved in this skin; not sure why you think so?

No use saying that my statement is not correct (about some hard coded lay-out in (embedded) py's and plugins) as you apparently haven't even tried it
Just grab the skin, put it on your box and you'll see within seconds where the issues (and hence the work to be fully 1080-OSD compatible) are.
And see how many plugins are not correctly displayed......

[WanWizard]

It is not our job to make plugins compatible, it is the job of the plugin author. You're barking up the wrong tree.

[Rob van der Does]

If you're really interested: have a look @ https://github.com/O...gma2/tree/1080p.
There you see that a separate branch had to be created due to the many changed requirements for a full support of a 1080-skin. Just have a quick look at the changes and you'll get the idea. Roughly the same would be required for PLi's E2.
And the same story applies to the plugins.....

[Rob van der Does]

It is not our job to make plugins compatible, it is the job of the plugin author. You're barking up the wrong tree.

As you seem to do: I was mentioning embedded py's as well as plugins. And embedded py's really stem from PLi.

 

Of course there are also good examples: e.g. the embedded screens of Open Uitzending Gemist indeed support all resolutions. But this is a rare example.

 

Again: please take a few minutes to actually use the skin; seeing the issues tells you much more than trying to deny them. 

[rossi2000]

dont take this the wrong way but can you clarify how you support 1080 skins for years?,  the only models you support with the 1080 framebuffer are xtrend and mutant

and xtrend only added support upon MY request back in march 2014.  

 

just curious.

[littlesat]

Xtrend did support 1080 skins almost from the beginning.... For the first drivers of the et10k and 8k this was indeed not available and I did request this already somewhere in februari when I discover this with my sample.

The fact that there was no 1080 skin yet, was due to no skinner did make it yet... I suppose you're one of the the first.

Please note you can make your skin code much easier.... position="0,0" size="1920,1080" can be replaced by position="full"

I also do not understand the stuff satkiekerd mentioned about the plugins... When you make a screen for a plugin within your skin the issue is solved.... A general solution could be found by recalculating cordinates when the positions on the main screen is not full or so...

Edited by littlesat, 31 October 2014 - 13:38.

[Rob van der Does]

I also do not understand the stuff satkiekerd mentioned about the plugins... When you make a screen for a plugin within your skin the issue is solved.... 

That is indeed the issue: most plugins need to be skinned, because they don't support the 1080 resolution. And that results in an extreme small plugin window.

And for some plugins the same applies as for some embedded py's (and even in C++): the lay-out is hard-coded, so they can't be properly skinned.

 

Again:

1- Look at the 1080-branches of the repos (E2, skin-default & plugins, https://github.com/o.../tree/2.3-1080p , https://github.com/o.../tree/2.3-1080p , https://github.com/oe-alliance/oe-alliance-e2-skindefault/tree/1080p ) to get some idea.

2- Just load the skin and you'll experience all issues yourself; that gives you a clear picture of the requirements for fully supporting 1080-OSD. Only costs you a couple of minutes....

Edited by SatKiekerd, 31 October 2014 - 13:53.

[littlesat]

With the links you giving us it costs hours... Do I see a patch coming here that I can use with git am -s later today?

You pointing us to a 1080 branch.... where are the essential commits there???

At this moment the skin.xml is short and lots of stuff have been transferred to vix's enigma2.... So the skin is not really good installable at this moment...

And please telling us fix has a great 1080hd skin is not really added value here... Added vallue here is to arrange that we'll get it also... This does not mean we have to re-invent a 1080hd skin by ourselves...

When plugins are skinned in the skin they all support 1080 skins... Indeed plugins with hardcoded coordinations will be displayed somewhere on the right/top of the screen... Please note in fact this is the fault from the plugin as they do not use c and e coordinates as dmm never supported it as this was an openpli solution. Some plugins have switches from sd to hd (720) with fix values and not 1080.... So the only fix here is work-a-round these plugins or add a screen for them in your specific skin... Where is the commit that work-a-rounds this?

P.s. And thanks for renaming hotkey...

Edited by littlesat, 31 October 2014 - 15:16.