Hi
during watching of Astra HD+ from Astra 19,2E I always have this errors
[h264 @ 0xabfba3d0]B picture before any references, skipping [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]B picture before any references, skipping [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]B picture before any references, skipping [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]B picture before any references, skipping [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]B picture before any references, skipping [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]B picture before any references, skipping [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]no frame! ffmpeg_video_dec: error decompressing frame [h264 @ 0xabfba3d0]non existing PPS referenced [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]non existing PPS referenced [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]non existing PPS referenced [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]non existing PPS referenced [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]non existing PPS referenced [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]non existing PPS referenced [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]no frame! ffmpeg_video_dec: error decompressing frame
200 frames delivered, 31 frames skipped, 52 frames discarded video_out: throwing away image with pts 120676128 because it's too old (diff : 25806). video_out: throwing away image with pts 120690172 because it's too old (diff : 43300). video_out: throwing away image with pts 120711478 because it's too old (diff : 73586). vdr: osdflush: n: 4, 76.7, timeout: 0, result: 0 video_out: throwing away image with pts 120732839 because it's too old (diff : 104127).
I think it's ffmpeg's problem, but I don't know how can I solve it. It seems to me, nobody from ffmpeg-devel list doesn't want to fix it. Has somebody experience with this problem ?
Igor
On Sun, May 04, 2008 at 11:13:37PM +0400, Igor wrote:
I think it's ffmpeg's problem, but I don't know how can I solve it. It seems to me, nobody from ffmpeg-devel list doesn't want to fix it. Has somebody experience with this problem ?
The Astra HD stream has errors always on the same positions in the loop. They show up also with the Reel HDE and the Humax HD1000.
When they were simulcasting AstraHD on the Pro7HD and PremiereHD-transponder, only the stream on the PremiereHD-transponder was OK. Now they apparently have moved the faulty stream also to PremiereHD...
I think it's ffmpeg's problem, but I don't know how can I solve it. It seems to me, nobody from ffmpeg-devel list doesn't want to fix it. Has somebody experience with this problem ?
The Astra HD stream has errors always on the same positions in the loop. They show up also with the Reel HDE and the Humax HD1000.
do you think - the reason into not corrected coder or is it decoder's problem ?
When they were simulcasting AstraHD on the Pro7HD and PremiereHD-transponder, only the stream on the PremiereHD-transponder was OK. Now they apparently have moved the faulty stream also to PremiereHD...
the same errors have other h.264 dvb-providers, not only AstraHD. Later I will show the statistic.
Igor
Hi,
Igor schrieb:
during watching of Astra HD+ from Astra 19,2E I always have this errors
We'll need to clarify what "during watching" means. See below for details.
[h264 @ 0xabfba3d0]B picture before any references, skipping [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]B picture before any references, skipping [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]B picture before any references, skipping [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]B picture before any references, skipping [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]B picture before any references, skipping [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]B picture before any references, skipping [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]no frame! ffmpeg_video_dec: error decompressing frame [h264 @ 0xabfba3d0]non existing PPS referenced [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]non existing PPS referenced [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]non existing PPS referenced [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]non existing PPS referenced [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]non existing PPS referenced [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]non existing PPS referenced [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]no frame! ffmpeg_video_dec: error decompressing frame
200 frames delivered, 31 frames skipped, 52 frames discarded video_out: throwing away image with pts 120676128 because it's too old (diff : 25806). video_out: throwing away image with pts 120690172 because it's too old (diff : 43300). video_out: throwing away image with pts 120711478 because it's too old (diff : 73586). vdr: osdflush: n: 4, 76.7, timeout: 0, result: 0 video_out: throwing away image with pts 120732839 because it's too old (diff : 104127).
I think it's ffmpeg's problem, but I don't know how can I solve it. It seems to me, nobody from ffmpeg-devel list doesn't want to fix it. Has somebody experience with this problem ?
The above messages are OK when you switch to this channel because we jump right into the middle of the video stream. So we will see B pictures, which cannot be decoded without it's reference pictures (I or P pictures respectively).
Moreover some pictures reference Picture Parameter Sets (PPS) which have been broadcast just before you switched to the channel, so these pictures cannot be decoded too.
All those errors should go away from the time on, where an IDR picture is seen in the video stream, as all data up to the next IDR picture will not reference any data structures broadcast before the IDR picture.
Let's now come back to the term "during watching": As written above, those messages are OK when switching to a channel. When they appear "during watching" the channel, I could think of VDR having issued a CLEAR as it's buffers ran full for any reason, but your excerpt doesn't show such messages.
Last but not least, the broadcast stream could have been "buggy".
Bye.
Guten Tag, Reinhard
I'm glad to see you :)
during watching of Astra HD+ from Astra 19,2E I always have this errors
We'll need to clarify what "during watching" means. See below for details.
[h264 @ 0xabfba3d0]B picture before any references, skipping [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]B picture before any references, skipping [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]B picture before any references, skipping [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]B picture before any references, skipping [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]B picture before any references, skipping [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]B picture before any references, skipping [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]no frame! ffmpeg_video_dec: error decompressing frame [h264 @ 0xabfba3d0]non existing PPS referenced [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]non existing PPS referenced [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]non existing PPS referenced [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]non existing PPS referenced [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]non existing PPS referenced [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]non existing PPS referenced [h264 @ 0xabfba3d0]decode_slice_header error [h264 @ 0xabfba3d0]no frame! ffmpeg_video_dec: error decompressing frame
200 frames delivered, 31 frames skipped, 52 frames discarded video_out: throwing away image with pts 120676128 because it's too old (diff : 25806). video_out: throwing away image with pts 120690172 because it's too old (diff : 43300). video_out: throwing away image with pts 120711478 because it's too old (diff : 73586). vdr: osdflush: n: 4, 76.7, timeout: 0, result: 0 video_out: throwing away image with pts 120732839 because it's too old (diff : 104127).
I think it's ffmpeg's problem, but I don't know how can I solve it. It seems to me, nobody from ffmpeg-devel list doesn't want to fix it. Has somebody experience with this problem ?
The above messages are OK when you switch to this channel because we jump right into the middle of the video stream. So we will see B pictures, which cannot be decoded without it's reference pictures (I or P pictures respectively).
ok, but I see this errors everytime :(
Moreover some pictures reference Picture Parameter Sets (PPS) which have been broadcast just before you switched to the channel, so these pictures cannot be decoded too.
All those errors should go away from the time on,
ah, it would be fine, but really I have this errors always during the watching AstraHD
where an IDR picture is seen in the video stream, as all data up to the next IDR picture will not reference any data structures broadcast before the IDR picture.
Let's now come back to the term "during watching": As written above, those messages are OK when switching to a channel. When they appear "during watching" the channel, I could think of VDR having issued a CLEAR as it's buffers ran full for any reason, but your excerpt doesn't show such messages.
Last but not least, the broadcast stream could have been "buggy".
what about your VDR system ? Have you the same errors ? 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
Igor
Hi,
Igor schrieb:
I'm glad to see you :)
Well, I was quite busy at work this week.
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. Hence, I regularly see VDR issue CLEARs after which such messages are normal.
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 [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 [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 [h264 @ 0xac236490]no frame! [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 [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 [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 [h264 @ 0xac236490]no frame!
Bye.
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
Hi,
Igor schrieb:
Hence, I regularly see VDR issue CLEARs after which such
messages are normal.
sorry, what do you mean "VDR issue CLEARs" ?
vdr-xine's console output:
video: synced early [vVMA]buffered 8,8 frames (v:25,2, a:8,8) frame: (0, 0)-(1920, 1088), zoom: (1,00, 1,00) buffered 9,3 frames (v:20,4, a:9,3) buffered 10,5 frames (v:25,9, a:10,5) buffered 10,2 frames (v:30,8, a:10,2) <<<<< Clear(0)DiscontinuityDetected: triggering soft start ! video: synced early [vAV]buffered 8,7 frames (v:28,7, a:8,7) buffered 9,3 frames (v:30,1, a:9,3) buffered 10,5 frames (v:30,5, a:10,5) buffered 7,2 frames (v:28,5, a:7,2) <<<<< Clear(1)DiscontinuityDetected: triggering soft start ! video: synced early [VA]buffered 8,5 frames (v:21,5, a:8,5)
VDR's syslog:
May 10 17:31:49 video vdr: [5227] cVideoRepacker: operating in H.264 mode May 10 17:32:01 video vdr: [5228] buffer usage: 70% (tid=5227) May 10 17:32:01 video vdr: [5228] buffer usage: 80% (tid=5227) May 10 17:32:01 video vdr: [5228] buffer usage: 90% (tid=5227) May 10 17:32:01 video vdr: [5228] buffer usage: 100% (tid=5227) May 10 17:32:01 video vdr: [5228] ERROR: 3607 ring buffer overflows (678105 bytes dropped) May 10 17:32:01 video vdr: [5227] clearing transfer buffer to avoid overflows May 10 17:32:02 video vdr: [5228] buffer usage: 0% (tid=5227)
xine's output:
+++ CLEAR(17a): sync point: 1d ao_flush (loop running: 1) === CLEAR(17.1) === CLEAR(17.2) === CLEAR(17.3) === CLEAR(17.4) === CLEAR(17.5) --- CLEAR(17a) ao_close audio_out: no streams left, closing driver audio discontinuity #80, type is 0, disc_off 0 waiting for in_discontinuity update #80 video discontinuity #80, type is 0, disc_off 0 vpts adjusted with prebuffer to 58459551 +++ CLEAR(17b): sync point: 1d ao_flush (loop running: 1) === CLEAR(17.1) === CLEAR(17.2) === CLEAR(17.3) === CLEAR(17.4) === CLEAR(17.5) --- CLEAR(17b)
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 ?
Well, one might consider this an error, but it has no influence on the output. VDR was written for MPEG1/2 and it properly calls cRemux::SetBrokenLink() when necessary, to indicate that the first few B frames shall not be decoded until two reference frames are available.
As there is no such flag in H.264, the function doesn't do anything than logging, that it didn't find a MPEG1/2 GOP header where this flag is located.
May 10 17:38:16 video vdr: [5430] SetBrokenLink: no GOP header found in video packet
Supporting this issue properly in H.264 would mean to not send the first B frames to the output device which is more complex than just setting a single bit. And with the upcoming recording format changes I don't want to address this issue at the moment.
Bye.
-
Georg Acher -
Igor -
Reinhard Nissl