Avimux refuses caps when sending JPEGs over UDP

[Sebastian Dröge]

On Mi, 2016-06-01 at 13:26 +0200, Mikkel Antonsen wrote:
> 
> which yields error messages such as this:
> 
> 0:00:00.117861054  6837      0x26e7540 DEBUG                 avimux
> gstavimux.c:415:gst_avi_mux_vidsink_set_caps:<avimux0>
> avimux0:video_0, caps=video/x-raw, format=(string)I420,
> width=(int)1920, height=(int)1080, interlace-
> mode=(string)progressive, pixel-aspect-ratio=(fraction)1/1, chroma-
> site=(string)mpeg2, framerate=(fraction)0/1
> 0:00:00.117925143  6837      0x26e7540 WARN                  avimux
> gstavimux.c:641:gst_avi_mux_vidsink_set_caps:<avimux0> refused caps
> video/x-raw, format=(string)I420, width=(int)1920, height=(int)1080,
> interlace-mode=(string)progressive, pixel-aspect-ratio=(fraction)1/1, 
> chroma-site=(string)mpeg2, framerate=(fraction)0/1
> ERROR: from element /GstPipeline:pipeline0/GstUDPSrc:udpsrc0:
> Internal data flow error.
> Additional debug info:
> gstbasesrc.c(2943): gst_base_src_loop ():
> /GstPipeline:pipeline0/GstUDPSrc:udpsrc0:
> streaming task paused, reason not-negotiated (-4)
> 
> I'm not sure what exactly is wrong with the caps. From what I
> understand gst-inspect avimux says that 0/1 is a valid framerate. 

avimux complains that it doesn't accept those caps in general, it's not
specific about the framerate. But when following the code in
gstavimux.c, your guess is correct. It doesn't support 0/1 as
framerate.

You will have to provide it with a valid framerate, e.g. by using a
videorate followed by a capsfilter with a specific framerate in front
of avimux.

-- 
Sebastian Dröge, Centricular Ltd · http://www.centricular.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 949 bytes
Desc: This is a digitally signed message part
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20160603/aa37bab6/attachment.sig>