[Info] Chocholousek picons (Enigma2 plugin)

Nachricht

#21

if you wish i can try to prepare bitbake recipe both for 6.4 and 6.5

s3n0 · #22

For what purpose do you mean creating that "bitbake" ? Do you mean that it is possible to use ChocholousekPlugin with ".pyo" files and not with ".py" files ?

If the situation with "__cache __ /*.cpython-38.pyc" files is only temporary solution under the alpha version, then I don't think it will interfere for a short time. But if it has to stay that way in the final version of OpenATV 6.5, then bitbake is a better solution.

#23

bitbake is buildsystem (openembedded) tool which builts ipks, image, feeds, etc. see GitHub - oe-alliance/oe-alliance-core: The openembedded alliance core. for example recipe (.bb) files. 6.4 images are built from 4.4 branch 6.5 from nextp3 branch.

#24

s3n0 hat geschrieben:Hi. Thanks for the info. The plugin is of course open source. I have it on my github. The OpenATV team of developers can safely insert as a fork from my github (e2plugins/ChocholousekPicons at master . s3n0/e2plugins . GitHub) if it is possible... I don't know. However, I will definitely leave the source code files in the next version of the ChocholousekPicons plugin for the time being, due to the smooth running in OpenATV-6.5 alpha version.

4.0.210130
For the needs of OpenATV-6.5 alpha version (based on Python 3.8.x), ".py" files are inserted into the installation package instead of ".pyo" files.

(download the plugin and more information can be found in the post #1)

Now ok with ATV 6.5 and 6.4 wenn I install it with the last Update from Today
wget -qO- --no-check-certificate "https://github.com/s3n0/e2plugins/raw/master/ChocholousekPicons/online-setup" | bash -s install

Install on ATV 6.4:

root@axashis4kcombo:~# wget -qO- --no-check-certificate "https://github.com/s3n0/e2plugins/raw/master/ChocholousekPicons/online-setup" | bash -s install
Removing enigma2-plugin-extensions-chocholousek-picons (4.0.210130) from root...
*********************************************************
Chocholousek picons - plugin ver.4.0.210130
Enigma2 plugin/extensions
by s3n0 , 2018-2021
*********************************************************
Successfully REMOVED. You should restart Enigma2 now.
*********************************************************
Installing enigma2-plugin-extensions-chocholousek-picons (4.0.210130) on root.
Configuring enigma2-plugin-extensions-chocholousek-picons.
*********************************************************
Chocholousek picons - plugin ver.4.0.210130
Enigma2 plugin/extensions
by s3n0 , 2018-2021
*********************************************************
Successfully INSTALLED. You should restart Enigma2 now.
*********************************************************

Install on ATV 6.5:

root@mutant51:~# wget -qO- --no-check-certificate "https://github.com/s3n0/e2plugins/raw/master/ChocholousekPicons/online-setup" | bash -s install
No packages removed.
Installing enigma2-plugin-extensions-chocholousek-picons (4.0.210130) on root.
Configuring enigma2-plugin-extensions-chocholousek-picons.
*********************************************************
Chocholousek picons - plugin ver.4.0.210130
Enigma2 plugin/extensions
by s3n0 , 2018-2021
*********************************************************
Successfully INSTALLED. You should restart Enigma2 now.
*********************************************************

s3n0 · #25

Nicker hat geschrieben:bitbake is buildsystem (openembedded) tool which builts ipks, image, feeds, etc. see GitHub - oe-alliance/oe-alliance-core: The openembedded alliance core. for example recipe (.bb) files. 6.4 images are built from 4.4 branch 6.5 from nextp3 branch.

I know what bitbake is, but I don't know what you want to do with it

.

#26

to build ipk from yours repo sources, so that anybody can install (and update) it from feeds later.

s3n0 · #27

So, it is probably enough to take the created IPK file and move it to the "feed" server for OpenATV 6.5. IPK file works now. So... if I put ".py" files directly into the installation package instead of ".pyo" files. Or does the IPK file have to be built differently ? Anyway, you can do it if you want ... :). It does not matter.

However, in the plugin's source code, detection and installation of a new version of the plugin is performed by detecting the new version on the GitHub server and then installing the downloaded new IPK file from the internet - from the GitHub server - if a newer version is found. So when updating to a new version of the plugin, I'm not using a feed source, but a GitHub source. And, of course, it is only a manual detection and installation of a new version (the user confirms with the button any detection and then also update of the plugin).

Of course, I'm happy even though the Chocholousek Picons plugin is part of the feed for OpenATV 6.4 :).

e2plugins/ChocholousekPicons at master . s3n0/e2plugins . GitHub

s3n0 · #28

4.0.210214
Add log output to the file "/tmp/chocholousek-picons.log", while updating picons.
Added testing of the connection to the server, which contains picon packages, after testing the internet connection.
Minor syntax modification according to PEP8 E251.
Renaming some functions (source code) to make them clearer.

