On 10/26/2021 4:14 PM, Derek Buitenhuis wrote: > In 45bfe8b838275235412777dd430206d9a24eb3ee, short_seek_threshold was removed > from the public AVIO struct. Although this option was private and not intended > to be used by public API users, it was nonetheless, because it provided > functionality > that could otherwise not be gained via public API. > > This was especially important for networked I/O like HTTP, where the internal > size for lavf could be way to small depending on the specifics of a user's > usecase, such as reading interlavd media files from cloud storage. > > Add an AVOption to make this functionality accessible to the HTTP client. > > Signed-off-by: Derek Buitenhuis <derek.buitenh...@gmail.com> > --- > libavformat/http.c | 4 ++++ > 1 file changed, 4 insertions(+)
Ping. We discussed this a bit on IRC and people are open to adding this, but the question is whether we should re-add the old option during this ABI unstability period, or whether AVOptions on specific protocols makes more sense. My gut says re-adding to AVIO, since AVOptions on specific protos seems kinda weirdly specific/restrictive, but my opinion is not a stong one. Any comments or opinion? If not, I'll send a v2 which adds it to AVIO. - Derek _______________________________________________ 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".
