Hello,
Iam trying around with the various possibilities to get EPG-data into MP resp. TVServer3 in my case since a couple of weeks now. Unfortunately I was not able to find a solution, which works fine for my needs. I would not want to discuss the reasons for that here, as Iam afraid that this will lead into a neverending thread.
The question Iam interested in is:
Why is it not possible to collect complete and reliable EPG-data from the DVB-stream? Or is it possible and just not implemented yet?
As far as I know in europe, at least in germany, this data is available. Every DVB-receiver provides this functionality, so I suppose there must be a reason why it is not properly implemented in MP/TVServer3. I know that we have the epg-grabber, but this one works a little bit weird as it only "sometimes" collects the data for all of the configured channels. Additiionally the epg-grabber doesnt update epg-data that is already in the database and sometimes it creates special characters in the program description.
So is this just a matter of bugfixing or are there other reasons (technical reasons, ressource problems) why the integrated epg-grabber only works at about 80% of its possibilities?
Regards,
Moorhuhn
Iam trying around with the various possibilities to get EPG-data into MP resp. TVServer3 in my case since a couple of weeks now. Unfortunately I was not able to find a solution, which works fine for my needs. I would not want to discuss the reasons for that here, as Iam afraid that this will lead into a neverending thread.
The question Iam interested in is:
Why is it not possible to collect complete and reliable EPG-data from the DVB-stream? Or is it possible and just not implemented yet?
As far as I know in europe, at least in germany, this data is available. Every DVB-receiver provides this functionality, so I suppose there must be a reason why it is not properly implemented in MP/TVServer3. I know that we have the epg-grabber, but this one works a little bit weird as it only "sometimes" collects the data for all of the configured channels. Additiionally the epg-grabber doesnt update epg-data that is already in the database and sometimes it creates special characters in the program description.
So is this just a matter of bugfixing or are there other reasons (technical reasons, ressource problems) why the integrated epg-grabber only works at about 80% of its possibilities?
Regards,
Moorhuhn