<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>It is generally preferred to keep parsers and decoders separate.
Older elements do both, newer elements don't (usually). This
design allows for better modularity.<br>
</p>
<p>That's why there's also h264parse, h265parse, vc1parse, aacparse,
mpegaudioparse etc. for example.<br>
</p>
<div class="moz-cite-prefix">On 06.08.19 10:54, Guillermo Rodriguez
Garcia wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CABDcavbkcm2bGH8m=r7mfb4rUezDCC14LfcBW4S90OcVMjnWsw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">Hello all,<br>
<br>
I am trying to decode a live mjpeg stream from an IP camera
using souphttpsrc ! multipartdemux ! avdec_ffmpeg, but I get
not-negotated errors:
<div><br>
</div>
<div>
<div>0:00:01.216966334 326 0xaba920 WARN
basesrc
gstbasesrc.c:3055:gst_base_src_loop:<souphttpsrc0>
error: Internal data stream error.</div>
<div>0:00:01.217129000 326 0xaba920 WARN
basesrc
gstbasesrc.c:3055:gst_base_src_loop:<souphttpsrc0>
error: streaming stopped, reason not-negotiated (-4)</div>
<div>ERROR: from element
/GstPipeline:pipeline0/GstSoupHTTPSrc:souphttpsrc0:
Internal data stream error. </div>
<div><br>
</div>
<div>If I add jpegparse between multipartdemux and
avdec_ffmpeg, then all works fine.</div>
<div><br>
</div>
<div>But, once I add jpegparse, do I need multipartdemux
at all ? souphttpsrc ! jpegparse ! avdec_ffmpeg *also*
seems to work fine. Is there any reason to keep
multipartdemux then?</div>
<div><br>
</div>
<div>Moreover, if I replace avdec_ffmpeg with jpegdec,
then I don't seem to need neither multipartdemux nor
jpegparse; I can just have souphttpsrc ! jpegdec and
that seems to work as well...</div>
<div><br>
I am a bit confused about the interaction between all
these plugins. Also I checked the examples in the
documentation, but that didn't help -- the docs for
multipartdemux show an example pipeline that includes
jpegparse, while the docs for a jpegparse show a similar
example pipeline that does not include multipartdemux...</div>
<div><br>
</div>
<div>Is there a "canonical" or recommended way to decode a
mjpeg stream from a live HTTP source?</div>
<div><br>
</div>
<div>Thank you,</div>
<div><br>
</div>
<div dir="ltr" class="gmail_signature">Guillermo Rodriguez
Garcia<br>
<a href="mailto:guille.rodriguez@gmail.com"
target="_blank" moz-do-not-send="true">guille.rodriguez@gmail.com</a></div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
gstreamer-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:gstreamer-devel@lists.freedesktop.org">gstreamer-devel@lists.freedesktop.org</a>
<a class="moz-txt-link-freetext" href="https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel">https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel</a></pre>
</blockquote>
</body>
</html>