After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 796172 - audiolatency cannot be used with rtpbin because this creates loop in pipeline
audiolatency cannot be used with rtpbin because this creates loop in pipeline
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
1.14.0
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2018-05-16 15:54 UTC by Daniel F
Modified: 2018-11-03 14:23 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Daniel F 2018-05-16 15:54:11 UTC
I have app which uses rtpbin to both send and receive RTP streams. I wanted to use new audiolatency element to measure delay of external VoIP server. However it turned out that I cannot use it together with rtpbin, because this creates loop in pipeline. Here are errors reported by my app:

1526484976.964529 1003: Pipeline error: Internal data stream error. (gstbasesrc.c(3055): gst_base_src_loop (): /GstPipeline:pipeline0/GstAudioLatency:audiolatency0/GstAudioTestSrc:audiotestsrc0:
streaming stopped, reason not-linked (-1))
1526484976.964638 1003: Pipeline error: Internal data stream error. (gstqueue.c(988): gst_queue_handle_sink_event (): /GstPipeline:pipeline0/GstQueue:queue2:
streaming stopped, reason not-linked (-1))

Please add new elements audiolatencysrc and audiolatencysink, which would communicate together "behind the scenes" and appear to GStreamer as a two separate elements. This will allow to use audiolatency together with rtpbin.
Comment 1 Daniel F 2018-05-16 16:24:57 UTC
I have checked my pipeline and found that elements were not linked. After adding extra audioconvert/audioresample elements it started working. However when app quits, it prints following warning 3 times. So some work here is still needed.

(gstreamertest:13301): GStreamer-WARNING **: loop detected in the graph of bin 'pipeline0'!!
Comment 2 Nicolas Dufresne (ndufresne) 2018-05-16 17:13:58 UTC
I had similar impression as you about the loop, loops of course work, but just can't always be freed/stopped.
Comment 3 GStreamer system administrator 2018-11-03 14:23:15 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/issues/709.