Reply to thread

Message

<blockquote data-quote="Moorhuhn" data-source="post: 128207" data-attributes="member: 46448">Hi,as I can see in the sourcecode it was quite a lot of work to integrate the language-filter in the EPG-grabber. So I suppose there was a good reason to implement it. Iam just wondering what this reason was/is?Why not grab the EPG for the selected channels no matter what language? Just selecting all languages is, for some reasons, not a solution, because there are still some channels for which the EPG-grabber wont collect EPG-data although they have EPG-data.My second question is, if it would be a very bad idea to try and implement an alternate EPG-grabber-strategy:1. Tune the channel for which the EPG is needed.2. Wait for a configurable amount of time (e.g. 20sec) to collect the EPG-data.3. Continue with step 1 for every channel, for which EPG-data is to collect.Was there a special reason not to implement it this way? I suppose yes, but why?Bye,Moorhuhn</blockquote>

[QUOTE="Moorhuhn, post: 128207, member: 46448"] Hi, as I can see in the sourcecode it was quite a lot of work to integrate the language-filter in the EPG-grabber. So I suppose there was a good reason to implement it. Iam just wondering what this reason was/is? Why not grab the EPG for the selected channels no matter what language? Just selecting all languages is, for some reasons, not a solution, because there are still some channels for which the EPG-grabber wont collect EPG-data although they have EPG-data. My second question is, if it would be a very bad idea to try and implement an alternate EPG-grabber-strategy: 1. Tune the channel for which the EPG is needed. 2. Wait for a configurable amount of time (e.g. 20sec) to collect the EPG-data. 3. Continue with step 1 for every channel, for which EPG-data is to collect. Was there a special reason not to implement it this way? I suppose yes, but why? Bye, Moorhuhn [/QUOTE]

Verification