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 744227 - Support RECORD | PLAY pipelines
Support RECORD | PLAY pipelines
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gst-rtsp-server
git master
Other Linux
: Normal enhancement
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on: 788950
Blocks:
 
 
Reported: 2015-02-10 09:10 UTC by Andreas Frisch
Modified: 2018-11-03 15:38 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
rtsp-stream+media: method to distinguish between in and out streams (4.72 KB, patch)
2015-02-10 09:10 UTC, Andreas Frisch
none Details | Review
proof-of-concept implementation of RECORD | PLAY mode for the same mount point (16.23 KB, patch)
2017-05-11 03:35 UTC, Sergey
none Details | Review

Description Andreas Frisch 2015-02-10 09:10:44 UTC
Created attachment 296447 [details] [review]
rtsp-stream+media: method to distinguish between in and out streams

So like i mentioned before in bug https://bugzilla.gnome.org/show_bug.cgi?id=743175  i want to be able to forward streams with the gst-rtsp-server.
Comment 1 Sergey 2017-05-11 03:35:11 UTC
Created attachment 351594 [details] [review]
proof-of-concept implementation of RECORD | PLAY mode for the same mount point

I'm pretty sure it's far from ideal, but at least it's working on my test pipeline. I will be glad to hear some comments to know if I'm going in the right direction and didn't do some obvious mistakes.
Thanks.
Comment 2 Tim-Philipp Müller 2017-06-13 11:09:33 UTC
Sergey, thanks for your patch. If I'm reading your code right you're creating separate rtpbins for play and record - is there a reason for that?
Comment 3 Sergey 2017-06-13 11:16:27 UTC
Yes, I've did separate rtpbins for play and record sides. Just thought since on record side and play side we will have different users, it will be better use different rtpbins. Do you think the same could be done with the single rtpbin?
Comment 4 Sergey 2017-06-13 11:25:31 UTC
FYI, a little bit improved version of above patch (and some other related) is available on GitHub: https://github.com/RSATom/gst-rtsp-server/commits/master - just don't sure it well enough to post it here...
Comment 5 Sebastian Dröge (slomo) 2017-06-13 11:53:27 UTC
I think it should be in the same rtpbin, possibly even in the same rtpsession. The RTCP is supposed to be shared AFAIU, or not?
Comment 6 Sergey 2017-06-13 11:58:09 UTC
Sorry, can't answer this question. I'm not familiar so well with rtp internals :(
Comment 7 Olivier Crête 2017-06-13 13:57:20 UTC
My understanding is that you want to use the same RTPbin only for streams that are meant to be synchronized together, otherwise we shouldn't.
Comment 8 Sebastian Dröge (slomo) 2017-06-15 07:25:28 UTC
While generally I agree, the problem I see here is that AFAIU there should be a single RTCP stream for this case. With multiple rtpbins you would have multiple.
Comment 9 Sergey 2017-06-15 10:59:20 UTC
Maybe it's dumb question, but why it should have single RTCP? Since pipeline inside rtsp server could do some additional job (for example I want show some splash screen when there are no input on record side), there just will be no receiver for rtcp. Other case, if pipeline do some heavy operation (transcoding for example) - there are no any meaning send rtcp to record source. Or maybe I don't understand well purposes of rtcp channel...
Comment 10 Sebastian Dröge (slomo) 2017-10-13 15:16:08 UTC
Nothing to do with "proxy" really, so renaming the bug :)
Comment 11 Sebastian Dröge (slomo) 2017-10-13 15:20:00 UTC
https://bugzilla.gnome.org/show_bug.cgi?id=788950 might be of interest here. Without, you create loops in the pipeline graph.
Comment 12 GStreamer system administrator 2018-11-03 15:38:12 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-rtsp-server/issues/5.