From: Mark Thompson <sw@jkqxz.net> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH v2] doc/bitstream_filters: add filter_units practical examples for removing closed captions Date: Mon, 11 Dec 2023 20:27:40 +0000 Message-ID: <1d84b346-9b97-434b-b5ef-28e9a5993eee@jkqxz.net> (raw) In-Reply-To: <20231211163305.970490-1-marth64@proxyid.net> On 11/12/2023 16:33, Marth64 wrote: > Added v2 label and signed off as per proper procedure. > > Signed-off-by: Marth64 <marth64@proxyid.net> > --- > doc/bitstream_filters.texi | 18 ++++++++++++++++++ > 1 file changed, 18 insertions(+) > > diff --git a/doc/bitstream_filters.texi b/doc/bitstream_filters.texi > index dc4f85bac0..7c36c5346d 100644 > --- a/doc/bitstream_filters.texi > +++ b/doc/bitstream_filters.texi > @@ -213,6 +213,24 @@ To remove all AUDs, SEI and filler from an H.265 stream: > ffmpeg -i INPUT -c:v copy -bsf:v 'filter_units=remove_types=35|38-40' OUTPUT > @end example > > +SEI messages are commonly used to contain Closed Captions as well as other metadata such as dynamic HDR. > +This filter can be used to remove the SEI messages if desired. > + > +To remove SEI messages (including CC) from a MPEG-2 stream: > +@example > +ffmpeg -i INPUT -c:v copy -bsf:v 'filter_units=remove_types=178' OUTPUT > +@end example MPEG-2 doesn't call these SEI, it is simply "user data". > + > +To remove SEI messages (including CC) from a H264 stream: > +@example > +ffmpeg -i INPUT -c:v copy -bsf:v 'filter_units=remove_types=6' OUTPUT > +@end example > + > +To remove SEI messages (including CC and dynamic HDR) from a HEVC stream: > +@example > +ffmpeg -i INPUT -c:v copy -bsf:v 'filter_units=remove_types=39' OUTPUT > +@end example Are closed captions allowed in suffix SEI as well? T.35 messages are certainly allowed there. (I'm mildly inclined to think that a more specific bitstream filter able to mess with the SEI types would be more useful? This approach feels like it has a lot of collateral damage.) Thanks, - Mark _______________________________________________ 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:[~2023-12-11 20:27 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-09 19:31 [FFmpeg-devel] [PATCH] " Marth64 2023-12-10 0:53 ` Stefano Sabatini 2023-12-10 1:26 ` Marth64 2023-12-10 1:35 ` Marth64 2023-12-10 3:06 ` Leo Izen 2023-12-10 3:17 ` Marth64 2023-12-11 23:29 ` Stefano Sabatini 2023-12-11 16:33 ` [FFmpeg-devel] [PATCH v2] " Marth64 2023-12-11 20:27 ` Mark Thompson [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=1d84b346-9b97-434b-b5ef-28e9a5993eee@jkqxz.net \ --to=sw@jkqxz.net \ --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