Reply to thread

Message: <blockquote data-quote="CyberSimian" data-source="post: 1284327" data-attributes="member: 141969">Thank you for adding the extra debug logging. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite24" alt="(y)" title="Thumbs Up    (y)" loading="lazy" data-shortname="(y)" /> <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile    :)" loading="lazy" data-shortname=":)" />I have installed the modified files and have been watching some live TV and recorded TV.One quirk that I noticed is with regard to the quantity of logging. I watched a 30-minute recording, and then exited MP to examine the log file. I found the "playback stopping" lines in "MediaPortal.log", but I could not find the "playback starting" lines. I then looked at the "MediaPortal.n.log" files (n=1 to 5), but the "playback starting" lines were nowhere to be found <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite12" alt="o_O" title="Er... what?    o_O" loading="lazy" data-shortname="o_O" />. All of the previous log files are filled with the new debug logging. It seems that MP starts a new log file when the log reaches about 5 MByte in size (around 60K lines), and keeps only the previous five logs (TV Server keeps the previous ten logs).I don't think that filling the log files matters greatly, as when the "no video" error occurs, I will stop playback immediately, so the important "playback starting" lines will be in the current log file.From looking at the log file, I notice that when a recording was being played, the log file has two lines that repeat every 20 msec, namely "In screensaver" and "Not blank". So I suppose that the screen saver code is executed every 20 msec to check whether it should do anything. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite12" alt="o_O" title="Er... what?    o_O" loading="lazy" data-shortname="o_O" />There is one unrelated (I think) quirk that looks like it might be an error. So far I have always assumed that the error log files contained the errors from the corresponding full log files. So "MediaPortal-Error.1.log" contains the error lines from "MediaPortal.1.log". With the extra debug logging, that is no longer true. For example, "MediaPortal.5.log" is a log from today, but "MediaPortal-Error.5.log" shows the error lines from yesterday. So for some reason the error log files and the full log files are no longer being kept in step. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite3" alt=":(" title="Frown    :(" loading="lazy" data-shortname=":(" />I will continue using the debug versions and see if I can provoke the error, but so far I have not noticed a correlation with any particular sequence of actions (other than the MP and/or the Windows screen savers operating when on a MP panel, but that is not enough to guarantee that the error will occur -- it seems as though there is some other factor involved).Thank you for the work that you have done so far! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile    :)" loading="lazy" data-shortname=":)" />-- from CyberSimian in the UK</blockquote>

Verification