yamcenutzer wrote:From what I have read until now, epg updates are only pulled by WMC clients upon start, and then every x hours.
The EPG information is processed by the dvblink/tvsource server which updates every 12 hours. Connect clients get their configuration from this server. I would guess that when a client machine wakes and the dvblink client service starts, it connects to the server and refreshes as required. Similarly if the server sleeps, the dvblink server service startup processes handle overdue EPG processing. The only thing you cannot do is 'push' EPG data file to a sleeping device, it has to be a pull....
I too have a number of guesses, but I would appreciate a confirmation of some kind.
Simple scenario: local TVSource wmc client doing scheduled recordings for a weekly series on a eit-based EPG( only the next 2-3 days available).
. the schedules of client and Server are not synchronized per se
. the server does its 12 hourly update of epg (i hope, it wakes the machine from sleep to do so)
. having done it's update, will server also update the local client?
. machine sleeps again (I hope)
. machine wakes up at another time for recording --> will it now grab latest epg?
. if not, how will it update its recording schedule for the next week?
If, like you suggested, the client also pulls epg after resume, and not only after restart, then the problem would be solved. That is yet to be confirmed (only read about 'restart', not resume)
Also, if the client could do oportunistic scans, the problem would also be solved. That of course requires inband EIT data, which is being suppressed, or some other GDDS Update event.
If the client is a remote client, then we have additional complexity added, which I would discuss in a different thread, once the basics are clarified.