Project

General

Profile

Bug #3310

EPG Grabber Channels Default Behavior

Added by Martin Walter almost 9 years ago. Updated almost 9 years ago.

Status:
Invalid
Priority:
Normal
Assignee:
Category:
EPG
Target version:
-
Start date:
2015-11-17
Due date:
% Done:

0%

Estimated time:
Found in version:
4.1.988
Affected Versions:

Description

Not sure whether this is because I updated by about 700 commits or whether this happens with fresh installs as well, but here the issue:

I mapped all channels on initial install and deactivated all of those I don't use, i.e. most of them. I use OTA grabbers only: EIT, UK Freeview and UK Freesat.

1) Configuration -> Channel / EPG -> Channels:
All channels are set to "Automatically map EPG source" enabled, also for those channels that I had activated.

2) Configuration -> Channel / EPG -> EPG Grabber Channels
All XMLTV modules are activated, again also for those channels I have deactivated.

Would it make sense to only automatically map those EPG sources by default for which the channel is actually enabled (javier segura) so that only those XMLTV modules are activated by default that are actually used (@2)?

History

#1

Updated by Jaroslav Kysela almost 9 years ago

I think that you mix things together - it seems that the new mapping table (EPG channel mapping) uncovered things you don't know. The basic XMLTV import behaviour was not changed.

The user is responsible to enable XMLTV sources (modules). If you enable them, they're ALWAYS processed (XML is parsed). The channels from 'EPG channel mapping' come from the XMLTV (as you enabled these sources) - so you see all EPG channels which you can map. But the EPG events are not completely parsed / stored when the TVH channel is not enabled.
And yes - it's better to remove the channels from XMLTV if they're not used to save a little CPU time.

#2

Updated by Martin Walter almost 9 years ago

Yes, I keep uncovering things I didn't know about way more often than I'd like to... :-)

Thanks for clarifying! I understand now. Is there some way to see in the EPG Grabber Channels tab, which sources (modules) are associated with enabled channels, then? Apparently the parser "knows" about the connection. I'm thinking of some column, which I could sort by or some filter I could use to avoid manual identification. I have two satellite positions with 558 XMLTV sources...

#3

Updated by Jaroslav Kysela almost 9 years ago

You should see 'Module' and 'Path' columns. Both of them identifies the XMLTV sources (internal XMLTV import). If you use socket interface (external XMLTV import) - you're bad, because this source cannot be identified - the utilities sends XML to a socket without the TVH knowledge of the source.

#4

Updated by Martin Walter almost 9 years ago

Hmh, module is "XMLTV" and path points at "[...]/epggrab/xmltv.sock" for all 558 entries. The ID refers to various microsoft.com sites. Must be internal XMLTV imports from OTA grabbers (EIT and UK Freeview/sat) though, as I'm not using external imports, but no way to distinguish enabled from disabled channels there.

Don't worry. I will wait for 4.2. and do a clean install. Wanted to try the bouquet feature for quite some time now. Will take care of the XLMTV sources then. Please feel free to close this ticket and thanks for your tremendous efforts in further improving and developing this software!

#5

Updated by Jaroslav Kysela almost 9 years ago

Martin Walter wrote:

Hmh, module is "XMLTV" and path points at "[...]/epggrab/xmltv.sock" for all 558 entries. The ID refers to various microsoft.com sites.ere.

You're using external XMLTV imports through socket. TVH does not know which task pushed data to this socket. If you are sure that no XMLTV "pusher" is running, you may remove all these lines in the EPG Channel Mapping grid. The OTA grabbers are not listed in this grid.

#6

Updated by Martin Walter almost 9 years ago

Gee, I must have carried those entries for months and months. I experimented with XMLTV pushers once, but found they woudn't add much value over the OTA grabbers. I have deleted all the orphan entries now and everything is fine.

Thanks again!

#7

Updated by Jaroslav Kysela almost 9 years ago

  • Status changed from New to Invalid

Ok, marking as invalid.

Also available in: Atom PDF