Hi Anand,

Not sure exactly what you mean. Are you asking about:

(1) The number of bits required to code each picture (e.g., "911376 bits 
for the I frame, 115936 for the B frame after it, etc.")? For this, you'll 
have to call mpeg2_getpos() to get the position in the stream as you hit 
PICTURE headers.

(2) The horizontal and vertical sizes of the luma and chroma matrices. 
These are in the sequence header -- see the code to dump_state.c for an 
example. E.g., "1920x1088 for luma, 960x544 for chroma".

(3) The intended displayed area of the frame (e.g., "1920x1080"). This is 
in the sequence display extension header, also printed out by dump_state.c 
("seq->display_width", etc.).

Sizes #2 and #3 are not allowed to vary on a picture-by-picture basis. 
Only by ending the sequence and then starting a new sequence can you 
change the size of the image. (A picture display extension header can vary 
the location of the "display rectangle" within the full luma and chroma 
matrices, but it can't change the dimensions of the "display rectangle.")

Hope that helps. If you can be more specific I'd be happy to help further.

Best,
Keith

On Wed, 4 Apr 2007, anand meher wrote:

> Hi,
>      i am trying to find the frame sizes of the individual i,b,p frame
> sizes using libmpeg2.the current picture data structure does not provide
> with the frame size.so is there any other way  to find the frame sizes
> usiiiing libmpeg2. i am using the decode function in mpeg2dec.c program of
> libmpeg2.
>
> thanks in advance
>

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Libmpeg2-devel mailing list
Libmpeg2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmpeg2-devel

Reply via email to