On Sat, 02 Aug 2008 03:52:21 -0400, amol mahamuni <[EMAIL PROTECTED]> wrote: > 3. But data in picture (AVFrame*) is somthing wrong. Meaning - it says > that data is YUV420P. And three buffers in > (AVFrame->data[0],AVFrame->data[2],AVFrame->data[2]) > has size (AVFrame->linesize[0] = 384 , AVFrame->linesize[0] = 192, > AVFrame->linesize[0] = 192) which is wong I think. It shd be 352, 176, > 176
Linesize is not the number of pixels in the row. Linesize is the number of bytes to skip to get from the start of one row to the start of the next row. This is most often used for alignment so that SSE instructions can be used. > 7) I guess the simplest way to decode h.263 over RTP is to implement > support > for RFC2190 in the RTSP/SDP demuxer in libavformat (then, libavformat > will > take care of correctly splitting the stream in frames, etc...). > ==> How to use libavformat? I only have libavcode.dll file. Is it > available withing this (libavcode.dll) Do you have the libav source code? If not, you will need it- the examples are the best documentation available currently. It is found at svn://svn.mplayerhq.hu/ffmpeg/trunk and if you compile it under windows (using MinGW - I have not tried with visual studio), you should get avcodec-##.dll, avformat-##.dll, and avutil-##.dll where "##" is a version number. Since h.263 is not currently supported over RTP, Luca was suggesting that you fill in the missing pieces in libavformat. Then, you can use the library as intended instead of making your application depend on internal parts of the library. (and if you contribute your fix back to the project, other people will maintain it, so that it doens't break as new versions of the library are released) -- Michael Conrad IntelliTree Solutions llc. 513-552-6362 [EMAIL PROTECTED] _______________________________________________ libav-user mailing list [email protected] https://lists.mplayerhq.hu/mailman/listinfo/libav-user
