From: Jack Lau <jacklau1222gm@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: [FFmpeg-devel] avoption: make the avoption like seekable more general Date: Tue, 11 Feb 2025 17:53:51 +0800 Message-ID: <A87DAA52-4792-4B32-BB61-966D1F25CFAB@gmail.com> (raw) Hi everyone, I’m trying to solve this issue https://trac.ffmpeg.org/ticket/11394. This ticket shows that we need use `-seekable` and `-http_seekable` to control the range header if send. Because these options belong to different file(hls.c and http.c) So I try to modify the http_seekable to seekable in hls.c, but I realized the avoption parameter will be released after being used once. In that case, the init_input and read_header functions in avformat_open_input of demux.c used avoption successively, resulting in no seekable parameter in the second part of the http request (it has been used and released by init_input). So the second part of http request still not controled by the seekable option. I think it’s necessary to make the avoption used be more general, it can be more friendly to users, there is no need for users to use two options for the same function. So I have two solutions here: 1. Do not release avoption immediately after use, to ensure that all avoptions have a complete life cycle in avformat_open_input, but this will cause a problem, that is, it is impossible to determine which options are used and which are not used. 2. Add new avoption type like general_avoption which has a longer life cycle than ordinary avoption, so that ordinary avoption can still retain the feature of being detected whether it is used. Anyone feel free to give me some advice, I really want to make some contribution for this issue. Thanks Jack _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
reply other threads:[~2025-02-11 9:54 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=A87DAA52-4792-4B32-BB61-966D1F25CFAB@gmail.com \ --to=jacklau1222gm@gmail.com \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git