From: Dale Curtis <dalecurtis@chromium.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] PATCH] Make H.274 film grain support optional for H.264. Saves ~779kb.
Date: Tue, 13 Aug 2024 13:08:51 -0700
Message-ID: <CAPUDrwfLn7VnKyOQjOVbeJbZM6ktSfjtWmwkZzAtQq45N_R1Sw@mail.gmail.com> (raw)
In-Reply-To: <840d1e0e-17a1-481e-82df-44ed855c05cf@gmail.com>
Thanks, disable-h274-film-grain and applying it to hevc too sgtm. I'll wait
to see what Niklas says before updating though.
- dale
On Tue, Aug 13, 2024 at 12:47 PM James Almer <jamrial@gmail.com> wrote:
> On 8/13/2024 4:31 PM, Dale Curtis wrote:
> > Film grain support adds a huge amount of overhead to the H264Context
> > structure for a feature that is rarely used. On low end devices or
> > pages that have lots of media this bloats memory usage rapidly.
> >
> > This introduces a --disable-h264-film-grain option which makes
> > these fields optional and reduces the H264Context size from
> > 851808 bytes to 53444 bytes.
> >
> > Bug: https://crbug.com/359358875
> > Signed-off-by: Dale Curtis <dalecurtis@chromium.org>
> >
> > Note: I'm not sure this is the right way to go about making this
> optional,
> > please
> > let me know if there's a better way.
> >
> > - dale
>
> The proper name for the option and define should be H274, or simply
> film_grain if you're also including AV1FG in it.
> I'm not against a change like this, but it needs to be thorough like we
> did with iamfenc and iamfdec, and there's more code handling film grain
> in other modules.
>
> Not sure what Niklas thinks.
>
> _______________________________________________
> 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".
>
_______________________________________________
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:[~2024-08-13 20:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 19:31 Dale Curtis
2024-08-13 19:47 ` James Almer
2024-08-13 20:08 ` Dale Curtis [this message]
2024-08-13 20:10 ` Hendrik Leppkes
2024-08-13 21:38 ` Dale Curtis
2024-08-14 6:29 ` Christophe Gisquet
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=CAPUDrwfLn7VnKyOQjOVbeJbZM6ktSfjtWmwkZzAtQq45N_R1Sw@mail.gmail.com \
--to=dalecurtis@chromium.org \
--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