[Bug 691400] rtpbin rtpsession->RTCP thread is starting to early for ntp-sync

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=691400
  GStreamer | gst-plugins-good | unspecified

--- Comment #2 from Thomas Roos <thomas at roosesweb.de> 2013-02-07 14:40:57 UTC ---
me neither, but rtpbin is acting as a receiver as well and if there's an error
and no rtp data is received it should (RFC says it) start sending receiver
reports. As I said according to the rfc3550 this behavior is correct. But in
order to use the ntp-sync mechanism this behavior is bad to get low latency
inter device synchronous audio playback, because you don't want to buffer a few
seconds, you want to start playback as fast as possible.
The delay is an maximum value to wait for starting the RTCP thread if nothing
is received or sended.
May you have an better idea?

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.