From: Rett W. <re...@rt...> - 2003-06-26 15:12:02
|
James Courtier-Dutton (Ja...@su...) wrote: > >Correction to my last email. >The example stream "test_ts.mpg" has wrongly defined PAT tables, so xine >ignores the PAT tables as it is told to by the "current_next_indicator" >This stream has them set to 0, so we should ignore them. >If they are set to 1, xine will act on them. >Summary: - >The device creating these streams has a bug! > >Cheers >James > > James: I have posted a different stream created from an upgraded version of the VideoLAN client that created the last stream I posted about. Xine acts differently with this file, posting several "PES errors" to the console during playback. Sample: demux_ts: PID 68: corrupted pes encountered demux_ts: PID 68: corrupted pes encountered demux_ts: PID 68: corrupted pes encountered demux_ts: PID 68: corrupted pes encountered demux_ts: PID 68: corrupted pes encountered I am putting the file out there now, its name is test4.ts available via anonymous FTP at ftp.rtwnetwork.com. Can you look at that one and see if it still looks like its videolan's fault? Thanks, Rett PS - Also, you may want to look at a later message of mine about xine having issues playing a PS (rather than TS) file created with the same tool that xine can't play, but mplayer can. Rett |