Error: gst-stream-error-quark: Internal data stream error (1) for element UDPSrc

[vk_gst]

A little more debugging and I guess the issue is with the sink pads of
rtpbin. Here are the logs : 

bin gstbin.c:2280:update_degree:<pipeline0> change element rtpbin,
degree 0->1, linked to udpsink0
GST_PADS gstpad.c:3052:event_forward_func:<rtpstorage0:src> Reffing and
pushing event 0x7f83e8028150 (eos) to rtpstorage0:src
GST_EVENT gstpad.c:5679:gst_pad_send_event_unchecked:<upload:src> have
event type qos event: 0x7f83d00065f0, time 99:99:99.999999999, seq-num 563,
GstEventQOS, type=(GstQOSType)GST_QOS_TYPE_UNDERFLOW,
proportion=(double)1.0029845288514361, diff=(gint64)6151135,
timestamp=(guint64)4987566916;
GST_PADS gstpad.c:5217:store_sticky_event:<rtpstorage0:src> stored
sticky event eos
GST_PADS gstpad.c:3978:check_sticky:<rtpstorage0:src> pushing all
sticky events
bin gstbin.c:2303:update_degree:<pipeline0> element udpsrc1 not linked
on any sinkpads
GST_PADS gstpad.c:3908:push_sticky:<rtpstorage0:src> event stream-start
was already received
bin gstbin.c:885:find_message:<pipeline0> no message found matching
types 00001000
GST_PADS gstpad.c:3908:push_sticky:<rtpstorage0:src> event caps was
already received
basetransform
gstbasetransform.c:1941:gst_base_transform_src_eventfunc:<upload>
handling event 0x7f83d00065f0 qos event: 0x7f83d00065f0, time
99:99:99.999999999, seq-num 563, GstEventQOS,
type=(GstQOSType)GST_QOS_TYPE_UNDERFLOW,
proportion=(double)1.0029845288514361, diff=(gint64)6151135,
timestamp=(guint64)4987566916;
GST_PADS gstpad.c:3908:push_sticky:<rtpstorage0:src> event segment was
already received



The udpsrc pads are not linked in this case. To create rtp sink pads at
rtpbin, special request using 'rtpbin.recv_rtp_sink_0' has to be made. This
was already done once before, during the  initial start of Rx pipeline. 

So when the Tx pipeline is stopped(Ctrl+C) and restarted again, does that
mean that the request 'rtpbin.recv_rtp_sink_X' has to be requested again?
Won't the same pads be retained, since the Rx pipeline is never exited? 

Can anyone provide some pointers, this is kind of a blocker right now for
me. Else any other suggestions that might avoid this issue altogether.


Regards



--
Sent from: http://gstreamer-devel.966125.n4.nabble.com/