Tvheadend

Can you help me ?

Hi,

I had today the same Question.
I checked the code in the GIT-Project and found this Commit:
https://github.com/tvheadend/tvheadend/commit/0b3fcdce580187227bc9f305b03f34d521c7300b

channel: added support for getting icons from underlying services

Also added an initial implementation of picon support.

So I think there is or it will come a service which loads or create the channel logo.

Edit: Maybe this is what you/we search: http://picons.bitbucket.org/howto.html

Best Regards,
Datafreak

Can you help me how i cane use it on my Synology NAS with Debian CHroot 7.4 ?

Give me instrukcjion step by step how run it...

Here a short Howto to generate the Picons:

1. Install some packages in the Debian/Ubuntu way.
   

   $ sudo apt-get install librsvg2-bin imagemagick pngnq tar bzip2 p7zip p7zip-full
   

2. Download the Repository from http://picons.bitbucket.org/.
   

   $ wget "https://bitbucket.org/picons/logos/get/34aab6ba9cbd.zip" 
   

3. Extract the Repository
   

   $ unzip 34aab6ba9cbd.zip
   

4. Building the picons
   

   $ cd picons-logos-34aab6ba9cbd/
   $ ./build.sh build
   

5. You find the binaries here:
   

   /tmp/picons-binaries
   

1. Unpack want you want to use (example hd.reflection-black).
   

   $ tar xfvj hd.reflection-black_*.tar.bz2
   

