Hi Huy, thanks for the example picture and the link to the viewer. It's very clear to me now. I used the "JM reference encoder" from Heinrich Hertz Institut (http://iphome.hhi.de/suehring/tml/), but I used a preconfigured flag (I forgot to deactivate it), which generates multiple PPS and with your mentioned viewer I can see a structure of SPS, PPS, PPS, PPS, IDR (only 1 slice!). Thus 3 different PPS with different IDs in a row, that MIGHT confuse ffmpeg, if it expects the IDR right after the first PPS, but I'm not sure about that. I reencode and go on with your suggested method ([785] ...)
cheers Sven 2010/9/20 Huy Tran <[email protected]>: > Hi Alex and Sven, > > I sent to you an image about the H.264 AnnexB payload format (file format). > > > http://img13.imageshack.us/img13/7995/h264d.jpg > > I create this bitstream by using x264: * x264.exe --slices 4 -o output.264 > input.yuv 1920x1080* > My bitstream has 5 frames and each frame has 4 slices. Thus I have total 20 > slices. > I use "H.264 Video ES Viewer" to check the length, starcode, nal_unit_type > and so on. > > To decode this bitstream in FFmpeg, you have to collect 4 slices data of a > whole frame before passing it to avcodec_decode_video. > You also have to calculate exactly the length of each slices, FFmpeg need it > to decode H.264. > > Hope it helps. > Huy. > _______________________________________________ > libav-user mailing list > [email protected] > https://lists.mplayerhq.hu/mailman/listinfo/libav-user > _______________________________________________ libav-user mailing list [email protected] https://lists.mplayerhq.hu/mailman/listinfo/libav-user
