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 749335 - glimagesink and videooverlay on windows
glimagesink and videooverlay on windows
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
git master
Other Windows
: Normal normal
: 1.5.1
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-05-13 21:14 UTC by Nicola
Modified: 2015-05-27 08:00 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
logs (257.84 KB, application/x-bzip)
2015-05-13 21:14 UTC, Nicola
Details

Description Nicola 2015-05-13 21:14:29 UTC
Created attachment 303333 [details]
logs

In my app I have this code:

gst_video_overlay_set_window_handle(GST_VIDEO_OVERLAY(video_sink),(guintptr)windowId);

this correctly embed xvimagesink and glimagesink in the provided window handle on linux,

on windows d3dvideosink is embedded as expected but glimagesink open and external window
Comment 1 Nicola 2015-05-27 07:13:34 UTC
works now after this commit

http://cgit.freedesktop.org/gstreamer/gst-plugins-bad/commit/?id=e24bc348bd5e78688c9c0da4f81c58e76a5920e6

it seems to crash if I use say 16 glimagesink windows inside the same app but this is another issue and eventually I'll report separately
Comment 2 Matthew Waters (ystreet00) 2015-05-27 08:00:02 UTC
Cool, thanks for testing!

commit e24bc348bd5e78688c9c0da4f81c58e76a5920e6
Author: Xavier Claessens <xavier.claessens@collabora.com>
Date:   Wed May 20 15:29:50 2015 -0400

    gl: win32: use a GMainContext to dispatch win32 messages
    
    gst_gl_window_win32_send_message_async() could be called before the
    internal window is created so we cannot use PostMessage there.
    
    x11 and wayland backends both create a custom GSource for this,
    so there is no reason to not do that for win32.
    
    https://bugzilla.gnome.org/show_bug.cgi?id=749601