Love the idea of gstreamer; HATE the execution

Zachary Hueras ZHueras at
Fri Dec 23 14:22:04 UTC 2022

There's a ton of available debug mechanisms, documentation, and active community members, any of which could have helped you get past this very first stage of debugging​ if you had done a little bit of research, or, heaven forbid,​ asked for help. Instead, you've put in no effort of your own and immediately started attacking the very community that could help you​.

Are you an engineer, or are you a self-entitled customer?

This is an open-source project. The people developing and supporting it are not being paid any money for their efforts; the least you could do is pony up a little kindness and respect. And no, your failure to grasp what they have produced does not relieve you of the burdens of basic human decency.

From: gstreamer-devel <gstreamer-devel-bounces at> on behalf of Chuck Crisler via gstreamer-devel <gstreamer-devel at>
Sent: Friday, December 23, 2022 8:53 AM
To: Discussion of the development of and with GStreamer <gstreamer-devel at>
Cc: Chuck Crisler <ccrislerathome at>; Dave Blanchard <dave at>
Subject: Re: Love the idea of gstreamer; HATE the execution

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.

On Fri, Dec 23, 2022 at 7:51 AM Nicolas Dufresne via gstreamer-devel <gstreamer-devel at<mailto:gstreamer-devel at>> wrote:
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.


> 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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the gstreamer-devel mailing list