Unable to play videos with Gstreamer about distribution HOT 12 CLOSED

from distribution.

I'm not sure what you mean by "using X". I think it's running Wayland with Xwayland. The following environment variables are set:

DISPLAY=:0
WAYLAND_DISPLAY=wayland-0

This is a fresh installation of Clearlinux (from Wednesday - version 20920) and I just added the GUI option from the installer (don't recall exactly what it was called).

I have tried to change the display option of vaapisink to use X11 (option 1) but that does not work - see below:

$ gst-launch-1.0 -v filesrc location=/home/gvancuts/Videos/Sintel.mp4 ! qtdemux ! h264parse ! vaapih264dec ! vaapisink display=1
failed to open /usr/lib64/dri/hybrid_drv_video.so
Failed to wrapper hybrid_drv_video.so
Setting pipeline to PAUSED ...
ERROR: Pipeline doesn't want to pause.
ERROR: from element /GstPipeline:pipeline0/GstVaapiSink:vaapisink0: GStreamer error: state change failed and some element failed to post a proper error message with the reason for the failure.
Additional debug info:
gstbasesink.c(5264): gst_base_sink_change_state (): /GstPipeline:pipeline0/GstVaapiSink:vaapisink0:
Failed to start
Setting pipeline to NULL ...
Freeing pipeline ...

The error I'm getting with a 'standard' gst-play-1.0 is identical to the one thrown when using display=3 (which corresponds to Wayland)

from distribution.

My question was more about "without using wayland"

from distribution.

I haven't tried that. Do you have a pointer on how I can switch to a native X11 environment?

Wayland is not the issue per se, it works fine if I use weston instead of mutter. I have tried that with weston running as a nested compositor or natively.

from distribution.

Just rebooted using 'GNOME on Xorg' from the logging screen (so pure X11 env) and the vaapisink element behaves correctly there (tried both the x11 and glx display option for vaapisink and both work).

from distribution.

ok that points us in a pretty narrow direction; thanks

from distribution.

This issue is known https://bugzilla.gnome.org/show_bug.cgi?id=775698

Being addressed in the driver here: intel/intel-vaapi-driver#357
(I pinged the driver team to get someone assigned to it)

For the upcoming gstreamer release, vaapisink has been downgraded as marginal unfortunately.

commit c653cb55f9a97d1bf6d3fc1d0ae30dcd958174a5
Author: Víctor Manuel Jáquez Leal [email protected]
Date: Mon Feb 12 17:53:58 2018 +0100

vaapi: register vaapisink as marginal on wayland

vaapsink, when used with the Intel VA-API driver, tries to display
surfaces with format NV12, which are handled correctly by
Weston. Nonetheless, COGL cannot display YUV surfaces, making fail
pipelines on mutter.

This shall be solved either by COGL or by making the driver to paint
RGB surfaces. In the meanwhile, let's just demote vaapisink as
marginal when the Wayland environment is detected, no matter if it is
Weston.

https://bugzilla.gnome.org/show_bug.cgi?id=775698

The right way to solve this is to get the support in for RGB surfaces - with multi-pixel plane support becoming the norm regarding color space in the display controller, the driver shouldn't have to be fixed to NV12 only.

from distribution.

And it is likely to get supported faster than getting YUV into COGL. Though that is doable too.

from distribution.

Thanks @seanvk !

from distribution.

@gvancuts Is this still an issue? can I close?

from distribution.

Hi @iphutch , I haven't tested this lately, I will try to get to it by EOW.

Do you have reasons to believe that this is fixed?

from distribution.

Mutter has been taken out of the equation (GNOME runs on X by default now)... so we're not hitting this issue anymore. I will close it.

from distribution.