Hello,
I was wondering if it is possible (or will probably be in the future) to have the EPGCache "caching" some kind of delay. From my older STB I am used to go back in "history" for a while (12-24 hours) to see what has been on TV during the last hours to catch up with what I might have missed.
As I'm using a CT9100 with latest OpenPLi, I asked for this feature at CT-Support forums and was told by "Coolman", that it is a behavoir which most likley needs to be taken care of on side of the enigma2 code. Coolman is only using the data that is provided be enigma2 to show EPG information inside his "Cool Guides".
Another question is how a can tell for how long the EPG data (from SAT, i only use Astra 19.2E) will reach into the future. Is this something that can be configured or does it only depend on the service(s) (provider/program/transponder) I use?
Thanks for your help/answers in advance!
Best regards
daPain
Two questions about EPGCache
Started by PainHealer, 27 Nov 2011 23:27
2 replies to this topic
Re: Two questions about EPGCache #2
Posted 28 November 2011 - 08:19
Letting the EPG have "historic" data is not a problem in code - just a few lines - but I suspect it will lead to weird failures and odd behaviour, as most components - especially plugins - just assume that the EPG data starts somewhere around "now". There's also the matter of RAM usage, some people have EPG data for hundreds of channels and will experience problems if the EPG data isn't deleted soon enough.
The EPG's range into the future is mostly determined by the provider. There is a line of code that throws away all EPG data more than four weeks in future, so that's the current maximum. I don't know what the rationale behind that is, probably it's considered untrustworthy or so, but changing that value is rather simple if the need ever arises.
The EPG's range into the future is mostly determined by the provider. There is a line of code that throws away all EPG data more than four weeks in future, so that's the current maximum. I don't know what the rationale behind that is, probably it's considered untrustworthy or so, but changing that value is rather simple if the need ever arises.
Real musicians never die - they just decompose
Re: Two questions about EPGCache #3
Posted 28 November 2011 - 08:56
Good Morning MiLo,
thanks for your reply! If having a history is not an "option", one should probably leave it as it is. It would have been fine if this could be configured. I also totally understand, that there are setups with multiple thousands of channels/providers and that memory should be considered. For the part of the plugins it would be better that the certain developer "knows" what he is doing. They should not rely on something "fuzzy" like "hope the data is correct and up to date"...;-) Sure, if a plugin can not tell how old the "oldest" data really is, how should it know how to display it.
For the "future data" I was wondering why I only have around five days (or even less) epg data, but I guess this really depends on the provider/channel? How can I determine for how long a certain channel provides epg data?
Regards
PainHealer
thanks for your reply! If having a history is not an "option", one should probably leave it as it is. It would have been fine if this could be configured. I also totally understand, that there are setups with multiple thousands of channels/providers and that memory should be considered. For the part of the plugins it would be better that the certain developer "knows" what he is doing. They should not rely on something "fuzzy" like "hope the data is correct and up to date"...;-) Sure, if a plugin can not tell how old the "oldest" data really is, how should it know how to display it.
For the "future data" I was wondering why I only have around five days (or even less) epg data, but I guess this really depends on the provider/channel? How can I determine for how long a certain channel provides epg data?
Regards
PainHealer
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users