Reply to thread

Message

<blockquote data-quote="spar1grep" data-source="post: 692267" data-attributes="member: 68691">Hi mm1352000No problems about the logs I do undestand how important generating a decent test is and reducing the possibility of mis-diagnosis because of noise. Yes I was running the MP client in window mode as normally I run it full screen but in order to capture the log files at the moment the TV server froze I reconfigured it to run in a window.&nbsp; In relation to the Main:OnResizeEnd could that event be generated by the MP Client window loosing focus and then me clicking on the windowed MP Client titlebar and moving the window as I had about five different windows open on the desktop and had to keep jumping between them to copy the files etc.&nbsp; You are right about your TS buffer reference I was referring to the timeshifting file when using the term transport stream.As you are pretty certain that something it telling MP to stop the stream and there is a difference time period before the LiveTV freezes dependant on the codec being used (the time period remains pretty consistent if I repeat the tests using the same codec over and over) to read the timeshifitng file, does the decoder codec make a difference to the amount of time that can be fitted inside say for example a 1GB timeshift buffer file or does the amount of time that fits into the timeshifiting file always remain constant?&nbsp; My thinking is that maybe when the next .TS file is supposed to be created and the MP Client is supposed to goto to the next .TS file in the sequence as configured in the TV Server timshifting section that something goes wrong at that point?&nbsp; I did read up on the Wiki article about the transport stream buffer but I could not figure out if the decoder used has a impact on it?Regards.Gary</blockquote>

[QUOTE="spar1grep, post: 692267, member: 68691"] Hi mm1352000 No problems about the logs I do undestand how important generating a decent test is and reducing the possibility of mis-diagnosis because of noise. Yes I was running the MP client in window mode as normally I run it full screen but in order to capture the log files at the moment the TV server froze I reconfigured it to run in a window. In relation to the Main:OnResizeEnd could that event be generated by the MP Client window loosing focus and then me clicking on the windowed MP Client titlebar and moving the window as I had about five different windows open on the desktop and had to keep jumping between them to copy the files etc. You are right about your TS buffer reference I was referring to the timeshifting file when using the term transport stream. As you are pretty certain that something it telling MP to stop the stream and there is a difference time period before the LiveTV freezes dependant on the codec being used (the time period remains pretty consistent if I repeat the tests using the same codec over and over) to read the timeshifitng file, does the decoder codec make a difference to the amount of time that can be fitted inside say for example a 1GB timeshift buffer file or does the amount of time that fits into the timeshifiting file always remain constant? My thinking is that maybe when the next .TS file is supposed to be created and the MP Client is supposed to goto to the next .TS file in the sequence as configured in the TV Server timshifting section that something goes wrong at that point? I did read up on the Wiki article about the transport stream buffer but I could not figure out if the decoder used has a impact on it? Regards. Gary [/QUOTE]

Verification