57 replies to this topic

[Inspiron80]

A skin that adds binaries….?

Many new and modern skin currently use this technique to display the video /audio Bitrates,

Be be honest I don't know why users looking for these data but many users looking and ask for it,

[WanWizard]

So it is a binary.

 

In that case it will not work, unless you include source. A binary needs to be ARCH compatible, and the only way to ensure that, is to include the source.

[littlesat]

When you want to show bitrate it should use one of the bitrate plug-ins and maybe delend on it, but not include a binary as we have boxes with different microcontroller artechiture it will never work for all boxes.

[Inspiron80]

So it is a binary.
 
In that case it will not work, unless you include source. A binary needs to be ARCH compatible, and the only way to ensure that, is to include the source.

I do not have it as open file, I test it with openpli and all images listed and it work without a problem I am not sure if openpli has something similar can rely on it to retrieve vido/audio Bitrates?....

I think we are talk a lot about the process without a single word about the skin itself,

Anyway, keep as it is, if you believe your end users can not install normal ipk file or use terminal to execute a simple telnet command, I think we will move in closed loop,

Regards

[Inspiron80]

When you want to show bitrate it should use one of the bitrate plug-ins and maybe delend on it, but not include a binary as we have boxes with different microcontroller artechiture it will never work for all boxes.

Both options are available in the skin, you have a skin plugin called XDREAMY, you have two choises for Bitrates data source.

1. Using Bitrates rendering
2. Using Bitrates plugin

So if you have any problem with one method simply you can swap to the second method,

I wonder if anyone of you explore the skin functions or options?

[Inspiron80]

The skin published in 26 Feb 2024 and mod to work with openpli from version 3.7, over 3000 visits of openpli users to thread page no one commented on Bitrates or report anything related to these subject,

Please have a look on it

Linuxsat-support.com

[DimitarCC]

The problem is that is not good practice to use precompiled binaries in skins (or at all). That always cause issues on one box or another. Are you saying you have tested all 20 brands that pli builds for and all the models so to prove that binary works?

I dont think so. So it is better to use plugin that is in the feed because it is built from source.... That is what is all about...

 

As for the "exploring" of skin functions and options...Well only users that use the skin do that. So you can expect feedback from them. BUt most of the users prefer install the skin from the feed and not installing detached ipk.

Edited by DimitarCC, 27 December 2024 - 20:05.

[WanWizard]

I can't comment on the skin (other than it is not for me, too wild and colourful), as long as I cannot install it. So lets get that out of the way first .

 

I've checked out the binary, it is an ARM ABI5 binary, requiring ld-linux-armhf, so it won't run on any box not using an ARM CPU, or not having that ld library. Which includes all boxes with a MIPS CPU.

 

So we can't include that. Ideally, the image should provide a renderer for bitrate information that skin developers can use, but I'm not a developer, so that's outside my responsability.

[Inspiron80]

The problem is that is not good practice to use precompiled binaries in skins (or at all). That always cause issues on one box or another. Are you saying you have tested all 20 brands that pli builds for and all the models so to prove that binary works?
I dont think so. So it is better to use plugin that is in the feed because it is built from source.... That is what is all about...
 
As for the "exploring" of skin functions and options...Well only users that use the skin do that. So you can expect feedback from them. BUt most of the users prefer install the skin from the feed and not installing detached ipk.

No, I didn't test it on all brands, but as I mentioned no one speak about anything related to Bitrates or crashes related to this subject, I used at beginning another Bitrates render working without opbitrate file and it work good with some boxes and not working with others but after using the opbitrate file, everything working good.

Again, I put two options for user to choose from, with and without Bitrates rendering, for this reason I asked if you guys explore the skin plugin to see the options list in it...

[DimitarCC]

 

Again, I put two options for user to choose from, with and without Bitrates rendering, for this reason I asked if you guys explore the skin plugin to see the options list in it...

 

 

That may work for end users, but can not work with build procedures so to add the skin in the feed. So to add the skin in the feed you need complete source code for everything including binaries. Obviously that cant happen with that binary since you don't have the source code for it.

And since it cant be built like that only way is that to be removed or skin to stay with ipk install only.

 

As for users that didnt report issues...well i doubt they used that on anything else than ARM boxes....

Edited by DimitarCC, 27 December 2024 - 20:18.

[Inspiron80]

Again, I put two options for user to choose from, with and without Bitrates rendering, for this reason I asked if you guys explore the skin plugin to see the options list in it...

 
That may work for end users, but can not work with build procedures so to add the skin in the feed. So to add the skin in the feed you need complete source code for everything including binaries. Obviously that cant happen with that binary since you don't have the source code for it.
And since it cant be built like that only way is that to be removed or skin to stay with ipk install only.
 
As for users that didnt report issues...well i doubt they used that on anything else than ARM boxes....

Well, without opbitrate file the render option will not work, but this will not impact skin function, so if you want to ignore the usr/bin/opbitrate file no problem,up to you.

From my side I will consider your point and search for another option without binary file,....

[DimitarCC]

Another potential problem is the python files (renderer and converters) that may conflict with another skin installed...

