After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 793886 - vaapisink: White is rendered pink with AMD card, wrong hue everywhere in RGBA and BGRA formats
vaapisink: White is rendered pink with AMD card, wrong hue everywhere in RGBA...
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gstreamer-vaapi
git master
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2018-02-27 16:10 UTC by Alicia Boya García
Modified: 2018-11-03 15:53 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
frame_01.png (test vector) (1.11 KB, image/png)
2018-02-27 16:11 UTC, Alicia Boya García 		Details
frame_01.png (wrong output) (1.99 KB, image/png)
2018-02-27 16:13 UTC, Alicia Boya García 		Details
Color_Wheel.png (test vector) (34.72 KB, image/png)
2018-02-27 16:14 UTC, Alicia Boya García 		Details
Color_Wheel.png (wrong output) (19.47 KB, image/png)
2018-02-27 16:15 UTC, Alicia Boya García 		Details
river.png (test vector) (187.74 KB, image/png)
2018-02-27 16:15 UTC, Alicia Boya García 		Details
river.png (wrong output) (144.12 KB, image/png)
2018-02-27 16:16 UTC, Alicia Boya García 		Details

Description Alicia Boya García 2018-02-27 16:10:49 UTC 
Testcase:

$ gst-launch-1.0 multifilesrc location="frame_01.png" caps="image/png,framerate=\(fraction\)3/1" ! pngdec ! videoconvert ! vaapisink

Works fine with xvimagesink:

$ gst-launch-1.0 multifilesrc location="frame_01.png" caps="image/png,framerate=\(fraction\)3/1" ! pngdec ! videoconvert ! xvimagesink
Comment 1 Alicia Boya García 2018-02-27 16:11:41 UTC 
Created attachment 369037 [details]
frame_01.png (test vector)
Comment 2 Alicia Boya García 2018-02-27 16:13:16 UTC 
Created attachment 369038 [details]
frame_01.png (wrong output)
Comment 3 Alicia Boya García 2018-02-27 16:14:52 UTC 
Created attachment 369039 [details]
Color_Wheel.png (test vector)
Comment 4 Alicia Boya García 2018-02-27 16:15:21 UTC 
Created attachment 369040 [details]
Color_Wheel.png (wrong output)
Comment 5 Alicia Boya García 2018-02-27 16:15:57 UTC 
Created attachment 369041 [details]
river.png (test vector)
Comment 6 Alicia Boya García 2018-02-27 16:16:25 UTC 
Created attachment 369042 [details]
river.png (wrong output)
Comment 7 Alicia Boya García 2018-02-27 16:29:39 UTC 
This problem does not reproduce when the image is encoded to h264.

$ gst-launch-1.0 multifilesrc location="frame_01.png" caps="image/png,framerate=\(fraction\)3/1" ! pngdec ! videoconvert ! x264enc ! vaapih264dec ! vaapisink
Comment 8 Alicia Boya García 2018-02-28 16:13:27 UTC 
Turns out the problem is RGBA and BGRA pixel formats being misread.

This can be reproduced even more easily with a capsfilter:

These two reproduce the problem:

gst-launch-1.0 -v videotestsrc ! video/x-raw, format=RGBA ! vaapisink
gst-launch-1.0 -v videotestsrc ! video/x-raw, format=BGRA ! vaapisink

For comparison, YUV based formats like these work without problems:

gst-launch-1.0 -v videotestsrc ! video/x-raw, format=I420 ! vaapisink
gst-launch-1.0 -v videotestsrc ! video/x-raw, format=NV12 ! vaapisink

(In the pipeline of the previous message, vaapih264dec decoded the h264 frames to NV12, therefore the problem did not reproduce.)
Comment 9 GStreamer system administrator 2018-11-03 15:53:21 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/85.