Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Niklas Haas <ffmpeg@haasn.xyz>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v2 1/4] avcodec/aom_film_grain: add AOM film grain synthesis
Date: Fri, 8 Mar 2024 14:44:17 +0100
Message-ID: <20240308144417.GB30572@haasn.xyz> (raw)
In-Reply-To: <186f152d-122a-4400-b941-526c986d0c56@gmail.com>

On Fri, 08 Mar 2024 10:31:28 -0300 James Almer <jamrial@gmail.com> wrote:
> On 3/8/2024 10:21 AM, Niklas Haas wrote:
> > From: Niklas Haas <git@haasn.dev>
> > 
> > Implementation copied wholesale from dav1d, sans SIMD, under permissive
> > license. This implementation was extensively verified to be bit-exact,
> > so it serves as a much better starting point than trying to re-engineer
> > this from scratch for no reason. (I also authored the original
> > implementation in dav1d, so any "clean room" implementation would end up
> > looking much the same, anyway)
> > 
> > The notable changes I had to make while adapting this from the dav1d
> > code-base to the FFmpeg codebase include:
> > 
> > - reordering variable declarations to avoid triggering warnings
> > - replacing several inline helpers by avutil equivalents
> > - changing code that accesses frame metadata
> > - replacing raw plane copying logic by av_image_copy_plane
> > 
> > Apart from this, the implementation is basically unmodified.
> 
> Do we want this to be public? Both as a struct and the decoding functions.
> It could be used by libavfilter or even outside our libraries. The hevc 
> decoder would export the relevant T.35 SEI in the new struct if told to 
> not apply fg, like we already do in av1.

I'm not sure if the AFGS1 struct itself needs to be public, since it is
largely just a codec-internal wrapper for multiple param sets (for
scalable codecs).

If we want to add a public film grain synthesis helper, IMHO it should
be a wrapper around both ff_aom_apply_film_grain *and*
ff_h274_apply_film_grain, which directly ingests an AVFilmGrainParams
and resolves to the correct implementation.

So we can merge this series as-is and still add a public helper on top.

Incidentally, there is a strong precedent here: dav1d.h exports
dav1d_apply_grain() precisely for the reason that VLC needs to
initialize the decoder *before* it knows whether to apply synthesis on
GPU or CPU, so it has to set the equivalent of `-export_side_data
film_grain` at init time and manually apply CPU film grain synthesis if
it turns out that GPU fgs is unavailable.
_______________________________________________
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-08 13:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-08 13:21 Niklas Haas
2024-03-08 13:21 ` [FFmpeg-devel] [PATCH v2 2/4] avcodec/aom_film_grain: implement AFGS1 Niklas Haas
2024-03-08 13:28   ` Niklas Haas
2024-03-08 13:21 ` [FFmpeg-devel] [PATCH v2 3/4] avcodec/h2645_sei: decode AFGS1 T.35 SEI Niklas Haas
2024-03-08 13:21 ` [FFmpeg-devel] [PATCH v2 4/4] avcodec/hevcdec: apply AOM film grain synthesis Niklas Haas
2024-03-08 13:31 ` [FFmpeg-devel] [PATCH v2 1/4] avcodec/aom_film_grain: add " James Almer
2024-03-08 13:44   ` Niklas Haas [this message]
2024-03-11 22:32     ` Mark Thompson
2024-03-12 21:40       ` Niklas Haas
2024-03-15 10:17 ` Niklas Haas
  -- strict thread matches above, loose matches on Subject: below --
2024-02-29 12:33 Niklas Haas
2024-02-29 12:43 ` Niklas Haas
2024-02-29 12:50   ` Andreas Rheinhardt

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=20240308144417.GB30572@haasn.xyz \
    --to=ffmpeg@haasn.xyz \
    --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