Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Marth64 <marth64@proxyid.net>
To: FFmpeg development discussions and patches
	<ffmpeg-devel@ffmpeg.org>, Marth64 <marth64@proxyid.net>
Subject: Re: [FFmpeg-devel] [PATCH] doc/bitstream_filters: add filter_units practical examples for removing closed captions
Date: Sun, 10 Mar 2024 10:29:05 -0500
Message-ID: <CA+28BfBDS5QNc84dJot4GN-MDTMRsmgZYyJ9nBYYbofTJ=nFDw@mail.gmail.com> (raw)
In-Reply-To: <Ze3KJc2RwNnUWLvQ@mariano>

Thanks, Stefano, I agree it’s not ideal with just having magic numbers. If
I think of a creative solution I'll let you know.

Appreciate your time,

On Sun, Mar 10, 2024 at 09:56 Stefano Sabatini <stefasab@gmail.com> wrote:

> On date Saturday 2024-03-09 19:56:49 -0600, Marth64 wrote:
> > Following up on this from December 2023. I simplified the content and
> > hopefully addressed the feedback.
> >
> > Signed-off-by: Marth64 <marth64@proxyid.net>
> > ---
> >  doc/bitstream_filters.texi | 15 +++++++++++++++
> >  1 file changed, 15 insertions(+)
> >
> > diff --git a/doc/bitstream_filters.texi b/doc/bitstream_filters.texi
> > index e06de1a73a..61539d2473 100644
> > --- a/doc/bitstream_filters.texi
> > +++ b/doc/bitstream_filters.texi
> > @@ -213,6 +213,21 @@ 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
> >
> > +To remove all user data from a MPEG-2 stream, including Closed Captions:
> > +@example
> > +ffmpeg -i INPUT -c:v copy -bsf:v 'filter_units=remove_types=178' OUTPUT
> > +@end example
> > +
> > +To remove all SEI from a H264 stream, including Closed Captions:
> > +@example
> > +ffmpeg -i INPUT -c:v copy -bsf:v 'filter_units=remove_types=6' OUTPUT
> > +@end example
> > +
> > +To remove all prefix and suffix SEI from a HEVC stream, including
> Closed Captions and dynamic HDR:
> > +@example
> > +ffmpeg -i INPUT -c:v copy -bsf:v 'filter_units=remove_types=39|40'
> OUTPUT
> > +@end example
> > +
>
> Not against, but I'm not super convinced this is super useful as it
> does not really explain what these values come from.  Probably it
> would be more useful a table, or even better make the parser somehow
> expose the supported types with the meaning (this would enable having
> e.g. a symbolic type "cc" abstracting the containter format).
>
> OTOH I agree thius would provide some practical examples, therefore
> I'll apply while we have no smarter way to expose the logic in a more
> effective way.
>
> Thanks.
>
_______________________________________________
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:[~2024-03-10 15:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-10  1:56 Marth64
2024-03-10 14:56 ` Stefano Sabatini
2024-03-10 15:29   ` Marth64 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-09 19:31 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

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='CA+28BfBDS5QNc84dJot4GN-MDTMRsmgZYyJ9nBYYbofTJ=nFDw@mail.gmail.com' \
    --to=marth64@proxyid.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