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 585285 - [0.11] rtpbin merge jitterbuffer and source
[0.11] rtpbin merge jitterbuffer and source
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-good
git master
Other Linux
: Normal blocker
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-06-09 20:59 UTC by Wim Taymans
Modified: 2012-10-02 20:16 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
the tar bzip2 (34.90 KB, patch)
2009-06-09 21:00 UTC, Wim Taymans 		none Details | Review

Description Wim Taymans 2009-06-09 20:59:44 UTC 
my current rtpbin work in progress
Comment 1 Wim Taymans 2009-06-09 21:00:50 UTC 
Created attachment 136230 [details] [review]
the tar bzip2
Comment 2 Sebastian Dröge (slomo) 2009-08-08 21:01:48 UTC 
Wim, what's the state of this bug?
Comment 3 Sebastian Dröge (slomo) 2010-01-14 19:56:56 UTC 
ping
Comment 4 Olivier Crête 2010-01-14 20:11:54 UTC 
Since rtpbin is now in -good and the API is therefore frozen, this is pushed back to 0.11 or something.
Comment 5 Tobias Mueller 2010-04-07 10:46:25 UTC 
Reopening as I can't see any open non-developer question.
Comment 6 Olivier Crête 2011-05-30 06:52:47 UTC 
When doing FEC over RTP, we want to do the rtpsession/rtpsource processing (to send the correct RTCP) to the original and FEC streams separately, but we want the jitterbuffer to be applied to the corrected stream. The FEC stream could use a different SSRC inside the same RTP session or could be in a separate RTP session, I think we want to support both cases. So it may make merging rtpsource and rtpjitterbuffer a bit tricky.
Comment 7 Tim-Philipp Müller 2012-08-29 15:35:41 UTC 
Not a blocker. Not sure if anything's left to do here.

Wim: can this be closed?
Comment 8 Tim-Philipp Müller 2012-10-02 20:16:51 UTC 
Dunno what's up with this. No response from Wim since 2009 and reasons from Olivier why this might not be so easy, so closing as OBSOLETE. I'm sure someonen will re-open it in 2016 if it's still interesting.