Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 1043672" data-attributes="member: 82144">What exactly do you mean by &quot;public&quot;, and have you tried disabling it completely?Also, what about the IPv6 question?I realise that. Obviously I can't be there to see what you're actually seeing, but just because I can't see your screen doesn't mean that the log entries aren't accurate.From the log quote in my last post we can see the first line in the log file which should be written almost immediately after you activate the MP shortcut.We can also see the point in time where you asked MP to close.There is no ambiguity about either of those times.The time difference is approximately 35 seconds. If you're saying it took 60 seconds to load MP on that occasion, not even counting the time between when MP finished loaded and when you closed it down again... something is off. Either your estimate is wildly wrong or a lot of time is spent before the first log entry is written. In the first case, you can ensure your estimate is not wrong by using a stopwatch every time; in the second case, to me that would indicate an OS/system problem.Does that make sense?Yes, it means the client tried to ask the server whether any tuners were recording, and the request failed. Failures of that kind usually happen because the connection between the client and server dropped out. Again I'd like to point out that in my opinion the log entry is not directly relevant to the delay. I'm ignoring it.Coming back to some comments you made previously...These two statements seem to contradict eachother. Can you please elaborate?</blockquote>

[QUOTE="mm1352000, post: 1043672, member: 82144"] What exactly do you mean by "public", and have you tried disabling it completely? Also, what about the IPv6 question? I realise that. Obviously I can't be there to see what you're actually seeing, but just because I can't see your screen doesn't mean that the log entries aren't accurate. From the log quote in my last post we can see the first line in the log file which should be written almost immediately after you activate the MP shortcut. We can also see the point in time where you asked MP to close. There is no ambiguity about either of those times. The time difference is approximately 35 seconds. If you're saying it took 60 seconds to load MP on that occasion, not even counting the time between when MP finished loaded and when you closed it down again... something is off. Either your estimate is wildly wrong or a lot of time is spent before the first log entry is written. In the first case, you can ensure your estimate is not wrong by using a stopwatch every time; in the second case, to me that would indicate an OS/system problem. Does that make sense? Yes, it means the client tried to ask the server whether any tuners were recording, and the request failed. Failures of that kind usually happen because the connection between the client and server dropped out. Again I'd like to point out that in my opinion the log entry is not directly relevant to the delay. I'm ignoring it. Coming back to some comments you made previously... These two statements seem to contradict eachother. Can you please elaborate? [/QUOTE]

Verification