Forums » Kodi (XBMC) as frontend »
any way to disable "User Icon" on tvheadend unstable?
Added by Oliver Stange about 10 years ago
good evening to everybody
i have the following problem:
i have set picons in xbmc, and they working nicely
but now tvheadend overwrite they with the "User Icon"
when i remove all this entries in channel tab and reinitialize the xbmc gui my picons are back
but the problem is, when tvheadend restarts the "User Icon" entries are all back and my picons are gone
is there any way to stop this behavior?
thanks!
Replies (10)
RE: any way to disable "User Icon" on tvheadend unstable? - Added by Chris Koster about 10 years ago
Same problem here. HAve you found a way to disable the icon in TVH?
RE: any way to disable "User Icon" on tvheadend unstable? - Added by Prof Yaffle about 10 years ago
Explain slowly, please. Does tvh have icons set? Are those the ones overriding XBMC's (in which case it may be an XBMC config issue)? Or is this a clash between channel icons and picons in tvh?
I think that tvh will over-rule XBMC if it has an icon set. So, remove them in tvh and then XBMC is the only thing that knows anything, so it'll use whatever you told it to.
But I might have the wrong end of the stick entirely...
RE: any way to disable "User Icon" on tvheadend unstable? - Added by Chris Koster about 10 years ago
It seems TVH automatically downloads (p)icons and i'd like to turn that functionality off. I think you are right in the assumption that TVH icons override the XBMC icons. In XBMC I configured a folder with correct icons. I go those from github as they already have the right filenames and all the icons for my cable provider (Ziggo) are in there.
Since I started using the latest unstable TVH no icons are visible in XBMC anymore. I have tried to find a setting in XBMC and in TVH to use my own icons but can't find anything. Besides that my whole TVH log is filled with entries about TVH constantly downloading all icons. It gives entries as following:
2014-11-02 21:18:53.130 HTTP: 192.168.0.114: /1_0_19_89C_1A_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:18:53.150 HTTP: 192.168.0.114: /1_0_19_89C_1A_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:18:53.170 HTTP: 192.168.0.114: /1_0_19_89C_1A_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.098 HTTP: 192.168.0.114: /1_0_19_7149_1D_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.116 HTTP: 192.168.0.114: /1_0_19_714A_1D_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.135 HTTP: 192.168.0.114: /1_0_19_714B_1D_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.154 HTTP: 192.168.0.114: /1_0_19_89C_1A_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.173 HTTP: 192.168.0.114: /1_0_19_6592_1A_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.192 HTTP: 192.168.0.114: /1_0_19_6593_1A_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.210 HTTP: 192.168.0.114: /1_0_19_7D01_20_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.230 HTTP: 192.168.0.114: /1_0_1_1771_6_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.247 HTTP: 192.168.0.114: /1_0_19_8A0_20_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.267 HTTP: 192.168.0.114: /1_0_19_7D03_20_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.284 HTTP: 192.168.0.114: /1_0_19_D2_3_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.302 HTTP: 192.168.0.114: /1_0_19_100_2_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.320 HTTP: 192.168.0.114: /1_0_19_F0_B_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.338 HTTP: 192.168.0.114: /1_0_19_EF_16_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.356 HTTP: 192.168.0.114: /1_0_19_7533_1E_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.374 HTTP: 192.168.0.114: /1_0_1_1B6D_7_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.392 HTTP: 192.168.0.114: /1_0_19_5DC2_18_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.410 HTTP: 192.168.0.114: /1_0_19_D7_16_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.428 HTTP: 192.168.0.114: /1_0_1_D5_9_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.445 HTTP: 192.168.0.114: /1_0_1_2EE4_C_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.465 HTTP: 192.168.0.114: /1_0_19_7531_1E_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.482 HTTP: 192.168.0.114: /1_0_19_1776_6_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.500 HTTP: 192.168.0.114: /1_0_1_7D3_2_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.517 HTTP: 192.168.0.114: /1_0_1_FA5_4_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.535 HTTP: 192.168.0.114: /1_0_1_FA4_4_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.554 HTTP: 192.168.0.114: /1_0_1_BBF_3_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.572 HTTP: 192.168.0.114: /1_0_1_BC3_3_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.589 HTTP: 192.168.0.114: /1_0_1_B7_F_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.606 HTTP: 192.168.0.114: /1_0_1_BBB_3_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.625 HTTP: 192.168.0.114: /1_0_1_59DC_17_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.642 HTTP: 192.168.0.114: /1_0_1_EE_12_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.662 HTTP: 192.168.0.114: /1_0_1_FA6_4_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.679 HTTP: 192.168.0.114: /1_0_1_7D05_20_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.698 HTTP: 192.168.0.114: /1_0_1_DA_F_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.715 HTTP: 192.168.0.114: /1_0_1_1773_6_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.734 HTTP: 192.168.0.114: /1_0_1_3A9E_F_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.751 HTTP: 192.168.0.114: /1_0_1_ED_1A_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.769 HTTP: 192.168.0.114: /1_0_1_99_1F5_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.787 HTTP: 192.168.0.114: /1_0_1_384_64_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.803 HTTP: 192.168.0.114: /1_0_1_64_64_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.822 HTTP: 192.168.0.114: /1_0_1_C8_64_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.839 HTTP: 192.168.0.114: /1_0_1_190_64_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.858 HTTP: 192.168.0.114: /1_0_1_1F4_64_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.875 HTTP: 192.168.0.114: /1_0_1_80EC_21_1F4_FFFF0000_0_0_0.png -- 1 2014-11-02 21:19:00.893 HTTP: 192.168.0.114: /1_0_1_B2_16_1F4_FFFF0000_0_0_0.png -- 1
In the channel list overview I have a column with picon urls:
[img]http://img.positivum.nl/HTS_Tvheadend_3.9.1972g9bb73c1trusty_2014-11-02_21-24-26.png[/img]
Would be nice if a user can disable the whole picon functionality in TVH
RE: any way to disable "User Icon" on tvheadend unstable? - Added by Prof Yaffle about 10 years ago
Delete the picon path in Configuration -> General
Select the channels in Configuration -> Channels/EPG -> Channels and click 'reset icon'
... you should now not have any picons assigned, and have no way to get new ones.
RE: any way to disable "User Icon" on tvheadend unstable? - Added by Chris Koster about 10 years ago
Thanks but I don't have any picon path configured in Configuration -> General
'Reset icon' in in Configuration -> Channels/EPG -> Channels does nothing. It doesn't clear any of the picon paths/urls. It also doesn't give any error or log entry.
RE: any way to disable "User Icon" on tvheadend unstable? - Added by Chris Koster about 10 years ago
Ah sorry, of course I had to select the channels first. Thing is when I select all channels, click reset icon and save the config.
Almost immediatly after i've the channels without picon urls, the picons get fetched again and set in channel config.
RE: any way to disable "User Icon" on tvheadend unstable? - Added by Prof Yaffle about 10 years ago
Odd - I just tested on one icon on mine (3.9.1987~gc053acd) and it seemed to work fine. And your installation must be getting the picons from somewhere - tvh has no knowledge (as far as I know!) of some universal website full of icons.
More testing... yes, I see what you mean. I can remove a user (file://) icon, and I immediately get the picon. If I disable picons, this makes now difference and the picon:// path still appears. I switched off image caching, but that made no difference: I didn't clean my image cache, though, which may be relevant.
It could be a bug, or it could be something getting cached so it survives to be used again. Thoughts include removing the picon path, disabling and clearing the cache and restarting tvh before resetting the icons - or simply deleting the picons you have downloaded, as they're clearly stored somewhere where your tvh instance can find them.
RE: any way to disable "User Icon" on tvheadend unstable? - Added by Chris Koster about 10 years ago
Well I think it's a bug. I'm using almost the same version (3.9.1972~g9bb73c1~trusty). I did clear my image cache and it doesn't make any difference.
There should be a switch to turn of the usage of picons in TVH alltogether. I don't where TVH gets the image from now but they aren't the ones that I cloned from github myself. Those files are in a folder outside the reach of TVH, have different filenames and have data inside them. All the TVH ones are blank images.
The only weird thing is, one might think a user could define in XBMC where to get the channel images from. I defined the correct image path in XBMC but the incorrect TVH picons gets used nonetheless.
RE: any way to disable "User Icon" on tvheadend unstable? - Added by Prof Yaffle about 10 years ago
If they're blank, then that explains one thing - it's not generating images, or getting them from anywhere - it's generating the path, but it doesn't lead anywhere if you don't have a picon directory defined.
However, yes, otherwise it sounds like a bug. I can't see any open issues concerning picons, so please open a new one.
RE: any way to disable "User Icon" on tvheadend unstable? - Added by Chris Koster about 10 years ago
Alright, will do tonight. Thanks for the help