redmed wrote: ↑Thu Apr 30, 2020 6:10 pm
It's been four days since I ran the garbage collection and the guide display is still fast! Thanks Gary!
Something I have noticed the last few months is that after a guide load i will do a "view scheduled" and see what the last day scheduled is. Then open the guide for the first time and the guide will not display the last day that shows with "view scheduled". It will be a day or two short. I will then close the guide and then open the guide for the second time then the guide will show the same last day that showed in "view schedule". There was a difference I've never seen before after this tuesday morning load. The "view scheduled" showed the schedule until 5\11 but the guide would only show up to 5\10 no matter how many times I open & closed the guide. This had me worried that the garbage collection did not go as smoothly as I had thought. But this morning after the thursday load the "view schedule" showed the schedule until 5\13. The first open of the guide only went to 5\12 but the second time I opened the guide it opened to 5\13 matching the schedule again. Does opening the guide trigger additional guide processing?
This is a bug with WMC that has always happened for me (even with Rovi/Microsoft data, and even before that when it used Gracenote). It is nothing new (at least for me).
When this happens, the guide just "stops" at a certain date/time and you can no longer scroll to the right. You will not see the "No data available" for the further out to the right timeslots that you would normally see. This is indicative of it just being a GUI/display problem, not a problem with the underlying data, which is still there, just not displayed by the GUI.
I've found two ways to "clear" the problem;
1) Run another guide update (with the old MS guide data it would return immediately since there would be no new data to download). I'm not sure if the same would happen if you did another EPG123 update, but I assume it would because, as you saw, it was fixed the next day you looked at it (most likely because of the second update). It is probably related to one of the two processes that are run after the update completes, and not the update itself.
2) Exit the WMC GUI and restart it.
Note that occasionally exiting WMC and restarting would not fix the problem, but I never had it not be fixed by starting a manual update of the guide data.
Now that we no longer use the built-in update mechanism (and instead use the external EPG123), I wonder if telling WMC to redownload the guide data would still work to fix this problem. If you try to update the guide using this old mechanism, it appears to do nothing, but it may still run the processes that tell it to update the guide "end" so that it scrolls further out to show the whole guide.