The backend is a MediaPortal 2 Server running on Windows 10.Īll working clients are also running on Windows 10, using Kodi 16.1 (and the matching Mediaportal PVR client 1.13.6). I searched via google and on this forum for a solution, but I couldn't find any useful info.

With a LibreELEC Kodi client, running on a Raspberry Pi, but unfortunately I can't get the client running,Įven if I have quite some experience with Kodi and MediaPortal in general already. 'sub-optimal'.I have planned to substitue one of my Windows-based Kodi MediaPortal PVR clients, mainly used for 'Live TV', In short: to me it looks like your grabber configuration is. Their data can come from grabbing for the selected TV channels. Therefore according to the above strategy: normally you should disable the radio 'store data only for selected channels' option and deselect all radio channels. It can acquire the EPG data for TV channels when grabbing for a radio channel, and vice versa.

and as mentioned above: don't forget about the radio EPG grabber section! The grabber has to update both TV and radio channels. and if you tick too many, guide data for some channels may never be updated (the grabber starts over from scratch every 240 minutes, as configured). The more channels that you tick, the longer it may be before guide data is populated/updated. Normally you should only tick one channel per provider, or at most, one channel per transponder/transmitter/frequency/mux.Īccording to your configuration (default), the idle grabber must grab for up to 10 minutes for each ticked channel. Select as few channels as possible (both TV and radio).Disable the 'store data only for selected channels' option s (both TV and radio).

Disable the 'grab EPG only for channels on the same transponder' option.The best strategy for the DVB EPG grabber is to: Is there a reason you've ticked/enabled 'store data only for selected channels'? Click to expand.Hmmm, that doesn't look so good.

Mediaportal 2 epg not working