From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com> To: ffmpeg-devel@ffmpeg.org Cc: Andreas Rheinhardt <andreas.rheinhardt@outlook.com> Subject: [FFmpeg-devel] [PATCH] doc/bitstream_filters.texi: Document types used by filter_units Date: Sun, 10 Mar 2024 16:34:23 +0100 Message-ID: <AS8P250MB074487C14BF6E732FA156A5D8F252@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM> (raw) Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com> --- doc/bitstream_filters.texi | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/doc/bitstream_filters.texi b/doc/bitstream_filters.texi index 61539d2473..3351625225 100644 --- a/doc/bitstream_filters.texi +++ b/doc/bitstream_filters.texi @@ -199,6 +199,13 @@ Identical to @option{pass_types}, except the units in the given set removed and all others passed through. @end table +The types used by pass_types and remove_types correspond to NAL unit types +(nal_unit_type) in H.264, HEVC and H.266 (see Table 7-1 in the H.264 +specification and HEVC specifications or Table 5 for H.266), to +marker values for JPEG (without 0xFF prefix), to start codes without +start code prefix (i.e. the byte following the 0x000001) for MPEG-2. +For VP8 and VP9, every unit has type zero. + Extradata is unchanged by this transformation, but note that if the stream contains inline parameter sets then the output may be unusable if they are removed. -- 2.40.1 _______________________________________________ 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 reply other threads:[~2024-03-10 15:34 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-10 15:34 Andreas Rheinhardt [this message] 2024-03-10 15:52 ` Stefano Sabatini 2024-03-10 16:21 ` 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=AS8P250MB074487C14BF6E732FA156A5D8F252@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM \ --to=andreas.rheinhardt@outlook.com \ --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