On Tue, 18 Apr 2017 12:31:25 +0200
Michael Niedermayer <mich...@niedermayer.cc> wrote:

> Signed-off-by: Michael Niedermayer <mich...@niedermayer.cc>
> ---
>  libavcodec/avcodec.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/libavcodec/avcodec.h b/libavcodec/avcodec.h
> index ee133712b5..2ac1523a36 100644
> --- a/libavcodec/avcodec.h
> +++ b/libavcodec/avcodec.h
> @@ -4960,7 +4960,7 @@ int avcodec_decode_subtitle2(AVCodecContext *avctx, 
> AVSubtitle *sub,
>   *                  Unlike with older APIs, the packet is always fully 
> consumed,
>   *                  and if it contains multiple frames (e.g. some audio 
> codecs),
>   *                  will require you to call avcodec_receive_frame() multiple
> - *                  times afterwards before you can send a new packet.
> + *                  times afterwards.
>   *                  It can be NULL (or an AVPacket with data set to NULL and
>   *                  size set to 0); in this case, it is considered a flush
>   *                  packet, which signals the end of the stream. Sending the

How did the old text imply that, and how does the new text remove this
implication? Because I can't see either.

This removes the important fact that you can't just call receive at
"any time", but that it must happen before you call send again.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel

Reply via email to