[FFmpeg-devel] [PATCH 2/3] lavf/avio: temporarily accept 0 as EOF.

Nicolas George george at nsup.org
Fri Oct 27 21:30:08 EEST 2017

Le sextidi 6 brumaire, an CCXXVI, Jan Ekstrom a écrit :
> Built and tested locally and the effect seems to be the one wished,
> although it seems like it is complaining about the AVClass being
> nullptr? Is this something inherent to custom AVIO contexts and it's
> the client that's supposed to fix this? Log follows:
> > [ffmpeg] av_log callback called with bad parameters (NULL AVClass).
> > [ffmpeg] This is a bug in one of Libav/FFmpeg libraries used.
> > [ffmpeg] Invalid return value 0 for stream protocol

Thanks. It seems custom AVIOContext are not real AVIOContext in the full
meaning, and there are glitches in fixing that.

I have locally changed the log line:

	av_log(NULL, AV_LOG_WARNING, "Invalid

Not completely satisfactory, but enough for a library-to-application

Shall I send the whole series again?


  Nicolas George
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Digital signature
URL: <http://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20171027/9a5be5f1/attachment.sig>

More information about the ffmpeg-devel mailing list