On Mon, Mar 06, 2017 at 10:38:12AM +0100, wm4 wrote: > --- a/libavcodec/avcodec.h > +++ b/libavcodec/avcodec.h > @@ -161,7 +168,20 @@ > + * A codec is not allowed to return EAGAIN for both sending and receiving. > This > + * would be an invalid state, which could put the codec user into an endless > + * loop. The API has no concept of time either: it cannot happen that trying > to > + * do avcodec_send_packet() results in EAGAIN, but a repeated call 1 second > + * later accepts the packet (with no other receive/flush API calls involved). > + * The API is a strict state machine, and the passage of time is not supposed > + * to influence it. As long as it never results to both send/receive > returning
never results in > + * both EAGAIN at the same time at any point, and no "flip flopping" between > the > + * send/receive APIs is possible (e.g. the codec randomly deciding that it > + * actually wants to consume a packet now instead of returning a frame, > after it > + * just has returned EAGAIN on an avcodec_send_packet() call), such behavior > + * might still be deemed acceptable. The last sentence reads awkward. I think it might improve if you switch beginning and end around by starting with "such behavior might still...". Diego _______________________________________________ libav-devel mailing list libav-devel@libav.org https://lists.libav.org/mailman/listinfo/libav-devel
