From: "Dennis Sädtler via ffmpeg-devel" <ffmpeg-devel@ffmpeg.org> To: "Martin Storsjö" <martin@martin.st> Cc: "Dennis Sädtler" <dennis@obsproject.com>, "Dennis Sädtler via ffmpeg-devel" <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] movenc: Add an option for hiding fragments at the end Date: Mon, 3 Jun 2024 11:38:59 +0200 Message-ID: <a3cfa865-1f2a-c331-d0ad-15027caea338@obsproject.com> (raw) In-Reply-To: <a92711b7-682a-eb74-9111-928271d9186b@martin.st> On 2024-06-03 09:51, Martin Storsjö wrote: >> Finally, I've also had a somewhat cursed thought about having a >> second always-hidden ftyp before the initial moov, which would then >> allow you to use the same file for progressive download and DASH/HLS >> streaming by using range-requests (e.g. via BYTERANGE) to skip the >> first ftyp + mdat header for the init segment and then using the >> fragments as normal. Though that goes beyond the scope of this patch, >> I just had to get it out there in case anybody thinks that might >> actually be fun to try :P > > Oh, that sounds quite cursed indeed. I definitely can see the appeal > of it :-) I guess it'd require some custom tooling to parse out the > relevant byte ranges from it though (or maybe just listening to the > avio marker callbacks?). It would at least require the DASH/HLS manifest creation tooling to understand this hack and skip the first N bytes. As I said this is kind of a fun idea but maybe not entirely practical. > Anyway, Timo had thoughts about the name for this option/flag - do you > have any suggestions to follow up with on that thread? Not really, I think "hide_fragments" is fine. Though perhaps the flag's description could explain what it does in a bit more detail. For OBS I settled on "Hybrid MP4" and calling the process of hiding the fragments a "soft remux", but the name of the flag should probably be a bit more technical. ~Dennis _______________________________________________ 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".
prev parent reply other threads:[~2024-06-03 9:39 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-31 8:53 Martin Storsjö 2024-05-31 12:18 ` Timo Rothenpieler 2024-05-31 12:38 ` Martin Storsjö 2024-06-01 12:38 ` Dennis Sädtler via ffmpeg-devel 2024-06-02 19:36 ` Martin Storsjö 2024-06-02 20:45 ` Dennis Sädtler via ffmpeg-devel 2024-06-03 7:51 ` Martin Storsjö 2024-06-03 9:38 ` Dennis Sädtler via ffmpeg-devel [this message]
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=a3cfa865-1f2a-c331-d0ad-15027caea338@obsproject.com \ --to=ffmpeg-devel@ffmpeg.org \ --cc=dennis@obsproject.com \ --cc=martin@martin.st \ /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