rtspsrc creating multiple video source pads from single stream

[Tim]

Tim,

It appears we have some kind of cross-pipeline contamination.  We spawn many
pipelines in parallel from a loop.  I noticed that usually on the second
pipeline, shortly after starting, a bogus pad is added for the video SSRC of
the previous pipeline.  It is very strange.  Below is a snippet from our log
showing CAPS being added for the second pipeline for the correct SSRC
(57718723) and then downstream, rtpsession creating a pad for the bogus SSRC
(72fd6338).  How could this happen?

0:01:31.057239196   980 0x7f8a28003190 DEBUG                 rtpbin
gstrtpbin.c:3568:caps_changed:<manager> got caps application/x-rtp,
media=(string)video, payload=(int)96, clock-rate=(int)90000,
encoding-name=(string)H264, packetization-mode=(string)1,
profile-level-id=(string)42e028,
sprop-parameter-sets=(string)"J0LgKI1oB4AiflQ\=\,KM4ESSAAAAAAAAAA",
a-recvonly=(string)"", ssrc=(uint)57718723, clock-base=(uint)3759370630,
seqnum-base=(uint)0, npt-start=(guint64)0, play-speed=(double)1,
play-scale=(double)1
0:01:31.057251017   980 0x7f8a28003190 DEBUG                 rtpbin
gstrtpbin.c:3579:caps_changed:<manager> insert caps for payload 96
0:01:31.057265705   980 0x7f8a28003190 DEBUG             rtpsession
gstrtpsession.c:1655:gst_rtp_session_event_recv_rtp_sink:<rtpsession2>
received event segment
0:01:31.057280603   980 0x7f8a28003190 DEBUG             rtpsession
gstrtpsession.c:1683:gst_rtp_session_event_recv_rtp_sink:<rtpsession2>
received segment time segment start=0:00:00.000000000,
offset=0:00:00.000000000, stop=99:99:99.999999999, rate=1.000000,
applied_rate=1.000000, flags=0x00, time=0:00:00.000000000,
base=0:00:00.000000000, position 0:00:00.000000000, duration
99:99:99.999999999
0:01:31.057308766   980 0x7f8a28003190 DEBUG             rtpsession
rtpsession.c:1708:obtain_source: creating new source 72fd6338 0x7f8a4801af30

Thanks again!
-Tim



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