From: "Jan Ekström" <jeebjp@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2] avcodec/libkvazaar: Respect codec context color settings.
Date: Sat, 30 Sep 2023 17:20:47 +0300
Message-ID: <CAEu79Sa58+BypaB4Q4_UxWnH7bYCvtvKsdTssSUYJLcR39HTgA@mail.gmail.com> (raw)
In-Reply-To: <20230929211150.68675-1-johnmather@sidefx.com>
On Sat, Sep 30, 2023 at 12:12 AM John Mather via ffmpeg-devel
<ffmpeg-devel@ffmpeg.org> wrote:
>
> This patch makes the libkvazaar encoder respect color settings that are
> present on the codec context, including color range, primaries, transfer
> function and colorspace.
> ---
> libavcodec/libkvazaar.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/libavcodec/libkvazaar.c b/libavcodec/libkvazaar.c
> index 2ef34dd82e..984f78ba65 100644
> --- a/libavcodec/libkvazaar.c
> +++ b/libavcodec/libkvazaar.c
> @@ -101,6 +101,15 @@ FF_ENABLE_DEPRECATION_WARNINGS
> cfg->rc_algorithm = KVZ_LAMBDA;
> }
>
> + if (avctx->color_range != AVCOL_RANGE_UNSPECIFIED)
> + cfg->vui.fullrange = avctx->color_range == AVCOL_RANGE_JPEG;
> + if (avctx->color_primaries != AVCOL_PRI_UNSPECIFIED)
> + cfg->vui.colorprim = avctx->color_primaries;
> + if (avctx->color_trc != AVCOL_TRC_UNSPECIFIED)
> + cfg->vui.transfer = avctx->color_trc;
> + if (avctx->colorspace != AVCOL_SPC_UNSPECIFIED)
> + cfg->vui.colormatrix = avctx->colorspace;
> +
Just one thing that I was going to type on IRC but then didn't have the moment:
If kvazaar does support chroma location, please could you add that as
well? :) You can see in libx264 wrapper how that is done when just a
single field needs to be filled, while libx265 wrapper's
9b2281a4a383677ded522e603514789cc22498fa shows how to handle the case
where both the bool and both the internal values have to be written
out.
Of course is kvazaar doesn't yet support writing this out, then
discard this part.
Finally, do these VUI entries require a new minimum kvazaar version
compared to the current configure check? As in, if you try to build
the wrapper with your commit together with... 0.8.1 - does it build
successfully?
Jan
_______________________________________________
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:[~2023-09-30 14:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 21:11 John Mather via ffmpeg-devel
2023-09-29 21:38 ` Vittorio Giovara
2023-09-30 14:16 ` Jan Ekström
2023-09-30 14:20 ` Jan Ekström [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=CAEu79Sa58+BypaB4Q4_UxWnH7bYCvtvKsdTssSUYJLcR39HTgA@mail.gmail.com \
--to=jeebjp@gmail.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