From: Philip Langdale <philipl@overt.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v3] avcodec/nvenc: add AV1 encoding support
Date: Sat, 5 Nov 2022 10:08:04 -0700
Message-ID: <20221105100804.647155c6@fido7> (raw)
In-Reply-To: <20221104114016.203-1-timo@rothenpieler.org>
On Fri, 4 Nov 2022 12:40:16 +0100
Timo Rothenpieler <timo@rothenpieler.org> wrote:
> The encoder seems to be trading blows with hevc_nvenc.
> In terms of quality at low bitrate cbr settings, it seems to
> outperform it even. It produces fewer artifacts and the ones it
> does produce are less jarring to my perception.
>
> At higher bitrates I had a hard time finding differences between
> the two encoders in terms of subjective visual quality.
>
> Using the 'slow' preset, av1_nvenc outperformed hevc_nvenc in terms
> of encoding speed by 75% to 100% while performing above tests.
>
> Needless to say, it always massively outperformed h264_nvenc in terms
> of quality for a given bitrate, while also being slightly faster.
Obviously not able to test, but looks reasonable to me.
--phil
_______________________________________________
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".
prev parent reply other threads:[~2022-11-05 17:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 23:59 [FFmpeg-devel] [PATCH] " Timo Rothenpieler
2022-11-02 1:14 ` Andreas Rheinhardt
2022-11-02 10:12 ` Timo Rothenpieler
2022-11-02 20:51 ` [FFmpeg-devel] [PATCH v2] " Timo Rothenpieler
2022-11-04 11:40 ` [FFmpeg-devel] [PATCH v3] " Timo Rothenpieler
2022-11-05 17:08 ` Philip Langdale [this message]
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=20221105100804.647155c6@fido7 \
--to=philipl@overt.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