I’m not sure when this got installed – it might have been installed with tvheadend. This causes tvheadend to uses a program in /usr/bin called tv_grab_na_dd. In “Internal Grabber” I picked “XMLTV: North America (Data Direct)”. In the general config I recommend don’t set “update channel name” because that overwrites the tvheadend “name” field, which I’d like to modify occasionally. In tvheadend: configuration->Channel/EPG->EPG Grabber is where one sets that up. Now tvheadend can be configured to get that data. I picked what geographical area I want a guide for, by zip code). I enrolled at their website, and then set up a “lineup” (i.e. There are (I think) options to get some EPG stuff for free, but I chose to use the service, which costs $25/yr. When that is all done, kodi can communicate with the backend, and it will enable the “TV” (some skins call it “Live TV”) entry in the Kodi main menu. It has to be given a userid/password, and the ip address and port number where to reach the tvheadend backend server (on cinnamon in my case). ![]() Then configuring it in system->settings->tv. This requires activating the pvr client (after installing it first if you are on linux). Once this is set up, Kodi can be set up to access it. Then it will scan and populate the channels. ![]() The trick I was missing originally was that once it is started, and tvheadend discovers the presence of the HDHomeRun boxes to provide source material, it won’t user them until you create what tvheadend calls a “network” (configuration->dvb inputs->network), and then go back and assign the tv adapters (configuration->dvb inputs->tv adapters) to the network. There are websites with info about initial setup. ![]() Once you are in with the browser, one of the settings is access stuff. If authorization is requested and you don’t have it, start the process in the foreground with the -C option which will allow browser access from anywhere by anybody. The tvheadend directory has the configuration and “database” for tvheadend.Ĭonfiguration of tvheadend is done with a web browser, on localhost:9981 (or .y:9981). home/hts contains two directories, one for tvheadend, and the other for the program guide stuff (more about this later). It runs as its own user “hts” so there is a /home/hts. It runs as a daemon, started out of init.d. I installed the tvheadend piece on cinnamon (ubuntu). I only needed to install the tvheadend piece somewhere, and I put it on cinnamon where the large file media array is, so that PVR recorded material can be stored there too. ![]() Since the kodi I watch is on coriander (the mac mini), the pvr stuff is already installed with kodi. Kodi for mac and windows has the pvr bits included, but they have to be added in linux.After the apt install, add-ons->my add-ons->PVR clients, select TVHeadend HTSP Client and configure it, then Activate it. The “kodi-pvr” bits are kodi add-ons that have to be added to kodi (in linux only) in order to provide the api between kodi and the backend. Kodi-pvr-hts-dbg – debugging symbols for TVHeadEnd PVR for Kodi Kodi-pvr-tvheadend-hts – Kodi PVR Addon TvHeadend Hts – PVR API:1.9.2 Tvheadend-dbg – Debug symbols for Tvheadend The tvheadend software has to be installed. There are apparently different backends supporting different hardware, but one of the backends is called “tvheadend”, and it supports HDHomeRun, and is supported by Kodi. To use the built in features in Kodi for “live tv”, you have to have another piece of software, which Kodi calls the “backend”. However, this is just watching, and doesn’t enable the guide, PVR etc. They also provide a Kodi Add-on which allows watching the streamed material directly from there. They provide an app for windows/linux/mac which enables watching the tv stream directly, and changing channels. HDHomeRun provides a source of tv in htsp format.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |