Differences

This shows you the differences between two versions of the page.

--- ffmpeg:av_read_frame [2007/11/22 17:00] – deva
+++ ffmpeg:av_read_frame [2007/11/22 17:03] (current) – deva
@@ Line 5: / Line 5: @@
 Return the next frame of a stream.\\
-The returned packet is valid until the next av_read_frame() or until av_close_input_file() and must be freed with av_free_packet. For video, the packet contains exactly one frame. For audio, it contains an integer number of frames if each frame has a known fixed size (e.g. PCM or ADPCM data). If the audio frames have a variable size (e.g. MPEG audio), then it contains one frame.\\
+The returned packet is valid until the next [[ffmpeg:av_read_frame()]] or until [[ffmpeg:av_close_input_file()]] and must be freed with [[ffmpeg:av_free_packet()]]. For video, the packet contains exactly one frame. For audio, it contains an integer number of frames if each frame has a known fixed size (e.g. PCM or ADPCM data). If the audio frames have a variable size (e.g. MPEG audio), then it contains one frame.\\
-pkt->pts, pkt->dts and pkt->duration are always set to correct values in AVStream.timebase units (and guessed if the format cannot provided them). pkt->pts can be AV_NOPTS_VALUE if the video format has B frames, so it is better to rely on pkt->dts if you do not
-decompress the payload.
+''pkt->pts'', ''pkt->dts'' and ''pkt->duration'' are always set to correct values in ''AVStream.timebase'' units (and guessed if the format cannot provided them). ''pkt->pts'' can be ''AV_NOPTS_VALUE'' if the video format has B frames, so it is better to rely on ''pkt->dts'' if you do not decompress the payload.
 <code c>
 int av_read_frame(AVFormatContext *s,