dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105145] vaExportSurfaceHandle interaction with surface interlaced flag prevents switching on vaapi deinterlacing dynamically
Date: Wed, 13 Jun 2018 11:15:57 +0000	[thread overview]
Message-ID: <bug-105145-502-Vce9FK3CFR@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105145-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1060 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=105145

--- Comment #13 from k.philipp@gmail.com ---
(In reply to Christian König from comment #12)
> Unfortunately yes it is.
That is indeed very unfortunate. It complicates stuff a lot :-(
I'd still like to see a solution that allows to support PAFF without copying
around already-decoded frames/fields all the time. Do you have any ideas? Could
we have the decoder put progressive content into progressive surfaces and
interlaced content into interlaced surfaces (under the assumption that we will
most likely want to deinterlace)?

> That HEVC and VP9 only support progressive layout in the output format is
> also only logical because those formats don't support interlaced content.
At least HEVC does support interlaced content in theory, but as far as I
understood it the (hw) decoder does not need special support for that. How
would that work then, would we get top/bottom field as two separate
quasi-frames?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2084 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-06-13 11:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-17 12:47 [Bug 105145] vaExportSurfaceHandle interaction with surface interlaced flag prevents switching on vaapi deinterlacing dynamically bugzilla-daemon
2018-02-17 13:48 ` bugzilla-daemon
2018-02-18  8:31 ` bugzilla-daemon
2018-02-19  7:49 ` bugzilla-daemon
2018-02-20 11:55 ` bugzilla-daemon
2018-02-20 12:56 ` bugzilla-daemon
2018-02-20 12:56 ` bugzilla-daemon
2018-02-20 13:51 ` bugzilla-daemon
2018-02-20 14:23 ` bugzilla-daemon
2018-03-07  7:43 ` bugzilla-daemon
2018-04-14 10:14 ` bugzilla-daemon
2018-06-11 12:58 ` bugzilla-daemon
2018-06-11 13:09 ` bugzilla-daemon
2018-06-13 11:15 ` bugzilla-daemon [this message]
2019-02-03 12:41 ` bugzilla-daemon
2019-09-25 18:02 ` bugzilla-daemon

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=bug-105145-502-Vce9FK3CFR@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.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