Reply to thread

Message

<blockquote data-quote="glenn 1990" data-source="post: 825414" data-attributes="member: 105566">RTSP looping problem seems solved <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />I often see the previous channel for a few seconds after zapping, this increases the tuning time (too)much.(channel1 --&gt; zap --&gt; black screen --&gt; freezed image channel1 for some seconds --&gt; channel2)I guess that it has the same root cause as the looping problem ( seeking inaccuracy).What if adding an offset&nbsp; to the seeking time, I guess the server will correct it if this is over the live point.I found some disabled code in tsreader about this.[CODE]//&nbsp; if (diff &lt;20 &amp;&amp; m_fStart&gt;1 )//&nbsp; {//&nbsp; &nbsp; m_fStart=dur+5;//&nbsp; }[/CODE]</blockquote>

[QUOTE="glenn 1990, post: 825414, member: 105566"] RTSP looping problem seems solved :) I often see the previous channel for a few seconds after zapping, this increases the tuning time (too)much. (channel1 --> zap --> black screen --> freezed image channel1 for some seconds --> channel2) I guess that it has the same root cause as the looping problem ( seeking inaccuracy). What if adding an offset to the seeking time, I guess the server will correct it if this is over the live point. I found some disabled code in tsreader about this. [CODE] // if (diff <20 && m_fStart>1 ) // { // m_fStart=dur+5; // }[/CODE] [/QUOTE]

Verification