From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110443] vaapi/vpp: wrong output for non 64-bytes align width (ex: 1200)
Date: Tue, 16 Apr 2019 04:41:34 +0000 [thread overview]
Message-ID: <bug-110443-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1250 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110443
Bug ID: 110443
Summary: vaapi/vpp: wrong output for non 64-bytes align width
(ex: 1200)
Product: Mesa
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: julien.isorce@gmail.com
QA Contact: dri-devel@lists.freedesktop.org
vaDeriveImage reports wrong stride.
Indeed Mesa's vlVaDeriveImage always sets the stride to w * 4 for RGBA format
https://cgit.freedesktop.org/mesa/mesa/tree/src/gallium/state_trackers/va/image.c#n259
This results in wrong video output, see
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/100
Is there a way to know the pipe_resource's stride
https://cgit.freedesktop.org/mesa/mesa/tree/src/gallium/state_trackers/va/image.c#n283
without exporting it to dmabuf (through whandle.stride) and without mapping it
(drv->pipe->transfer_map / pipe_transfer.stride) ?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2907 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-04-16 4:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 4:41 bugzilla-daemon [this message]
2019-04-16 20:02 ` [Bug 110443] vaapi/vpp: wrong output for non 64-bytes align width (ex: 1200) bugzilla-daemon
2019-04-16 20:16 ` bugzilla-daemon
2019-04-16 23:47 ` bugzilla-daemon
2019-04-18 16:51 ` bugzilla-daemon
2019-04-19 22:37 ` bugzilla-daemon
2019-04-23 22:48 ` bugzilla-daemon
2019-05-01 22:24 ` bugzilla-daemon
2019-05-01 22:27 ` bugzilla-daemon
2019-05-01 23:18 ` bugzilla-daemon
2019-05-02 20:15 ` bugzilla-daemon
2019-05-02 22:46 ` bugzilla-daemon
2019-05-03 19:49 ` bugzilla-daemon
2019-05-03 19:56 ` bugzilla-daemon
2019-05-08 19:51 ` bugzilla-daemon
2019-06-11 16: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-110443-502@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 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.