[FFmpeg-devel] [PATCH v3 3/3] avformat/avio{, buf}: introduce public AVIOContext::bytes_{read, written}

[Michael Niedermayer]

On Mon, Oct 18, 2021 at 03:47:23PM +0300, Jan Ekström wrote:
> Such fields can be seen as generally useful in cases where the
> API user is not implementing custom AVIO callbacks, but still would
> like to know if data is being read or written out, such as in case
> data is being read from input but no AVPacket has been received yet.
> ---
>  doc/APIchanges              |  3 +++
>  libavformat/avio.h          | 14 +++++++++++++-
>  libavformat/avio_internal.h |  5 +++++
>  libavformat/aviobuf.c       | 10 ++++++++--
>  libavformat/version.h       |  2 +-
>  5 files changed, 30 insertions(+), 4 deletions(-)

Probably ok

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

I have never wished to cater to the crowd; for what I know they do not
approve, and what they approve I do not know. -- Epicurus
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <https://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20211019/2e1dce23/attachment.sig>