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
warning.
Shall I send the whole series again?
Regards,
--
Nicolas George
signature.asc
Description: Digital signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
