<div dir="ltr">HI,<br><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Aug 15, 2013 at 5:22 AM, watch_the_rain <span dir="ltr"><<a href="mailto:watch_the_rain@163.com" target="_blank">watch_the_rain@163.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="line-height:1.7;font-size:14px;font-family:arial">Today I found that the the progam did not find the event schedule information in the EIT table when I decode a new TS stream, but It works well with the old stream. (The verison of the library I used was v 0.1.6.)<br>
Then I tryed with the latest version(v1.1.0), the result iwas a little better,14 events in the event schedule table were found.<br>The debug error infromation was printf like this: <br> TS discontinuity (received 6, expected 5) for PID 18<br>
TS discontinuity (received 0, expected 15) for PID 18<br> TS discontinuity (received 0, expected 15) for PID 18<br> ............<br>So I printed the continuity counter number in the ts paket I before pushed to the EIT decoder,It showed text below (just a small fraction):<br>
continuity_counter:0<br> continuity_counter:1<br> continuity_counter:2<br> continuity_counter:4<br> libdvbpsi error (PSI decoder): TS discontinuity (received 4, expected 3) for PID 18<br> continuity_counter:5<br>
libdvbpsi debug (EIT decoder): Table version 11, i_table_id 80, i_extension 1, section 0 up to 248, current 1<br> continuity_counter:6<br> continuity_counter:9<br> libdvbpsi error (PSI decoder): TS discontinuity (received 9, expected 7) for PID 18<br>
continuity_counter:11<br> libdvbpsi error (PSI decoder): TS discontinuity (received 11, expected 10) for PID 18<br> continuity_counter:12<br> libdvbpsi debug (EIT decoder): Table version 11, i_table_id 80, i_extension 3, section 8 up to 248, current 1<br>
continuity_counter:13<br> continuity_counter:14<br> continuity_counter:0<br> libdvbpsi error (PSI decoder): TS discontinuity (received 0, expected 15) for PID 18<br> .........<br>A “continuity_counter: xx” means pushing a packet to EIT decoder once. There were an average of one error message every 6 packets. The packets missed were lost in the transport.<br>
Is the <span><a>high</a> <a>frequency of </a></span>discontinuity that made the decoder failed? And I think that the packet loss is too hight in the ts transport, but the <span>superior don't think so. </span>What do you think?<br>
I'm sorry my English was not good, there must be some error in the email.<br>Please help me, thanks very much!<br><br></div></blockquote><div><br>In the example log above you lost 5 packets out of 15, which is one third !!!</div>
<div><br>You have massive loss of packets and thus you miss information form the EIT tables.<br><br>First fix the reason for the packet loss, then test the EIT again.<br> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div style="line-height:1.7;font-size:14px;font-family:arial"><br></div><br><br><br>_______________________________________________<br>
libdvbpsi-devel mailing list<br>
<a href="mailto:libdvbpsi-devel@videolan.org">libdvbpsi-devel@videolan.org</a><br>
<a href="https://mailman.videolan.org/listinfo/libdvbpsi-devel" target="_blank">https://mailman.videolan.org/listinfo/libdvbpsi-devel</a><br>
<br></blockquote></div><br></div><div class="gmail_extra">Kind regards,<br><br></div><div class="gmail_extra">Jean-Paul Saman<br></div></div></div>