All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Burton, Ross" <ross.burton@intel.com>
To: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gstreamer1.0-plugins-good: fix 4k playback for v4l2 decoder
Date: Sat, 2 Sep 2017 00:26:59 +0100	[thread overview]
Message-ID: <CAJTo0LZV5BNYANyc=R1_kbaLuRGa=cK-EPDa_7U65ffVErz+Uw@mail.gmail.com> (raw)
In-Reply-To: <20170901124506.19317-1-nicolas.dechesne@linaro.org>

[-- Attachment #1: Type: text/plain, Size: 989 bytes --]

On 1 September 2017 at 13:45, Nicolas Dechesne <nicolas.dechesne@linaro.org>
wrote:

> +++ b/meta/recipes-multimedia/gstreamer/gstreamer1.0-
> plugins-good/0001-v4l2-Fix-4K-colorimetry.patch
> @@ -0,0 +1,47 @@
> +From 545646cccba243236e10362fe7325f89be57da1f Mon Sep 17 00:00:00 2001
> +From: Nicolas Dufresne <nicolas.dufresne@collabora.com>
> +Date: Tue, 18 Jul 2017 11:28:37 -0400
> +Subject: [PATCH] v4l2: Fix 4K colorimetry
> +
> +Since 1.6, the transfer function for BT2020 has been changed from BT709
> +to BT2020_12. It's the same function, but with more precision. As a side
> +effect, the V4L2 colorpsace didn't match GStreamer colorspace. When
> +GStreamer ended up making a guess, it would not match anything supported
> +by V4L2 anymore. This this by using BT2020_12 for BT2020 colorspace and
> +BT2020 transfer function in replacement of BT709 whenever a 4K
> +resolution is detected.
> +
> +Upstream-Status: Backport
>

This needs your s-o-b.

Ross

[-- Attachment #2: Type: text/html, Size: 1440 bytes --]

      parent reply	other threads:[~2017-09-01 23:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-01 12:45 [PATCH] gstreamer1.0-plugins-good: fix 4k playback for v4l2 decoder Nicolas Dechesne
2017-09-01 13:04 ` ✗ patchtest: failure for " Patchwork
2017-09-01 23:26 ` Burton, Ross [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='CAJTo0LZV5BNYANyc=R1_kbaLuRGa=cK-EPDa_7U65ffVErz+Uw@mail.gmail.com' \
    --to=ross.burton@intel.com \
    --cc=nicolas.dechesne@linaro.org \
    --cc=openembedded-core@lists.openembedded.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
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.