Reply to thread

Message

<blockquote data-quote="msj33" data-source="post: 876860" data-attributes="member: 16747">I found a bug in Tsreader when using Server/Client setup - A Bug that occurs with both Original and experimental Tsreader.&nbsp;Tsreader does in some cases not recover properly from a Continuity error - The Video playback keeps showing &quot;old&quot; frames.&nbsp;I will later link to 2 videos that show the issues. (Especially see the time counter on top of picture in video 1).Video 1: [media=youtube]9XlVU70RI9o[/media]Video 2: [media=youtube]SkvfX8uvCvI[/media]I can resolve the issue by doing a rewind and/or forward back to realtime playback. Also a stop/Start does recover the streaming. (video 2)&nbsp;I have this issue almost every day.&nbsp;In the attached logfiles, a freeze occured in playback at 22.04(Caused by either bad signal, wireless connection or cpu/disk usuage?)&nbsp;For the next 15 minutes the video playback kept being corrupted, untill I did a 15 sec. rewind.&nbsp;Can someone please have a look at this, and help confirm that this is actually a bug?&nbsp;Thanks in advanceMorten</blockquote>

[QUOTE="msj33, post: 876860, member: 16747"] I found a bug in Tsreader when using Server/Client setup - A Bug that occurs with both Original and experimental Tsreader. Tsreader does in some cases not recover properly from a Continuity error - The Video playback keeps showing "old" frames. I will later link to 2 videos that show the issues. (Especially see the time counter on top of picture in video 1). Video 1: [media=youtube]9XlVU70RI9o[/media] Video 2: [media=youtube]SkvfX8uvCvI[/media] I can resolve the issue by doing a rewind and/or forward back to realtime playback. Also a stop/Start does recover the streaming. (video 2) I have this issue almost every day. In the attached logfiles, a freeze occured in playback at 22.04(Caused by either bad signal, wireless connection or cpu/disk usuage?) For the next 15 minutes the video playback kept being corrupted, untill I did a 15 sec. rewind. Can someone please have a look at this, and help confirm that this is actually a bug? Thanks in advance Morten [/QUOTE]

Verification