From: Ezequiel Garcia <ezequiel@collabora.com>
To: Maxime Ripard <maxime.ripard@bootlin.com>,
Hans Verkuil <hverkuil@xs4all.nl>
Cc: hans.verkuil@cisco.com, acourbot@chromium.org,
sakari.ailus@linux.intel.com,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
tfiga@chromium.org, posciak@chromium.org,
Paul Kocialkowski <paul.kocialkowski@bootlin.com>,
Chen-Yu Tsai <wens@csie.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org, nicolas.dufresne@collabora.com,
jenskuske@gmail.com, jernej.skrabec@gmail.com, jonas@kwiboo.se,
linux-sunxi@googlegroups.com,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Guenter Roeck <groeck@chromium.org>
Subject: Re: [PATCH v3 1/2] media: uapi: Add H264 low-level decoder API compound controls.
Date: Tue, 12 Feb 2019 18:17:52 -0300 [thread overview]
Message-ID: <fb7e6bf4474583535961712bac5248b43dd47af0.camel@collabora.com> (raw)
In-Reply-To: <20190212130548.tytlxmbu4q6qgzzq@flea>
On Tue, 2019-02-12 at 14:05 +0100, Maxime Ripard wrote:
> Hi,
>
> On Mon, Feb 11, 2019 at 04:21:47PM +0100, Hans Verkuil wrote:
> > > I think the API should be designed with 4k video in mind. So if some of
> > > these constants would be too small when dealing with 4k (even if the
> > > current HW doesn't support this yet), then these constants would have to
> > > be increased.
> > >
> > > And yes, I know 8k video is starting to appear, but I think it is OK
> > > that additional control(s) would be needed to support 8k.
> >
> > Hmm, 4k (and up) is much more likely to use HEVC. So perhaps designing this
> > for 4k is overkill.
> >
> > Does anyone know if H.264 is used for 4k video at all? If not (or if very
> > rare), then just ignore this.
>
> I don't know the state of it right now, but until quite recently
> youtube at least was encoding their 4k videos in both VP9 and
> H264. They might have moved to h265 since, but considering 4k doesn't
> seem unreasonable.
>
Just asked the multimedia team here, and they say that 4k videos are in
fact widely used for both H264 and VP9 because of the HEVC licensing issues,
and because gains in compressions are not so impressive.
Regards,
Ezequiel
next prev parent reply other threads:[~2019-02-12 21:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 14:39 [PATCH v3 0/2] media: cedrus: Add H264 decoding support Maxime Ripard
2019-02-11 14:39 ` [PATCH v3 1/2] media: uapi: Add H264 low-level decoder API compound controls Maxime Ripard
2019-02-11 15:16 ` Hans Verkuil
2019-02-11 15:21 ` Hans Verkuil
2019-02-12 13:05 ` Maxime Ripard
2019-02-12 21:17 ` Ezequiel Garcia [this message]
2019-02-11 17:16 ` Nicolas Dufresne
2019-02-11 17:12 ` Ezequiel Garcia
2019-02-12 10:23 ` Maxime Ripard
2019-02-11 19:53 ` Ezequiel Garcia
2019-02-11 14:39 ` [PATCH v3 2/2] media: cedrus: Add H264 decoding support Maxime Ripard
2019-02-11 19:21 ` [linux-sunxi] " Jernej Škrabec
2019-02-12 10:43 ` Maxime Ripard
2019-02-12 17:46 ` Jernej Škrabec
2019-02-11 19:48 ` Ezequiel Garcia
2019-02-12 12:47 ` Maxime Ripard
2019-02-12 17:40 ` Jernej Škrabec
2019-02-14 20:42 ` Jernej Škrabec
2019-02-14 21:27 ` Jernej Škrabec
2019-02-12 12:50 ` [PATCH v3 0/2] " Tomasz Figa
2019-02-12 21:22 ` Ezequiel Garcia
2019-02-13 3:02 ` Tomasz Figa
2019-02-13 16:28 ` Ezequiel Garcia
2019-02-14 15:47 ` Maxime Ripard
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=fb7e6bf4474583535961712bac5248b43dd47af0.camel@collabora.com \
--to=ezequiel@collabora.com \
--cc=acourbot@chromium.org \
--cc=groeck@chromium.org \
--cc=hans.verkuil@cisco.com \
--cc=hverkuil@xs4all.nl \
--cc=jenskuske@gmail.com \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=maxime.ripard@bootlin.com \
--cc=nicolas.dufresne@collabora.com \
--cc=paul.kocialkowski@bootlin.com \
--cc=posciak@chromium.org \
--cc=sakari.ailus@linux.intel.com \
--cc=tfiga@chromium.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=wens@csie.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).