<div dir="ltr">GStreamer is meant for developers, not end users. Yes, some of the error messages and information could be better. However, it is assumed that you have some knowledge of these concepts and the interest to look into the code. Also, the support on this mailing list is quick and very good. The community is very helpful in regards to resolving issues and helping you learn how it works. </div> <div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Dec 23, 2022 at 7:51 AM Nicolas Dufresne via gstreamer-devel <<a href="mailto:gstreamer-devel@lists.freedesktop.org">gstreamer-devel@lists.freedesktop.org</a>> wrote: </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Thanks for the rant, Le vendredi 23 décembre 2022 à 01:06 -0600, Dave Blanchard via gstreamer-devel a écrit : > The concept of gstreamer is great, but the execution is TERRIBLE. 9/10 configurations that I try fail for obscure, incomprehensible reasons, with ZERO explanation of what went wrong. The error messages are COMPLETELY USELESS. > > Redistribute latency... > ERROR: from element /GstPipeline:pipeline0/GstSRTSrc:srtsrc0: Internal data stream error. > Additional debug info: > ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): /GstPipeline:pipeline0/GstSRTSrc:srtsrc0: > streaming stopped, reason not-negotiated (-4) not-negotiated is translated to "Not negotiated" in english. It means that srtsrc (the error emitter reported on previous line) is not compatible with the set of element/capsfilter you have placed downstream to it (to the right). Of course you haven't shared the pipeline, this was just a rant, and I assume you didn't care, but sharing the pipeline you are using will allow us to help you further. regards, Nicolas > Execution ended after 0:00:00.345528392 > Setting pipeline to NULL ... > 01:02:38 AM.416780/gst-launch-1.0*E:SRT.ei: epoll/update: IPE: update struck E1 which is NOT SUBSCRIBED to @710665059 > Freeing pipeline ... > > > "Internal data stream error." And what the hell does that mean, exactly....???? Why not change the error text to "Oops! Something went wrong, lol". Then you can be exactly like Twitter. > </blockquote></div>