Stefano Sabatini: > On date Tuesday 2024-03-12 13:25:23 +0100, Andreas Rheinhardt wrote: >> Stefano Sabatini: >>> --- >>> doc/muxers.texi | 30 ++++++++++++++++++++++++++++++ >>> 1 file changed, 30 insertions(+) >>> > [...] >> I do not think that this muxer should be publically documented. In fact, >> I think it would be better if this muxer would only exist inside the >> fifo_muxer test and if it were not included in a normal libavformat at all. > > It looks like it is not possible to register a custom muxer outside of > the list in allformats.c, or do I miss something? (OTOH it would be > useful if one wants to registers a custom component, but this seems to > be disabled at the API level). >
It is possible to use custom muxers internally: The AVOutputFormat* pointer one passes to avformat_alloc_output_context2() need not be in the list of output formats in the lists in allformats.c/alldevices.c. In order to make the fifo muxer actually use a custom muxer, a slight hack is needed. See https://ffmpeg.org/pipermail/ffmpeg-devel/2024-March/323314.html > The simple alternative is to simply not to document the muxer, > although I don't like it very much, given that is output in the muxers > list, so I think at least we want to mention that this is only used > for testing. Given that this muxer is dangerous (see the above commit message) it should not be publicly accessible at all. - Andreas _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
