All the full resolution channel logos and their link to the actual channel (=serviceref) are kept up2date in this repository. The end result are picons for Enigma2 tuners and Kodi mediacenter in combination with a compatible PVR backend.
Ubuntu and Cygwin on Windows are tested and supported platforms for building the picons.
Download the repository by using the following command:
git clone https://github.com/picons/picons-source.git /tmp/picons-source
Next, copy the required files to the folder build-input.
We will start the creation of the servicelist and the picons with the following commands:
cd /tmp/picons-source
./1-build-servicelist.sh
./2-build-picons.sh
Take a look at the folder build-output for the results.
TIP: To automate the building process, you can also use some of the following commands:
./1-build-servicelist.sh snp
./1-build-servicelist.sh srp
./2-build-picons.sh snp
./2-build-picons.sh srp
./2-build-picons.sh snp-full
./2-build-picons.sh srp-full
So you would like to contribute? Have a look here, just so you'll know the rules.
The idea behind SNP is that a simplified name derived from the channel name is used to lookup a channel logo. The idea and code was first implemented by OpenVIX for the Enigma2 tuners. Any developer currently using the serviceref method as a way to lookup a logo and would like to implement this alternative, can find the code used to generate the simplified name at the OpenVIX github repository.
Copy your enigma2 folder, probably located in /etc on your box into this folder.
TvHeadend users, have two options:
-
Use the server generated configuration files by copying your
tvheadendconfiguration folder, probably located in/home/hts/.htson your server into this folder. -
Use the servers API and directly ask the server about all channels by creating a file called
tvheadend.serverconf.
The first option has the advantage to work even without a running server. The advantage of the second option is that you don't have to copy files around, automatically you'll have the most accurate channel list and it's about 20% faster.
The file tvheadend.serverconf can contain the following values:
# hostname or ip address of tvheadend server (default: "localhost")
TVH_HOST="localhost"
# port of tvheadend API (default: 9981)
TVH_PORT="9981"
# tvheadend user name
TVH_USER=""
# tvheadend password of above user
TVH_PASS=""Only the values which are different from the default values are required. For most people this will be a file with a single host name or host IP address.
TVH_HOST="my.tvheadend.server"If you're running TvHeadend on the same machine, even an empty file (defaulting to localhost) should be sufficient.
If you're using VDR together with the Kodi addon xvdr, copy your channels.conf file to this folder.
A file backgrounds.conf should be placed in this folder. If no file is found, the default file will be used.
Syntax:
<resolution>;<resolution-padding>;<logotype>;<background>
Example:
# My own awesome settings
100x60;86x46;dark;reflection
100x60;100x60;default;transparent
100x60;100x60;light;transparent
# My commented settings
#800x450;800x450;light;transparent
This folder will contain the output from the build. Similar to the files servicelist-enigma2-snp and servicelist-enigma2-srp. The picon binaries are also saved in this folder.
Possible output files and folders:
binaries-snp/
binaries-srp/
servicelist-enigma2-snp
servicelist-enigma2-srp
servicelist-tvheadend-filemode-snp
servicelist-tvheadend-filemode-srp
servicelist-tvheadend-servermode-snp
servicelist-tvheadend-servermode-srp
servicelist-vdr-snp
servicelist-vdr-srp
This is where all the channel logos go and how they are linked to the serviceref or a simplified version of the name. Backgrounds and the default backgrounds.conf file can also be found in this directory.
Some additional scripts used by the main scripts.