gst-core-error-quark: GStreamer error: state change failed and some element failed to post a proper error message with the reason for the failure

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

gst-core-error-quark: GStreamer error: state change failed and some element failed to post a proper error message with the reason for the failure

rinaldomerlo
Hi,

I am having stability issues in my applications that use gstreamer pipiline
via shared memory socket.

I have a continuously running gstreamer 'server' created like so that
streams to /tmp/multiviewersock:

gst-launch-1.0 decklinkvideosrc connection=HDMI mode=720p60 device-number=0
! queue leaky=downstream  
! shmsink wait-for-connection=0 socket-path=/tmp/multiviewersock

And then I have anywhere up to 8 or 10 client applications intermittently
reading from it, often overlapping. They are set up like so:

source_pipeline = shmsrc socket-path=/tmp/multiviewersock do-timestamp=1  !
video/x-raw,format=UYVY,framerate=60/1,
width=1280,height=720,pixel-aspect-ratio=1/1,interlace-mode=progressive,chroma-site=mpeg2,colorimetry=bt709
! queue ! videoconvert
#sink_pipeline = xvimagesink sync=false

This setup is wanted to be stable for days on end, but I am too often
getting this issue:

19:20:14 RuntimeError: gst-core-error-quark: GStreamer error: state change
failed and some element failed to post a proper error message with the
reason for the failure. (4): GStreamer error: state change failed and some
element failed to post a proper error message with the reason for the
failure.
19:20:14 gstbasesrc.c(3452): gst_base_src_start ():
/GstPipeline:pipeline1/GstShmSrc:shmsrc0:
19:20:14 Failed to start

When it happens it affects most, if not all, clients and can last over an
hour, then often magically rights itself (but sometimes not).

Surprisingly, when in this state, restarting the 'server' part does not seem
to help.

When I looked up this error in the gstreamer mailing list archives, I notice
the results that came up were also to do with sharing out a pipeline, so I
don't doubt it's something to do with my clients connecting and
disconnecting and overlapping etc. One result recommended the use of 'valve'
in the pipeline, but not sure exactly what that does. Any help would be
appreciated



--
Sent from: http://gstreamer-devel.966125.n4.nabble.com/
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel