Comments (16)
I found a solution for myself with the following settings. After that you might need to reset the icons in the "Channel / EPG" Tab.
from docker-tvheadend.
The Readme file (which can be seen on https://hub.docker.com/r/linuxserver/tvheadend) should be updated according to the screenshot.
And if wonder if it's possible to remove spaces by default from the icon names (because the default picons don't contain them)
from docker-tvheadend.
- there is already information, but it is wrong. just setting the path to "/picons" results in 404 errors
- my tvheadend config is older than this feature, that's why I have to do some things manually from time to time
about the names:
if I empty the user icon field of a channel or click "reset icon", it automatically gets a new value, for example "file:///picons/das%20erste%20hd.png". But such a file doesn't exist. instead, it should be "file:///picons/daserstehd.png"
from docker-tvheadend.
- it's a usability topic. saying "set the Channel icon path in Configuration --> General --> Base to "file:///picons/%C.png" " doesn't feel painful.
regarding the names: so what's the usual procedure? removing %20 from all channel icon paths manually? where does the /picons.tar.bz2 come from?
update: after starting a new tvheadend instance and copying the full block of config values from there it seems to work now, the default names don't have spaces anymore
from docker-tvheadend.
It seems I have the same issue. Picons are added in the "Channel / EPG" Tab and the Imagecache number is also increasing if you reset the image cache, however when opening the Imagecache URL direktly, I always getting a 404 file not found error. Maybe some file permission error?
from docker-tvheadend.
you don't have to map /picons
to host as they are included within the image.
from docker-tvheadend.
Created a pull for this issue. #110
from docker-tvheadend.
Why is it needed to add something to the Readme? The picon settings is set up automatically at first boot.
We use the picons from picons.xyz and the names comes from them.
from docker-tvheadend.
- There is no information to set it only to /picons. There is information about where to adjust the settings.
- We provide basic information for how to get this container to run, not how to set everything up. Refer to the tvheadend documentation for this.
Regarding the names, this is tvheadends domain and not something we have control over. We just package tvheadend into a container.
from docker-tvheadend.
Feel free to make a PR for the readme.
Picons are from picons.xyz as mentioned in the Readme.
from docker-tvheadend.
Why is it needed to add something to the Readme? The picon settings is set up automatically at first boot.
Migrating from a bare metal instance is a use case.
from docker-tvheadend.
update: after starting a new tvheadend instance and copying the full block of config values from there it seems to work now, the default names don't have spaces anymore
@daald Could you please post the correct values? I didn't manage to get rid of the spaces for the lookup. Thanks in advance!
from docker-tvheadend.
Got it with your screenshot!
For other readers: You can reset an existing icon url in the Configuration
-> Channel / EPG
tab (the last button in the toolbar: Reset icon
)
from docker-tvheadend.
Why is it needed to add something to the Readme? The picon settings is set up automatically at first boot.
Migrating from a bare metal instance is a use case.
That is something we don't test. We do not want to fill the readme with too much information. Setting up the picons should be looked up in the tvheadend documentation. The info in our readme is for getting the container up and running and not for configuring tvheadend.
from docker-tvheadend.
That is something we don't test. We do not want to fill the readme with too much information. Setting up the picons should be looked up in the tvheadend documentation. The info in our readme is for getting the container up and running and not for configuring tvheadend.
Why not writing it to a secondary documentation. It's still a difference from the tvheadend original settings, this is reason enough to be documented. Or just a link to that tvheadend documentation which I can't find. I only found two forum topics. but the path prefix file:///picons/
is clearly specific to this image anyway.
from docker-tvheadend.
That is something we don't test. We do not want to fill the readme with too much information. Setting up the picons should be looked up in the tvheadend documentation. The info in our readme is for getting the container up and running and not for configuring tvheadend.
Why not writing it to a secondary documentation. It's still a difference from the tvheadend original settings, this is reason enough to be documented. Or just a link to that tvheadend documentation which I can't find. I only found two forum topics. but the path prefix
file:///picons/
is clearly specific to this image anyway.
It's mentioned in the readme what the path to the picons are. The rest should be looked up in the tvheadend documentation, which is available in thveadend by clicking the help button. It's also the second hit on Google if you search for tvheadend documentation. https://docs.tvheadend.org/
We also have a short guide for setting up tvheadend with a dvb-t2 device in our blog, that also mentions picons setup.
https://blog.linuxserver.io/2017/02/19/how-to-set-up-tvheadend-with-your-dvb-t2-receiver/
We welcome all PRs, so feel free to open one of there is something missing. It does not guarantee that we will accept the PR though.
from docker-tvheadend.
Related Issues (20)
- [BUG] Cron not working HOT 2
- [FEAT] enable libxml2 HOT 10
- [BUG] PERL Module missing - DateTime::Format::Strptime module HOT 8
- New build has lost XMLTV internal grabber for Schedules Direct HOT 10
- [BUG] Crash when deleting multiple recordings HOT 3
- [BUG] Unresponsive and can't stop container HOT 4
- [BUG] d1366a06-ls152 broke vaapi amd transcoding on FC38 host HOT 7
- [BUG] XMLTV - tv_grab_zz_sdjson can't determine local timezone HOT 4
- [BUG] Memory increase while recording HOT 4
- JSON XS perl module missing HOT 1
- [BUG] Permissions issue on /recordings folder HOT 2
- [BUG] TV_grab_url permission HOT 7
- [BUG] Cannot use DVB-C HOT 3
- [FEAT] Allow for setting up username and password from docker-config HOT 2
- [BUG] Picons are out of date HOT 10
- [FEAT] IPv6 Support HOT 4
- How to support IPv6 network video sources? HOT 6
- tvheadend docker recording problem files over 2GB[BUG] <title> HOT 3
- [FEAT] Compile libdvbcsa with icam support HOT 4
- [FEAT] Execute command after upgrading docker image HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from docker-tvheadend.