Reply to thread

Message

<blockquote data-quote="davidf" data-source="post: 649521" data-attributes="member: 19484">Can I raise a tiny bug too.&nbsp; Your log file date format is different from the rest of Mediaportal, your logs have date in the format DD-MM-YYYY HH:MM: SS:FFF mediaportal uses YYYY-MM-DD HH:MM: SS:FFFFFF, also your logfile has empty lines in it which is different to mediaportal too.&nbsp; I've knocked up something to combine multiple logfiles to get a single timeline and your logfile didn't parse first time (Really I just like consistency <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />).The dropping mostly happens when the bias is set to 1.040956 (the detected framerate is 50, but had been incorrectly 47.952 when the bias was selected and it also detected 59.94 at one point).&nbsp; It then trys at a framerate of50 with a bias of 1 and playback with audo is correct within 0.5 seconds.</blockquote>

[QUOTE="davidf, post: 649521, member: 19484"] Can I raise a tiny bug too. Your log file date format is different from the rest of Mediaportal, your logs have date in the format DD-MM-YYYY HH:MM: SS:FFF mediaportal uses YYYY-MM-DD HH:MM: SS:FFFFFF, also your logfile has empty lines in it which is different to mediaportal too. I've knocked up something to combine multiple logfiles to get a single timeline and your logfile didn't parse first time (Really I just like consistency :-)). The dropping mostly happens when the bias is set to 1.040956 (the detected framerate is 50, but had been incorrectly 47.952 when the bias was selected and it also detected 59.94 at one point). It then trys at a framerate of50 with a bias of 1 and playback with audo is correct within 0.5 seconds. [/QUOTE]

Verification