Reply to thread

Message

I can see why it stopped in the logs - in MediaPortal.log:

[CODE]
2012-02-17 20:54:28.532408 [Info.][MPMain(1)]: TSReaderPlayer: current pos:728,9113959 dur:4200,841
2012-02-17 20:54:40.614099 [Info.][MPMain(1)]: TSReaderPlayer : currentPos > duration
[/CODE]

The 'currentPos > duration' is the trigger for the MP TV player to stop playback because it thinks it's reached the end of the file, but only 12 seconds before it says that the playing position is only 728 secs into 4200 sec video....

There's not enough logging to show why it thinks 'currentPos > duration' - there's probably been a glitch in the position or duration data

Tony

<blockquote data-quote="Owlsroost" data-source="post: 844710" data-attributes="member: 83973">I can see why it stopped in the logs - in MediaPortal.log:&nbsp;[CODE]2012-02-17 20:54:28.532408 [Info.][MPMain(1)]: TSReaderPlayer: current pos:728,9113959 dur:4200,8412012-02-17 20:54:40.614099 [Info.][MPMain(1)]: TSReaderPlayer : currentPos &gt; duration[/CODE]&nbsp;The 'currentPos &gt; duration' is the trigger for the MP TV player to stop playback because it thinks it's reached the end of the file, but only 12 seconds before it says that the playing position is only 728 secs into 4200 sec video....&nbsp;There's not enough logging to show why it thinks 'currentPos &gt; duration' - there's probably been a glitch in the position or duration data <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite5" alt=":confused:" title="Confused&nbsp; &nbsp; :confused:" loading="lazy" data-shortname=":confused:" />&nbsp;Tony</blockquote>

[QUOTE="Owlsroost, post: 844710, member: 83973"] I can see why it stopped in the logs - in MediaPortal.log: [CODE] 2012-02-17 20:54:28.532408 [Info.][MPMain(1)]: TSReaderPlayer: current pos:728,9113959 dur:4200,841 2012-02-17 20:54:40.614099 [Info.][MPMain(1)]: TSReaderPlayer : currentPos > duration [/CODE] The 'currentPos > duration' is the trigger for the MP TV player to stop playback because it thinks it's reached the end of the file, but only 12 seconds before it says that the playing position is only 728 secs into 4200 sec video.... There's not enough logging to show [B][I] why[/I][/B] it thinks 'currentPos > duration' - there's probably been a glitch in the position or duration data :confused: Tony [/QUOTE]