Re: [vdr] Possibly corrupt stream for VDR frontends in 1.7.4?

2009-04-16 Thread Artem Makhutov
Hi, On Tue, Apr 14, 2009 at 11:31:07AM +0200, alexw wrote: > Hi, > > In your capture file, I can see the PAT insertion have a bad TS > continuity counter. But his should not prevent from getting the PMT and > decoding the stream. > > PID: 0118x continuity errors (PAT) > PID: 97 OK

Re: [vdr] Possibly corrupt stream for VDR frontends in 1.7.4?

2009-04-14 Thread alexw
Hi, In your capture file, I can see the PAT insertion have a bad TS continuity counter. But his should not prevent from getting the PMT and decoding the stream. PID: 0118x continuity errors (PAT) PID: 97 OK (PMT) PID: 51111x continuity errors (VIDEO) PID: 5158x continuity er

Re: [vdr] Possibly corrupt stream for VDR frontends in 1.7.4?

2009-04-10 Thread Artem Makhutov
Hello, alexw schrieb: > Hi, > > Could you please check the TS continuity with dvbsnoop when using > streamdev or xineliboutput over the network? If not please make a > network recording (~ 5 minutes) for both case. > > 1) Streamdev > wget -q -O - http://:3000/TS/ > streamdev.ts > > 2) Xinelib

Re: [vdr] Possibly corrupt stream for VDR frontends in 1.7.4?

2009-04-06 Thread alexw
Artem Makhutov wrote: > Hello, > > currently watching HDTV channels using a VDR frontend (streamdev and > xineliboutput - current CVS builds) is impossible for me. > > Watching the recordings (1.ts) using xine (with VDPAU) works like a charm. > > I am wondering if there could be a bug in how VD