[Bug 768586] glimagesink: on Raspberry Pi seems to get elected by playbin even if it does not support set_window_handle

[GStreamer (GNOME Bugzilla)]

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

--- Comment #11 from Nicolas Dufresne (stormer) <nicolas at ndufresne.ca> ---
(In reply to Tim-Philipp Müller from comment #10)
> Question is though what will it do to performance for everyone just doing
> some command line stuff or gst-play/playbin ? It will force worst-performing
> code paths then, no? I think applications should set xvimagesink/ximagesink
> etc. themselves depending on the windowing system they target.

X11 is what the Raspberry Pi Foundation targets at the moment. All projects I
know that uses glimagesink for performance pick glimagesink directly.
glimagesink on raspberry pi is just a poor choice for any serious application
because you can't even place the overlay in the screen, it's always centered.

The counter argument is that they are supposedly working on a mesa base driver
that will support GLX, but it's been ages. On Raspbian, they still hack the
decoder to color transform to RGB, so the rendering to ximagesink is quite fast
in fact.

> 
> Perhaps GstVideoOverlay::set_window_id/handle should gain a _full() function
> that adds a string identifying the handle / windowing system. Then
> autovideosink could somehow (element details *handwave*) try suitable sinks
> first. </random ideas>

No idea. To be honest, I have low interest in up-streaming this patch. I feel
like the "current" RPi stack is just wrong, and what happens here is a user
that suffer it.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.