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 722248 - vaapisink: split renderer specific code to GstVaapiSinkBackendXXX
vaapisink: split renderer specific code to GstVaapiSinkBackendXXX
Status: RESOLVED FIXED
Product: gstreamer-vaapi
Classification: Other
Component: general
git master
Other Linux
: Normal enhancement
: ---
Assigned To: gstreamer-vaapi maintainer(s)
gstreamer-vaapi maintainer(s)
Depends on:
Blocks: 711478
 
 
Reported: 2014-01-15 09:45 UTC by Gwenole Beauchesne
Modified: 2014-07-30 16:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Gwenole Beauchesne 2014-01-15 09:45:45 UTC 
Split renderer specific code to GstVaapiSinkBackendXXX objects. At the minimum, the hooks would look like:
- create_window(): create a new window, owned by vaapisink
- create_window_from_handle(): bind a foreign window by handle
- render_surface(): render the supplied surface to screen
- set_handle_events(): start/stop events handler thread accordingly
Comment 1 Gwenole Beauchesne 2014-07-30 16:40:39 UTC 
commit 30c59af0a012ce2c75ce45bbe47b303f40f04ebe
Author: Gwenole Beauchesne <gwenole.beauchesne@intel.com>
Date:   Wed Jul 30 17:27:50 2014 +0200

    vaapisink: introduce separate backends.
    
    Introduce new backends vtable so that to have clean separation between
    display dependent code and common base code. That's a "soft" separation,
    we don't really need dedicated objects.
    
    https://bugzilla.gnome.org/show_bug.cgi?id=722248