Reply to thread

Message

<blockquote data-quote="Imokles" data-source="post: 484264" data-attributes="member: 91173">Yesterday, I moved my TV Server from an Analog/DVB-C combination to DVB-S. Since then, I also have PMT timeout problems.I spent the better part of yesterday trying to investigate. I already increased the time from 10s to 15s and completely disabled EPG grabbing. It seems that TV will only work one time after TV server startup (and I mean boot, not TV service start). Once I close the MP client, reopen it and try to access it for the 2nd time, the error occurs. So maybe the problem lies with the actions during shutdown of the TV client?I am running MP1.0.2. TV server runs on Windows Home Server (yes, I know, not supported, but the Analog/DVB-C combo ran fine) and two clients running Vista Home Premium. Therefore, I can't just try to upgrade to MP 1.1.0 alpha without investing lots of time.TV log (cut to the relevant section) attached.Can somebody help me or at least confirm I have the same problem as everybody else here (which would mean a fix is in the works)?</blockquote>

[QUOTE="Imokles, post: 484264, member: 91173"] Yesterday, I moved my TV Server from an Analog/DVB-C combination to DVB-S. Since then, I also have PMT timeout problems. I spent the better part of yesterday trying to investigate. I already increased the time from 10s to 15s and completely disabled EPG grabbing. It seems that TV will only work one time after TV server startup (and I mean boot, not TV service start). Once I close the MP client, reopen it and try to access it for the 2nd time, the error occurs. So maybe the problem lies with the actions during shutdown of the TV client? I am running MP1.0.2. TV server runs on Windows Home Server (yes, I know, not supported, but the Analog/DVB-C combo ran fine) and two clients running Vista Home Premium. Therefore, I can't just try to upgrade to MP 1.1.0 alpha without investing lots of time. TV log (cut to the relevant section) attached. Can somebody help me or at least confirm I have the same problem as everybody else here (which would mean a fix is in the works)? [/QUOTE]

Verification