From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH 2/2] avformat/hls: .ts is always ok even if its a mov/mp4 Date: Wed, 5 Feb 2025 19:21:44 +0100 Message-ID: <20250205182144.GC4991@pb2> (raw) In-Reply-To: <33dadb2c-3081-4bbc-aff7-73be15eacc05@gmail.com> [-- Attachment #1.1: Type: text/plain, Size: 2188 bytes --] Hi Traneptora On Tue, Feb 04, 2025 at 06:35:07PM -0500, Leo Izen wrote: > > > On 1/28/25 4:44 PM, Michael Niedermayer wrote: > > Hi > > > > On Tue, Jan 28, 2025 at 10:12:30PM +0200, Jan Ekström wrote: > > > On Tue, Jan 28, 2025 at 4:24 PM Michael Niedermayer > > > <michael@niedermayer.cc> wrote: > > > > > > > > Maybe fixes: 11435 > > > > > > > > > > Do I understand correctly that the root issue that's being attempted > > > to be fixed by the initial patch set is that unusual demuxers were > > > possible to have been probed and opened through the HLS meta demuxer? > > > In that case I would say that instead of trying to make very nebulous > > > and easily breakable extension based checking, maybe this demuxer > > > should just limit its default usable input formats? > > > > > > To my knowledge the officially utilized container formats for HLS are > > > MPEG-TS, MP4-likes (fragmented mp4) and raw audio formats such as AAC, > > > MP3 or AC-3. One could check what hls.js or ExoPlayer support, and > > > that should be a generally mostly encompassing thing that does not > > > depend on what extensions are in use. Adding an AVOption to add > > > additional formats without code changes would then allow for some > > > outliers to be added by users. > > > > there is extended M3U > > https://en.wikipedia.org/wiki/M3U > > > > that allows a wide range of things in it > > > > our hls demuxer can read these, if we limit to mpeg-ts/mp4 we would remove > > support for these. > > > > From reading this, it seems like we're using the same demuxer for both HLS > streams (specified informationally in RFC 8216) as well as for generic m3u > playlists, and changes to the HLS implementation for security reasons also > change the M3U demuxer. > > Why don't we just separate this into two different demuxers/protocols? yes, i was thinking the same, we should do this for git master thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB "Nothing to hide" only works if the folks in power share the values of you and everyone you know entirely and always will -- Tom Scott [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 195 bytes --] [-- Attachment #2: Type: text/plain, Size: 251 bytes --] _______________________________________________ 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".
next prev parent reply other threads:[~2025-02-05 18:21 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-01-28 14:24 [FFmpeg-devel] [PATCH 1/2] avformat/hls: Print input format in error message Michael Niedermayer 2025-01-28 14:24 ` [FFmpeg-devel] [PATCH 2/2] avformat/hls: .ts is always ok even if its a mov/mp4 Michael Niedermayer 2025-01-28 20:12 ` Jan Ekström 2025-01-28 21:44 ` Michael Niedermayer 2025-02-04 11:45 ` Kacper Michajlow 2025-02-05 18:41 ` Michael Niedermayer 2025-02-05 23:51 ` Michael Niedermayer 2025-02-04 23:35 ` Leo Izen 2025-02-05 18:21 ` Michael Niedermayer [this message] 2025-01-28 22:24 ` Michael Niedermayer
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=20250205182144.GC4991@pb2 \ --to=michael@niedermayer.cc \ --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