> > what about your VDR system ? Have you the same errors ? > > Well, my P4 2.8 GHz HT system is not powerful enough to play this > stream in real time. yes, I have the same CPU CPU: Intel(R) Pentium(R) 4 CPU 3.00GHz (Family: 15, Model: 3, Stepping: 4) >Hence, I regularly see VDR issue CLEARs > after which such messages are normal. sorry, what do you mean "VDR issue CLEARs" ? > > btw , I have uploaded one sample from AstraHD with the size 10 MB > > > > Astra.pes > > http://www.zshare.net/download/1179707004348a83/ > > > > you can try it > > As written above, I had to slow down replaying: > > xine -S slow2 astra.pes#demux:mpeg_pes > > This only gives me messages for two B pictures, i. e. you're cut > VDR recording shows a picture structure like that: > > IBBP.... > > In MPEG2, one (VDR) would have set the broken link flag for such > a group of pictures as the B pictures cannot be decoded without a > reference picture from the previous GOP. > > But H.264 doesn't have a broken link flag, so that's why FFmpeg > gives messages like the following: > > [h264 @ 0xac236490]B picture before any references, skipping > [h264 @ 0xac236490]decode_slice_header error > [h264 @ 0xac236490]B picture before any references, skipping > [h264 @ 0xac236490]decode_slice_header error so, could you give some resume about this errors ? is it ffmpeg/provider/vdr/driver problem ? or no any problem ? Igor _______________________________________________ vdr mailing list vdr@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
