| Message ID | 20231211163305.970490-1-marth64@proxyid.net |
|---|---|
| State | New |
| Headers | show |
| Series | [FFmpeg-devel,v2] doc/bitstream_filters: add filter_units practical examples for removing closed captions | expand |
| Context | Check | Description |
|---|---|---|
| yinshiyou/make_loongarch64 | success | Make finished |
| yinshiyou/make_fate_loongarch64 | success | Make fate finished |
| andriy/make_x86 | success | Make finished |
| andriy/make_fate_x86 | success | Make fate finished |
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
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 + +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 + @section hapqa_extract Extract Rgb or Alpha part of an HAPQA file, without recompression, in order to create an HAPQ or an HAPAlphaOnly file.
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(+)