On Tue, May 4, 2021 at 5:52 PM Derek Buitenhuis <derek.buitenh...@gmail.com> wrote: > > On 03/05/2021 22:05, Steinar H. Gunderson wrote: > > Two reasons: > > > > - As the commit message says, it is desirable to have this on pipe output > > as > > well (Cubemap would like to fork out to FFmpeg to do remuxing etc. for > > it, without having to speak HTTP over the pipe). > > - The HTTP layer does not have the information about what is a header etc., > > so it would need to be plumbed down the layers. I tried this at first, > > but > > it got markedly more intrusive than this, so I left it pretty early on. > > Can this not be accomplished outside of FFmpeg, by registering your own I/O > callbacks? That would seem to me to be the 'proper' way to do this. More > work? Yes. But less hacky. > > I am in agreement that the current placement inside AVIO itself is king of > horrible. >
I agree with that. AVIO is supposed to be generic IO abstraction, something like this has no place in it. AVIO already allows for various callbacks, if needed that framework can be extended, without putting a lot of very specific code into a place it doesn't belong. - Hendrik _______________________________________________ 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".