So its always good if that is used as less as possible and to to try to use what is already in the image as much as possible

[DimitarCC]

 

 

Again, I put two options for user to choose from, with and without Bitrates rendering, for this reason I asked if you guys explore the skin plugin to see the options list in it...

 
That may work for end users, but can not work with build procedures so to add the skin in the feed. So to add the skin in the feed you need complete source code for everything including binaries. Obviously that cant happen with that binary since you don't have the source code for it.
And since it cant be built like that only way is that to be removed or skin to stay with ipk install only.
 
As for users that didnt report issues...well i doubt they used that on anything else than ARM boxes....

Well, without opbitrate file the render option will not work, but this will not impact skin function, so if you want to ignore the usr/bin/opbitrate file no problem,up to you.

From my side I will consider your point and search for another option without binary file,....

 

Well if @WanWizard decides he can exclude the binary from the bitbake recipe in PLi. But that is not decision that i have to make

[Inspiron80]

Again, I put two options for user to choose from, with and without Bitrates rendering, for this reason I asked if you guys explore the skin plugin to see the options list in it...

 
That may work for end users, but can not work with build procedures so to add the skin in the feed. So to add the skin in the feed you need complete source code for everything including binaries. Obviously that cant happen with that binary since you don't have the source code for it.
And since it cant be built like that only way is that to be removed or skin to stay with ipk install only.
 
As for users that didnt report issues...well i doubt they used that on anything else than ARM boxes....

Actually it work on my old dreambox DM 520 which has MISP core...

[DimitarCC]

 

 

Again, I put two options for user to choose from, with and without Bitrates rendering, for this reason I asked if you guys explore the skin plugin to see the options list in it...

 
That may work for end users, but can not work with build procedures so to add the skin in the feed. So to add the skin in the feed you need complete source code for everything including binaries. Obviously that cant happen with that binary since you don't have the source code for it.
And since it cant be built like that only way is that to be removed or skin to stay with ipk install only.
 
As for users that didnt report issues...well i doubt they used that on anything else than ARM boxes....

Actually it work on my old dreambox DM 520 which has MISP core...

 

 

I believe DM520 is with BCM73265 SoC which appears to be ARM arch. Is not MIPS (as far as i know)....

DM500HD is MIPS arch....

But OpenPLi doesnt build for those anymore anyway

Edited by DimitarCC, 27 December 2024 - 20:35.

[Inspiron80]

Another potential problem is the python files (renderer and converters) that may conflict with another skin installed...
So its always good if that is used as less as possible and to to try to use what is already in the image as much as possible

All used renderers and Converters are customized for the skin, no way to conflict with another skin even in removal process,

Actually my target was not upload the skin to openpli feeds, my target was feedback from end users to check it out and report any issues they might have, openatv team upload the skin to their feeds without asking anything,sure if they has a problem reported from their users they will tell me

[DimitarCC]

All used renderers and Converters are customized for the skin, no way to conflict with another skin even in removal process,

 

 

As long as another skin provide the converter/renderer with same filename and/or class name (is not impossible)....

 

 

Actually my target was not upload the skin to openpli feeds, my target was feedback from end users to check it out and report any issues they might have, openatv team upload the skin to their feeds without asking anything,sure if they has a problem reported from their users they will tell me

 

 

Well the problem is OpenPLi is not OpenATV....And OpenPLi users prefer installing it from the feed. If they  not install it they cant report anything...

[Inspiron80]

Dear DimitarCC

If someone use any renderer or converter from my skin and didn't change the name of it, this is not my fault or something I can prevent, I am using other people work and no problem to use my work,

I mentioned OPENATV Feed to explain to you that, sure many users with different box architecture try it and sure if they have a problem they will report it somewhere,

Again, feel free to use it or not, I am not a developer as I mentioned before, let's make it simple, it is just a skin, if it make a problem with your device simply remove it, it will not explode your box

[WanWizard]

ATV have a different user base, it is much smaller than ours, and consists to a large extend of forum visiting geeks. Also, ATV doesn't care about whether or not an image or plugins are stable. You could put a virus or a bot in your ipk, and they would still publish it.

 

99% of OpenPLi users are regular end users, of the type your mom or dad. They wouldn't have a clue how to visit a forum or download an ipk, let alone know what an ipk was, or what to do when the box crashes (in most cases, it was bought or setup with OpenPLi, they don't know what flash is).

 

And we actively discourage people from downloading ipk's from an unknown source and installing those, as experience has learned most of them aren't OpenPLi compatible.

 

So we a different target audience, and have different requirements.

 

And to be clear, none of the comments here are to critisize, they are to help.

p.s. of all the images we make, 66 of them are for boxes with a MIPSEL based SoC.

 

[WanWizard]

Again, feel free to use it or not, I am not a developer as I mentioned before

 

You keep saying that, but if you are not, where does the code come from? If you haven't made it, it might be in use elsewhere. Most developers prefix their classes with something specific to them, to avoid collisions.

 

edit: the converters look very much like those from MCelliotG's Glamour skins...