Error while sending fb frames using udpsink element

[Nicolas Dufresne]

Le lundi 24 avril 2017 à 04:26 -0700, Gokul Vellingiri a écrit :
> Additional debug info:
> gstmultiudpsink.c(598): gst_multiudpsink_render ():
> /GstPipeline:pipeline0/GstUDPSink:udpsink0:
> Reason: Error sending message: Message too long/
> 
> Is this is the proper way to send my data to another client ?. What
> is
> Significance of the errror "*Reason: Error sending message: Message
> too
> long*"

In UDP, the frames need to fit the socket buffer, a kernel
configuration (see buffer-size property). In general though, what
people do is to "packetize" each frames into multiple parts, generally
the size of one MTU to avoid packets being split by the network. The
packetization is usually done in a way to remember the framing even
though each frame is on multiple packets. A good options is to use RTP
payloaders. That will let you then use an rtpjitterbuffer on the
receiving end, to compensate network jitter and to reorder the
packets. Later on with RTP, you could start using rtpbin and enable
feedback and retransmissions for better quality.

  ... ! rtpvrawpay ! udpsink ...

And receiver would look like:

  udpsrc caps=... ! rtpjitterbuffer latency=20 ! rtpvrawdepay ! ...

If you want to stream on slower network though, you may have to start
thinking about compressing your stream using CODECs, for that there is
many option, including JPEG, VP8/9, H264/5 (non-free), etc.

regards,
Nicolas


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20170425/15b7edfb/attachment.sig>