From: Timo Rothenpieler <timo@rothenpieler.org>
To: Roman Arzumanyan <r.arzumanyan@visionlabs.ai>,
FFmpeg development discussions and patches
<ffmpeg-devel@ffmpeg.org>
Cc: Diego Felix de Souza <ddesouza@nvidia.com>
Subject: Re: [FFmpeg-devel] [PATCH] avcodec/nvenc: High bit depth encoding for HEVC
Date: Thu, 18 Apr 2024 15:33:06 +0200
Message-ID: <2540329d-79aa-4996-a566-b7b55299de0c@rothenpieler.org> (raw)
In-Reply-To: <CAJZRZVk+YN1e8FaLqLA1may9RJHD4-RyLS4hOvkz4GKRds0_jg@mail.gmail.com>
On 18/04/2024 14:29, Roman Arzumanyan wrote:
> Hi Diego,
> Asking for my own education.
>
> As far as you've explained, the 8 > 10 bit conversion happens within the
> driver, that's understandable.
> But how does it influence the output? Does it perform some sort of
> proprietary SDR > HDR conversion under the hood that maps the ranges?
> What's gonna be the user observable difference between these 2 scenarios?
> 1) 8 bit input > HEVC 8 bit profile > 8 bit HEVC output
> 2) 8 bit input > 10 bit up conversion > HEVC 10 bit profile > 10 bit
> HEVC output
>
> Better visual quality? Smaller compressed file size?
> In other words, what's the purpose of this feature except enabling new
> Video Codec SDK capability?
Video Codecs tend to be more efficient with 10 bit, even if it's just 8
bit content that's been up-converted to 10 bit.
I.e. yes, it'll (Or can, at least. Not sure if it's a given.) produce
smaller/higher quality content for the same input.
As for the exact reason, I can't explain, but it's a well known concept.
_______________________________________________
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-04-18 13:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 14:39 Diego Felix de Souza via ffmpeg-devel
2024-04-17 14:27 ` Timo Rothenpieler
2024-04-18 10:43 ` Diego Felix de Souza via ffmpeg-devel
2024-04-18 12:29 ` Roman Arzumanyan
2024-04-18 13:33 ` Timo Rothenpieler [this message]
2024-04-19 7:39 ` Roman Arzumanyan
2024-04-19 8:33 ` Diego Felix de Souza via ffmpeg-devel
2024-04-19 8:38 ` [FFmpeg-devel] [PATCH v2] " Diego Felix de Souza via ffmpeg-devel
2024-04-19 11:29 ` Lynne
2024-04-19 11:55 ` Timo Rothenpieler
2024-04-24 22:43 ` Timo Rothenpieler
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=2540329d-79aa-4996-a566-b7b55299de0c@rothenpieler.org \
--to=timo@rothenpieler.org \
--cc=ddesouza@nvidia.com \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=r.arzumanyan@visionlabs.ai \
/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