Reply to thread

Message

<blockquote data-quote="erosco" data-source="post: 389568" data-attributes="member: 52829">Small update..I've built a patched TSREADER.ax that dumps the TS packet when an out of sequence occurs. I can confirm that this sequence error is not a LAN issue but is the way the packet is sent from the RTSP (Tv-Server) server..&nbsp; So it's not a LAN problem but equally may be just transmission errors over DVB-T.I am still sus (especially because the stuttering increases when EPG is on). I'll continue my tracing to see what I can find.CheerseroscoFurther update..After confirming today that this is not a network problem (correctly transmitted and received packets show missing TS records), I've continued me testing.A key point in my analysis is that after receiving a stutter in multiseat (using RTSP). If I hit the back button (to replay the last 30 seconds) the stutter doesn't happen again (in the same spot).This tells me that the live.ts.buffer file on the server has correctly captured an uncorrupted tv stream. The corruption is happening between the TV-Server reading the TS stream and pushing it out using the RTSP library.I am hoping the MP devs are following this post, as I'm now convinced this is a software bug in the TV-Server of LIVE555 library. I would appreciate any advice the TSWriter and RTSP devs could offer on where to go next. Ideally I'd like to add debug code that logs when stream TS sequence errors happen in TSWriter and matching code in the RTSP server code. Ideally matching lost packets should appear in the TSWriter Log, RTSP stream builder log, and TSReater log on the client. I strongly suspect this will show where TS records are being dropped in the server.Thankserosco</blockquote>

[QUOTE="erosco, post: 389568, member: 52829"] Small update.. I've built a patched TSREADER.ax that dumps the TS packet when an out of sequence occurs. I can confirm that this sequence error is not a LAN issue but is the way the packet is sent from the RTSP (Tv-Server) server.. So it's not a LAN problem but equally may be just transmission errors over DVB-T. I am still sus (especially because the stuttering increases when EPG is on). I'll continue my tracing to see what I can find. Cheers erosco Further update.. After confirming today that this is not a network problem (correctly transmitted and received packets show missing TS records), I've continued me testing. A key point in my analysis is that after receiving a stutter in multiseat (using RTSP). If I hit the back button (to replay the last 30 seconds) the stutter doesn't happen again (in the same spot). This tells me that the live.ts.buffer file on the server has correctly captured an uncorrupted tv stream. The corruption is happening between the TV-Server reading the TS stream and pushing it out using the RTSP library. I am hoping the MP devs are following this post, as I'm now convinced this is a software bug in the TV-Server of LIVE555 library. I would appreciate any advice the TSWriter and RTSP devs could offer on where to go next. Ideally I'd like to add debug code that logs when stream TS sequence errors happen in TSWriter and matching code in the RTSP server code. Ideally matching lost packets should appear in the TSWriter Log, RTSP stream builder log, and TSReater log on the client. I strongly suspect this will show where TS records are being dropped in the server. Thanks erosco [/QUOTE]

Verification