Explaining Gstreamer plugin example

horai ivo.hora at seznam.cz
Sun Nov 24 21:05:06 UTC 2019


Dear sir,

Well, does it mean that the problem lies in Weston (wayland compositor) ?
I assumed due to the fact waylandsink is in gst-plugins-bad, it is not fully
ready yet and I also assumed that gstVideoOverlay is just a glue layer to
give commands to waylandsink to behave the way we it is ordered via
gstVideoOverlay methods, lets say, we want to clear (destroy) the area
waylandsink is rendering video into, we call 
gst_video_overlay_set_render_rectangle and it passes the arguments in a
exact way to waylandsink and it is up to waylandsink how it will negotiate
this request with wayland display server. Therefore, if it communicates in a
wrong way, then waylandsink does not fullfill the request and this method
will fail as I experienced in this case:
http://gstreamer-devel.966125.n4.nabble.com/gst-video-overlay-set-render-rectangle-td4691801.html. 
Could my assumption be correct?
If I understand it correctly, that race-condition is just another case where
waylandsink fails to do something correctly when talking to wayland server
as in my case multiple pipelines need to be disconnected from the server.
And this fails randomly, not always since according to Gstreamer
documentation there is no extra need to take care of threads when having
multiple pipeline in single application.
Could it be possible that the problem really lies in waylandsink improper
communication and not in compositor (Weston) code? If my assumption is
correct, I guess following this documentation we could try to fix it to suit
our needs:
https://wayland.freedesktop.org/docs/html/apb.html




--
Sent from: http://gstreamer-devel.966125.n4.nabble.com/


More information about the gstreamer-devel mailing list