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 752652 - glimagesink: overlay composition resize does not place text correctly
glimagesink: overlay composition resize does not place text correctly
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
git master
Other All
: Normal normal
: 1.5.90
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-07-21 04:13 UTC by Matthew Waters (ystreet00)
Modified: 2015-08-16 13:38 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Matthew Waters (ystreet00) 2015-07-21 04:13:02 UTC 
Reproducal:

Run gst-launch-1.0 videotestsrc ! textoverlay text=YAY ! glimagesink and resize the window.

The text does not stay in the same place relative to the video but is stuck at a fixed offset.
Comment 1 Matthew Waters (ystreet00) 2015-07-21 04:56:22 UTC 
Actually it lags behind the window resize.
Comment 2 Lubosz Sarnecki 2015-07-21 08:16:01 UTC 
I forgot to propose the hack for gst-plugins-base to make the negotation fnish every event cycle.

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

This fixes the lag. It's still slow but the resolution is correct in the same event cycle at least.
Comment 3 Nicolas Dufresne (ndufresne) 2015-07-21 13:28:45 UTC 
Works for me.
Comment 4 Nicolas Dufresne (ndufresne) 2015-07-21 13:32:03 UTC 
You might see 1 or two frames wrong, that's because we where asked to use the a serialize query to get the window size. which enforce the race (even though you could have wrong frames with the other method, the upstream event).

The nature of reconfiguration is asynchronous, while the resize is synchronous. There might be something we could do at the renderer side to improve that, please leave this bug open.
Comment 5 Nicolas Dufresne (ndufresne) 2015-07-24 22:07:51 UTC 
This is fixed now, sorry for the inconvenience.