Reply to thread

Message: <blockquote data-quote="CyberSimian" data-source="post: 1105862" data-attributes="member: 141969">This is an interesting observation, and perhaps will lead to the eventual diagnosis of the problem.My HTPC has a reasonably-powerful CPU (Intel Q6600) and loads of tuners (8), so when I configured EPG-grabbing in "TV Server Config", I enabled almost everything:(1) It grabs when the tuners are idle.(2) It grabs when recording/timeshifting.(3) It fills in EPG holes.(4) It updates existing EPG entries.(5) It does CRC checks. But I left the EPG refresh timeout at 240 minutes, and have not programmed the HTPC to wake up in the middle of the night to grab the EPG.  Consequently, when I switch it on in the morning to check repeating recordings and schedule one-off recordings for that day, it is overdue for an EPG grab, and so starts grabbing the EPG immediately after wake from hibernation.So this morning I checked to see if the EPG had any scheduled recordings that were not highlighted.  I first checked immediately after starting MP after wake, but I did not find any missing highlights.  However, I checked again a few minutes later, and this time I did find some missing highlights.  Now I am running MP 1.9.0 pre, and this seems to have the log modes already set to DEBUG, so I had a look at the TV Server log:(1) System woke from hibernation at 09:09:39.(2) System started EPG grabbing at 09:09:45.(3) EPG had a missing highlight for the programme "Call the Council" on "BBC One HD" when I checked at 09:23 (I took a screen shot, but that does not tell us anything, so I have not included it).(4) System finished EPG grabbing at 09:26:41.I searched the TV Server log from the start of EPG grabbing for ERROR or WARN entries, but did not find any.  I have included the logs, but I don't know whether they will be of any use (unfortunately I had not started MP from the Watchdog, so MP is using the "aMPed" skin).  Nevertheless, the point of me writing this post is to suggest that perhaps we have now identified the circumstances in which this error occurs, and hence be able to reproduce this error on demand when an MP developer has time to investigate it.Finally, is there a workaround that avoids this problem?  It occurs to me that one could change the EPG refresh time from 240 minutes to 1440 minutes (i.e. 24 hours).  If one could then contrive to get TV Server to perform an EPG grab at (say) 03:00:00, it would continue to grab the EPG at that time on following days, and not when the user was using the HTPC.However, increasing the EPG refresh time also has its disadvantages.  I have been using MP as my DVR for just two months, and yet in that time there have been three occurrences (that I know about!!!) when programmes that I have scheduled to record have had last minute EPG changes that altered their start times and/or their end times.  I mostly use option 8 for recording ("weekly on this channel"), so changes in start/end times are automatically picked up provided that the EPG is updated.  If the EPG were updated only once every 24 hours, these last minute EPG changes would not be detected, and TV Server would record the programmes at the old (i.e. wrong) times.  These are only the occurrences I know about; there must be many more such changes for programmes that I don't record.  So increasing the EPG refresh time to 24 hours is not really a solution (at least, not in the UK).-- from CyberSimian in the UK</blockquote>

Verification