"GStreamer" (GNOME Bugzilla)
2017-10-20 10:40:34 UTC
https://bugzilla.gnome.org/show_bug.cgi?id=789236
Bug ID: 789236
Summary: vaapisink shows blank and white output
Classification: Platform
Product: GStreamer
Version: unspecified
OS: Linux
Status: NEW
Severity: normal
Priority: Normal
Component: gstreamer-vaapi
Assignee: gstreamer-***@lists.freedesktop.org
Reporter: ***@amd.com
QA Contact: gstreamer-***@lists.freedesktop.org
CC: ***@gmail.com, ***@igalia.com
GNOME version: ---
Created attachment 361925
--> https://bugzilla.gnome.org/attachment.cgi?id=361925&action=edit
Screen shot of Black and White Output
Hi,
I m using the pipeline
gst-launch -v videotestsrc ! vaapisink and the see a black and while output on
one H/W system (Config 1 1). The same Hard disk on a different H/W system
(different processor than Config1), shows colored o/p.
I used GST_DEBUG=vaapisink:5 gst-launch-1.0 videotestsrc ! vaapisnk to
compare the debug logs on both system and debug traces are the same.
Is there any further debug approaches that you could suggest ?
Thank you
Mats
Bug ID: 789236
Summary: vaapisink shows blank and white output
Classification: Platform
Product: GStreamer
Version: unspecified
OS: Linux
Status: NEW
Severity: normal
Priority: Normal
Component: gstreamer-vaapi
Assignee: gstreamer-***@lists.freedesktop.org
Reporter: ***@amd.com
QA Contact: gstreamer-***@lists.freedesktop.org
CC: ***@gmail.com, ***@igalia.com
GNOME version: ---
Created attachment 361925
--> https://bugzilla.gnome.org/attachment.cgi?id=361925&action=edit
Screen shot of Black and White Output
Hi,
I m using the pipeline
gst-launch -v videotestsrc ! vaapisink and the see a black and while output on
one H/W system (Config 1 1). The same Hard disk on a different H/W system
(different processor than Config1), shows colored o/p.
I used GST_DEBUG=vaapisink:5 gst-launch-1.0 videotestsrc ! vaapisnk to
compare the debug logs on both system and debug traces are the same.
Is there any further debug approaches that you could suggest ?
Thank you
Mats
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.