2. Move it to a usefull path:
   

   $ mkdir /home/hts/picons
   $ mv hd.reflection-black_*/* /home/hts/picons
   $ chown -R hts:hts /home/hts/picons/
   

3. Update the Picon path in the Configurations
   

   file:///home/hts/picons
   

• picons-binaries.7z

• hd.black-white_2014-10-19--21-09-17.7z
• hd.blue-black_2014-10-19--21-09-17.7z
• hd.reflection-black_2014-10-19--21-09-17.7z
• hd.transparent-black_2014-10-19--21-09-17.7z
• hd.transparent-white_2014-10-19--21-09-17.7z
• hd.white-black_2014-10-19--21-09-17.7z
• sd.black-white_2014-10-19--21-09-17.7z
• sd.blue-black_2014-10-19--21-09-17.7z
• sd.reflection-black_2014-10-19--21-09-17.7z
• sd.transparent-black_2014-10-19--21-09-17.7z
• sd.transparent-white_2014-10-19--21-09-17.7z
• sd.white-black_2014-10-19--21-09-17.7z
• shd.black-white_2014-10-19--21-09-17.7z
• shd.blue-black_2014-10-19--21-09-17.7z
• shd.reflection-black_2014-10-19--21-09-17.7z
• shd.transparent-black_2014-10-19--21-09-17.7z
• shd.transparent-black-nopadding_2014-10-19--21-09-17.7z
• shd.transparent-white_2014-10-19--21-09-17.7z
• shd.transparent-white-nopadding_2014-10-19--21-09-17.7z
• shd.white-black_2014-10-19--21-09-17.7z

• picons-binaries.bz2

• hd.black-white_2014-10-19--21-09-17.tar.bz2
• hd.blue-black_2014-10-19--21-09-17.tar.bz2
• hd.reflection-black_2014-10-19--21-09-17.tar.bz2
• hd.transparent-black_2014-10-19--21-09-17.tar.bz2
• hd.transparent-white_2014-10-19--21-09-17.tar.bz2
• hd.white-black_2014-10-19--21-09-17.tar.bz2
• sd.black-white_2014-10-19--21-09-17.tar.bz2
• sd.blue-black_2014-10-19--21-09-17.tar.bz2
• sd.reflection-black_2014-10-19--21-09-17.tar.bz2
• sd.transparent-black_2014-10-19--21-09-17.tar.bz2
• sd.transparent-white_2014-10-19--21-09-17.tar.bz2
• sd.white-black_2014-10-19--21-09-17.tar.bz2
• shd.black-white_2014-10-19--21-09-17.tar.bz2
• shd.blue-black_2014-10-19--21-09-17.tar.bz2
• shd.reflection-black_2014-10-19--21-09-17.tar.bz2
• shd.transparent-black_2014-10-19--21-09-17.tar.bz2
• shd.transparent-black-nopadding_2014-10-19--21-09-17.tar.bz2
• shd.transparent-white_2014-10-19--21-09-17.tar.bz2
• shd.transparent-white-nopadding_2014-10-19--21-09-17.tar.bz2
• shd.white-black_2014-10-19--21-09-17.tar.bz2

• picons-binaries.ipk.zip

• enigma2-plugin-picons-tv-ocram.hd.black-white_2014-10-19--21-09-17_all.ipk
• enigma2-plugin-picons-tv-ocram.hd.blue-black_2014-10-19--21-09-17_all.ipk
• enigma2-plugin-picons-tv-ocram.hd.reflection-black_2014-10-19--21-09-17_all.ipk
• enigma2-plugin-picons-tv-ocram.hd.transparent-black_2014-10-19--21-09-17_all.ipk
• enigma2-plugin-picons-tv-ocram.hd.transparent-white_2014-10-19--21-09-17_all.ipk
• enigma2-plugin-picons-tv-ocram.hd.white-black_2014-10-19--21-09-17_all.ipk
• enigma2-plugin-picons-tv-ocram.sd.black-white_2014-10-19--21-09-17_all.ipk
• enigma2-plugin-picons-tv-ocram.sd.blue-black_2014-10-19--21-09-17_all.ipk
• enigma2-plugin-picons-tv-ocram.sd.reflection-black_2014-10-19--21-09-17_all.ipk
• enigma2-plugin-picons-tv-ocram.sd.transparent-black_2014-10-19--21-09-17_all.ipk
• enigma2-plugin-picons-tv-ocram.sd.transparent-white_2014-10-19--21-09-17_all.ipk
• enigma2-plugin-picons-tv-ocram.sd.white-black_2014-10-19--21-09-17_all.ipk
• enigma2-plugin-picons-tv-ocram.shd.black-white_2014-10-19--21-09-17_all.ipk
• enigma2-plugin-picons-tv-ocram.shd.blue-black_2014-10-19--21-09-17_all.ipk
• enigma2-plugin-picons-tv-ocram.shd.reflection-black_2014-10-19--21-09-17_all.ipk
• enigma2-plugin-picons-tv-ocram.shd.transparent-black_2014-10-19--21-09-17_all.ipk
• enigma2-plugin-picons-tv-ocram.shd.transparent-black-nopadding_2014-10-19--21-09-17_all.ipk
• enigma2-plugin-picons-tv-ocram.shd.transparent-white_2014-10-19--21-09-17_all.ipk
• enigma2-plugin-picons-tv-ocram.shd.transparent-white-nopadding_2014-10-19--21-09-17_all.ipk
• enigma2-plugin-picons-tv-ocram.shd.white-black_2014-10-19--21-09-17_all.ipk

Best Regards,
Datafreak

Ok i do this but what next ?

HowTo is updated.
See Usage.

Where see usage ?

I set in tvheadend path to picons where is the files which you see in previous post. But nothing.

Hi Piotr,

it worked in my case (I use the las Version build from GIT HTS Tvheadend 3.9.1901~g43e805d). Maybe your system is different.
Maybe it helps to reload the tvheadend service (/etc/init.d/tvheadend restart) or to clear you Brower cache.

Here my settings:

and here the Icon:

Best Regards,
Datafreak

in path file:///home/hts/picons you have all generated file ipk and tar.bz2 and 7z ?

No, please read and follow the usage steps in my HowTo.
As I wrote, I updated my HowTo.

In my example it looks like this:

I do this step by step as you describe but nothing. Restarted TVHEADEND. I have a Debian Chroot 7.4

hts@Synology_DS713:~$ /home/hts/picons# ls -lah | head
-bash: /home/hts/picons#: No such file or directory
hts@Synology_DS713:~$

The message says "No such file or directory". This means something was not found or maybe you have not the right to access it.
Maybe you got an error or so after on of the steps.

As I wrote, you use a different system so maybe the steps on your system are also different.
So you have to find your own work to get it to run.

Ok
I search ikon in folder /home/hts/picons for channel TVP Polonia. This icon name has: 1_0_1_5A46_E7_270F_FFFF0000_0_0_0.png

In TVHeadend path to picons for this channel has: picon://1_0_16_21_3_2268_EEEE0000_0_0_0.png

It is diferent. I changed to: picon://1_0_1_5A46_E7_270F_FFFF0000_0_0_0.png and it works.

But why name was different ?

I can not tell you, why the name is different.
Maybe there was a bug and it is fixed. Please try the last version from Git.

I use latest git.

maybe i should send an issue...

That i post to add this function...

https://tvheadend.org/issues/2393

It is propably problem that i use TV Cabel which stream in DVB-T. Yes DVB-T not DVB-C

I used the howto to add the picons. That worked very well. I can see the I icons within the EPG.
But how do I access these I icons from outside? The iconname is provided by icon_url. But which http path has to be accessed?

'access... from outside'? How do you mean?

XBMC will - for example - ask tvheadend for the icons. Also, anything else can still point to the underlying icons through a URI or folder/directory path dependent on where you've put them and what protocols you're using.

Thanks Data Freak for the great guide. Does anyone know if picons like these have been created for radio stations?

DVB-T, same issue (different image name) here:

"Canale 5", picon image is

1_0_1_2_3DE_110_820000_0_0_0.png

but tvh automatically generated one is

picon://1_0_1_FA5_3AC_110_EEEE0000_0_0_0.png

I also have this problem. And i dont use picon and i use png file on local disk.

I have similar problem. The generated picon filenames do not match with the filnames in downloaded picon set. In my case the problem is with satellites on west side.

I found this explanation of picon filename:

_What does an example file name pointing to the .png file look like? 1_0_1_957_327B_3277_6400000_0_0_0.png = the Plicon of 1600e_golden_west_network.png

• The file name, what does it mean?

1 = reftype, fixed
0 = flags, fixed
1 = servicetype (1=tv)
957 = SID
327B = transponder id
3277 = network id
6400000 = namespace (orbital position 1600 --> 640 hex)
0 = parent SID
0 = parent transponder id
0 = unused_

In my case the Thor 0,8W picons have generated filename like this: 1_0_1_7601_2BE_600_FFF70000_0_0_0.png
The downloaded is: 1_0_1_7601_2BE_600_E0800000_0_0_0.png

The difference is that TVH assigns FFF7 -> (-9 decimal?) while the picon has E08 -> 3592 (359.2 degree East)
So the problem is with the calculation of orbital position. This is a bug.

0xFFF7 is decimal 65527, or suspiciously 8 off 65535 (0xFFFF). Does that thus correspond to 0.8, i.e. it's generating 0.8W versus 359.2E?

Is that what you concluded, that picon orbital position should always be specified as east of Greenwich, yes?

I've been searching the web for some definitive guide to naming ... I've failed to find anything ...

Hi,

-8 should be FFF8.
Yes, I think the problem is in 0.8W versus 359.2E.

Anyway, my conclusion is empirical. Picons with E08 (359,2E) are working in Enigma. I assume that this is the right way of calculation. On the other hand, according to the reference above, only the first 3 digit of namespace shows the orbital position.

So I think that the calculation should be modified to always use position as east of Greenwich.

Is there an open ticket for this issue (wrongly generated picon filename)?
Should I open one?