L'octidi 8 vendémiaire, an CCXXV, wm4 a écrit : > This seems like a rather special use case. Why does it have a demuxer, > and can't be in your own C code using libavcodec/libavformat?
Of course, it can. It just takes more effort overall. You do not believe that Stefano and I both started working on a similar project on a whim, do you? We did it because we felt it would gain time in the long run. Once the demuxer is there, it is ready for all uses. I very often have samples triggering bugs that I want to tweak to see what is causing the bug exactly: timestamps, order of packets, even the payload. Editing them with a powerful text editor or a perl one-liner beats anything in terms of efficiency to do so. > In addition, I think using the ffprobe "format" is an overcomplication, > and will justify adding even more stuff to the demuxer, until it's a > similarily complex mess like the ffm demuxer/muxer. This looks like a "slippery slope" fallacy. Since it is clearly useful almost only for developers doing debugging, I would not mind having no probe function or even disabled by default, making it a non-issue security-wise. Beyond that, I have yet to see an actual argument against it. Regards, -- Nicolas George
signature.asc
Description: Digital signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
