From: Stefano Sabatini <stefasab@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Cc: Marth64 <marth64@proxyid.net> Subject: Re: [FFmpeg-devel] [PATCH] doc/bitstream_filters: add filter_units practical examples for removing closed captions Date: Sun, 10 Dec 2023 01:53:50 +0100 Message-ID: <ZXUMHlzfBp12Z4bY@mariano> (raw) In-Reply-To: <20231209193112.783495-1-marth64@proxyid.net> On date Saturday 2023-12-09 13:31:13 -0600, Marth64 wrote: > --- > doc/bitstream_filters.texi | 17 +++++++++++++++++ > 1 file changed, 17 insertions(+) > > diff --git a/doc/bitstream_filters.texi b/doc/bitstream_filters.texi > index 145aa8684e..b01ede0c93 100644 > --- a/doc/bitstream_filters.texi > +++ b/doc/bitstream_filters.texi > @@ -213,6 +213,23 @@ 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 > > +By nature of removing SEI messages, the filter can also remove Closed Captions. I think you might expand this to shortly explain the relation between Closed Captions and SEI message. Also, I'd avoid the expression "by nature" and replace with a plainer/more explicit expression (as most of the readers are not English speakers). [...] _______________________________________________ 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:[~2023-12-10 0:54 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-09 19:31 Marth64 2023-12-10 0:53 ` Stefano Sabatini [this message] 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 2024-03-10 1:56 [FFmpeg-devel] [PATCH] " Marth64 2024-03-10 14:56 ` Stefano Sabatini 2024-03-10 15:29 ` Marth64
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=ZXUMHlzfBp12Z4bY@mariano \ --to=stefasab@gmail.com \ --cc=ffmpeg-devel@ffmpeg.org \ --cc=marth64@proxyid.net \ /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