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 770877 - vaapisink overlay: error during create overlay
vaapisink overlay: error during create overlay
Status: RESOLVED NOTABUG
Product: GStreamer
Classification: Platform
Component: gstreamer-vaapi
1.9.1
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-09-05 09:38 UTC by imeshns
Modified: 2016-10-04 11:32 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description imeshns 2016-09-05 09:38:13 UTC 
I'd like to report bug during create overlay vaapisink. There are description and solution of my report:

http://gstreamer-devel.966125.n4.nabble.com/vaapisink-overlay-td4678988.html

I have to make for example 200ms delay and then use gst_video_overlay_set_window_handle().
Comment 1 Hyunjun Ko 2016-09-06 07:57:29 UTC 
You can refer to the sample on https://gstreamer.freedesktop.org/data/doc/gstreamer/head/gst-plugins-base-libs/html/gst-plugins-base-libs-gstvideooverlay.html

In msg callback, you can set your xwindow handle. 
I confirmed that the sample is working on vaapisink based on your sample code.
Comment 2 Víctor Manuel Jáquez Leal 2016-10-04 11:32:10 UTC 
Hi, 

Thanks for reporting this issue. I have re-checked it.

As we talked in the gstreamer mailing list, the application should wait for two events: the widget realize and the "prepare window handle" in the pipeline's bus.

Hyunjun pointed to a snippet with a way to wait for these two events. There are others ways, like the one used in gst-player library in gst-plugins-bad. 

Using the pre-release of gstreamer 1.10 and 1.8, your code doesn't work as is anymore, there's an X related error:

The error was 'BadDrawable (invalid Pixmap or Window parameter)'.

If you wait for the bus message, the application works fine.

Thus, I'm closing this bug as NOTABUG.