On 2009-08-05 at 11:09:40 [+0200], Sven Alisch <[email protected]> wrote: > Dear Stephan, hello everyone, > > Thank you Stephan for your detailed explainations. I understood it. Now I > come to the conclusion, that the support for 1080i h.264 coded streams in > libav is not very well (Sorry I don't want to cry or to be unpolite!!! > libav is a good library!!!). > > At now I want to know, when does av_read_frame support reading > interleaced h.264 frames corectly? Is it planned?
What version of the library are you using? I am using the 0.5 release and there is works well for 1080i in "AVC-HD" clips from my Sony Camera, i.e. the special mpegts container with h.264 stream. IMHO, it doesn't work perfect, since I think it is an error to report a field rate of 50.0 (correct) from the libavformat, but reporting a frame height of the full frame (does not match the frame rate), and also decoding only complete frames (at 25.0 fps) later on in libavcodec. Of course if you use libavcodec to do the deinterlacing, and if you ignore the incorrect frame rate, it is actually more convenient. I would just like a flag from the demuxer, which tells you *before* decoding if something will be interlaced. Best regards, -Stephan _______________________________________________ libav-user mailing list [email protected] https://lists.mplayerhq.hu/mailman/listinfo/libav-user