(download the plugin and more information can be found in the post #1)

GH_162 · #29

Thank you for this useful plugin.
Is it possible to add another update method as "Sync with lamedb"?
This way we can have more picons, but not those unnecessary ones of channels that we cannot receive in some satellites?
Thanks in advance.

s3n0 · #30

Hi.

The lamedb file contains a database of all available channels and transponders (since the last search for stations on the set-top box tuners).

Userbouquet files are a list of your own channels that you only watch.

The channels in the lamedb database you do not watch all of them, but only those that are in the userbouquet files. So that would be unnecessary. You would also have a lot of picon (.png files) on the local disk in the set-top box. If you are not bothered by many picons (.png files), do not use the picon update synchronization method. Simply use the method of copying the whole packages (all their contents of all picons) for one whole satellite - depending on which satellite positions you have activated in the configuration of the ChocholousekPicons plugin.

GH_162 · #31

s3n0 hat geschrieben: If you are not bothered by many picons (.png files), do not use the picon update synchronization method. Simply use the method of copying the whole packages (all their contents of all picons) for one whole satellite - depending on which satellite positions you have activated in the configuration of the ChocholousekPicons plugin.

Hi,
Thanks for your reply.
I receive 20 sats with a T90 dish.
Normally, after having downloaded one by one all 20 picon files, I extract them all in a folder called "picon" in PC.
I open Dreamboxedit and receive files from the box.
Then there's an option in Edit menu: "Remove all unused picons (checks lamedb and user bouquets)"
After that, the amount of picons goes down to 9380, from almost 28000!
And finally, I transfer those 9380 to the picon folder in the box.
This plugin is great as it makes this process automatically, but it would be much better if we could have picons for all available channels, excluding all those unnecessary ones that are in majority.

s3n0 · #32

Hi.

Of course it can be added to the plugin. The question is whether this matters at all. The original purpose of my plugin was to develop an algorithm that will load only the really needed picons. And unnecessary picons are deleted - the plugin also contains the entire algorithm for the purpose of deleting unnecessary picons.

What you want, I don't think it makes sense.

There may be a situation where a completely new channel is added - i.e. with new tuner data (transponder, frequency, PID, ...). And in this case, you have to start the plugin again and update (download) the picons from the internet again, even for the new channel. So the synchronization with lamedb is insignificant.

Now it is so that there you have one option to load all the picons in the set-top box or the other option to load only the necessary picons according to the userbouquet files. What would be the third option - something in between ? You will still have to update the picons again and again if another new channel is added in the meantime. So it doesn't make sense to upload all the picons in the set-top box, as well as to upload the picons according to lamedb (almost all the picons).

It has its justification. That yes. It also has its meaning - to use the lamedb database. However, this only applies if you completely delete some channels from your lists and later re-add them. In this case, the icon remains stored on the internal disk, according to the lamedb file.

Well, I don't know .... I'm thinking about it yet

.

GH_162 · #33

Hi,
Thanks again for detailed info.
You certainly have a point about the logic of lamedb in general.
I try to keep mine clean and actual, by removing all channels on ceased frequencies etc. but there are probably very few people doing this, so my case is surely an exception.

Whether you decide to add this extra option or not, this plugin will still be one of my favourites, thank you once more for this great job.

#34

created bb recipe and added to openatv-feeds:
enigma2-plugin-extensions-chocholousek-picons - created bb recipe and… . nickersk/oe-alliance-core@28b8f38 . GitHub

s3n0 · #35

4.0.210301
Improved Lithuanian language from 2021-02-16 (thx to @Adga).
Fixed a minor bug in the sorting of database files in a folder:
- the error could theoretically cause the database update of available picons to be stuck
- so sorting files by algorithm is now alphabetical, not by creation date
Created and added a new bb-recipe to OpenATV feeds (thx to @Nicker):
- https://github.com/nickersk/oe-alliance ... 713dad54b9
- https://github.com/oe-alliance/oe-allia ... v-feeds.bb
- https://github.com/oe-alliance/oe-allia ... -picons.bb

(download the plugin and more information can be found in the post #1)

#36

@s3n0,
can you please take a look with your Plugin on ATV 6.5,I think there is an error,because with ATV 6.4 I can see your Plugin on Feed,but with ATV 6.5 I can´t see it.

s3n0 · #37

@Gio60 :

The version of oATV 6.5 is still in the alpha version. You are probably using an old build with a strict feed. The update of the offline package list probably doesn't work, according to the online feed:

Code: Alles auswählen

opkg update

I really don't know. Sorry. Simply put, version 6.5 is for developers and testers only. Not for regular users.

If you want to use this plugin, install it manually via Shell (by downloading the installation package from my github). But first, don't forget to uninstall your current version:

Code: Alles auswählen

opkg remove enigma2-plugin-extensions-chocholousek-picons

#38

Sorry,for me is not a problem, I have your actuell Plugin Version on my PC and it works on ATV 6.5 without problems, normally when a Plugin works on ATV 6.5 it is in the Feed too.

s3n0 · #39

@Gio60 :

OK then. But I dont understand... where exactly is the problem ?

The new version of the plugin is missing on the oATV 6.5 feed server ?

#40

Yes, and we are looking to fix this, I hope tomorrow it's on ATV 6.5 OK too.