Great.Thanks! That seems to have (maybe) done the trick. I've only watched a 42min show thus far but it didn't randomly stop, so I have a good feeling about this.
Also out of interest I changed my TV client config to point at 127.0.0.1 (although in the log it still shows my actual machine IP) but whilst there appear to be TV service heart beat problem I have never one had TV playback fail, I guess because it is actually playing recording from a local file and I don't watch much live TV (am I right to assume that a network loss would only affect live stream, not recorded on the local machine?, or does the TV CLient network stream recorded programs from the TV Service on the local machine as well? in which case any idea why this would not drop out?
Also out of interest I changed my TV client config to point at 127.0.0.1 (although in the log it still shows my actual machine IP) but whilst there appear to be TV service heart beat problem I have never one had TV playback fail, I guess because it is actually playing recording from a local file and I don't watch much live TV (am I right to assume that a network loss would only affect live stream, not recorded on the local machine?, or does the TV CLient network stream recorded programs from the TV Service on the local machine as well? in which case any idea why this would not drop out?
If TV server and client are on the same PC, and the hostname is the local PC (or 127.0.0.1 - 'localhost'), then MP assumes it's a single-seat system and plays the timeshift and recording files directly, but it always uses the network for control/status communications between client, server and database (so you always need a working 'network' system, even if there is no external connection to it - Windows handles this situation automatically).