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.
BUILDING THE PICONS
When using Bash on Ubuntu on Windows, clone to
/mnt/c, which is your
C:\ drive on Windows. That way you can manipulate your files from within Windows, going to
%localappdata%\lxss\rootfs directly inside Windows and modifying files, is not recommended.
Download the repository by using one of the following commands:
# Ubuntu, Bash on Ubuntu on Windows sudo apt-get install git binutils pngquant imagemagick librsvg2-bin jq # Ubuntu git clone https://github.com/picons/picons-source.git ~/picons-source # Bash on Ubuntu on Windows git clone https://github.com/picons/picons-source.git /mnt/c/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:
# Ubuntu cd ~/picons-source # Bash on Ubuntu on Windows cd /mnt/c/picons-source # Ubuntu, Bash on Ubuntu on Windows ./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
SNP - SERVICE NAME PICONS
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.
Enigma2 servicelist creation
enigma2 folder, probably located in
/etc on your box into this folder.
TvHeadend servicelist creation
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
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.
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.
If you're running TvHeadend on the same machine, even an empty file (defaulting to
localhost) should be sufficient.
Note: In order to make the generator work with TvHeadend, you'll need to enable picons first by defining a path to the future picon folder under Configuration -> General -> Base.
VDR servicelist creation
If you're using VDR together with the Kodi addon xvdr, copy your
channels.conf file to this folder.
Configuring which backgrounds to build
backgrounds.conf should be placed in this folder. If no file is found, the default file will be used.
# My own awesome settings 100x60;86x46;dark;reflection 100x60;100x60;default;transparent 100x60;100x60;light;transparent # My commented settings #800x450;800x450;light;transparent
Possible output files and folders:
binaries-snp/ binaries-srp/ servicelist-enigma2-snp.txt servicelist-enigma2-srp.txt servicelist-tvheadend-filemode-snp.txt servicelist-tvheadend-filemode-srp.txt servicelist-tvheadend-servermode-snp.txt servicelist-tvheadend-servermode-srp.txt servicelist-vdr-snp.txt servicelist-vdr-srp.txt
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 files.