rtsp-server: Implement clock signalling according to RFC7273
For NTP and PTP clocks we signal the actual clock that is used and signal the direct media clock offset. For all other clocks we at least signal that it's the local sender clock. This allows receivers to know which clock was used to generate the media and its RTP timestamps. Receivers can then implement network synchronization, either absolute or at least relative by getting the sender clock rate directly via NTP/PTP instead of estimating it from RTP timestamps and packet receive times. https://bugzilla.gnome.org/show_bug.cgi?id=760005
Showing
- gst/rtsp-server/rtsp-client.c 18 additions, 0 deletionsgst/rtsp-server/rtsp-client.c
- gst/rtsp-server/rtsp-media-factory.c 51 additions, 0 deletionsgst/rtsp-server/rtsp-media-factory.c
- gst/rtsp-server/rtsp-media-factory.h 3 additions, 0 deletionsgst/rtsp-server/rtsp-media-factory.h
- gst/rtsp-server/rtsp-media.c 92 additions, 0 deletionsgst/rtsp-server/rtsp-media.c
- gst/rtsp-server/rtsp-media.h 21 additions, 0 deletionsgst/rtsp-server/rtsp-media.h
- gst/rtsp-server/rtsp-sdp.c 95 additions, 0 deletionsgst/rtsp-server/rtsp-sdp.c
- gst/rtsp-server/rtsp-stream.c 77 additions, 0 deletionsgst/rtsp-server/rtsp-stream.c
- gst/rtsp-server/rtsp-stream.h 6 additions, 0 deletionsgst/rtsp-server/rtsp-stream.h
Loading
Please register or sign in to comment