From: Tobias Rapp <t.rapp@noa-archive.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avcodec: Add dv marker bsf
Date: Tue, 8 Mar 2022 09:49:14 +0100
Message-ID: <588b1d9f-c249-9acf-09d7-991682483710@noa-archive.com> (raw)
In-Reply-To: <20220307231743.28998-1-michael@niedermayer.cc>
On 08/03/2022 00:17, Michael Niedermayer wrote:
> Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
> ---
> doc/bitstream_filters.texi | 15 ++++
> libavcodec/Makefile | 1 +
> libavcodec/bitstream_filters.c | 1 +
> libavcodec/dv_error_marker_bsf.c | 117 +++++++++++++++++++++++++++++++
> 4 files changed, 134 insertions(+)
> create mode 100644 libavcodec/dv_error_marker_bsf.c
>
> diff --git a/doc/bitstream_filters.texi b/doc/bitstream_filters.texi
> index a0092878c8..6a882ade97 100644
> --- a/doc/bitstream_filters.texi
> +++ b/doc/bitstream_filters.texi
> @@ -132,6 +132,21 @@ the header stored in extradata to the key packets:
> ffmpeg -i INPUT -map 0 -flags:v +global_header -c:v libx264 -bsf:v dump_extra out.ts
> @end example
>
> +@section dv_error_marker
> +
> +Blocks in DV which are marked as damaged are replaced by blocks of the specified color.
> +
> +@table @option
> +@item color
> +The color to replace damaged blocks by
> +@item sta
> +The error status to replace. If -1 then the stamask is used. -1 is the default.
> +@item stamask
> +A 16 bit mask which specifies which of the 16 possible error status values are
> +to be replaced by colored blocks. 0xFFFE is the default which replaces all non 0
> +error status values.
> +@end table
> +
> @section eac3_core
> [...]
In my opinion it would be more user-friendly to use a single "status"
option of AV_OPT_TYPE_FLAGS with "s0" ... "s15" constants, instead of
the "sta"/"stamask" option pair. Maybe there also could be constants for
hard errors (STA = 0111 / 1111) and error concealment types A/B/C to
make the option value readable.
Also it would be nice to add the link to S314M documentation pages also
in the option documentation.
Regards,
Tobias
_______________________________________________
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:[~2022-03-08 8:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 23:17 Michael Niedermayer
2022-03-08 8:49 ` Tobias Rapp [this message]
2022-03-12 18:11 Michael Niedermayer
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=588b1d9f-c249-9acf-09d7-991682483710@noa-archive.com \
--to=t.rapp@noa-archive.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