Ravenna/AES67 protocol: before starting the journey...

[Roberto Grossi]

Thanks Sebastian, I am interest in your implementation.

As for point 3, this is a sample SDP info (the last three lines are
optional):

v=0
o=- 1 0 IN IP4 169.254.19.237
s=Session Test Name
t=0 0
a=clock-domain:PTPv2 0
m=audio 5004 RTP/AVP 98
c=IN IP4 232.249.178.198/1
a=rtpmap:98 L24/44100/8
a=sync-time:0
a=framecount:32-64
a=ptime:1.4512471
a=mediaclk:direct=0

a=maxptime:1.4512471
a=udp-src:8554
a=rtcp:5005

The ptime attribute indicates the preferred packet time (= framecount *
1000 / samplingFrequency)
Some documentation is here:

http://s10552c2bc54233da.jimcontent.com/download/version/1443433736/module/11950353523/name/RAVENNA___AES67_V1.0.pdf

In general, it would be nice also to let one specify:
RTP port number = even number (e.g. 5004)
RTCP port number = RTP port number + 1 (e.g. 5005)
TTL time-to-live (e.g. 1)
UDP port numbr (e.g. 8554)

Regards
Roberto

On Sat, Dec 5, 2015 at 11:46 PM, Sebastian Dröge <sebastian at centricular.com>
wrote:

> On Sa, 2015-12-05 at 21:19 +0100, Roberto Grossi wrote:
> >
> > 1. Does gst-rtsp-server already include the support for PTPv2?
>
> Since 1.6 we have PTP support, and you can use a PTP clock in gst-rtsp-
> server like any other clock.
>
> > 2. Can I slave the RTP timestamps of gst-rtsp-server to the DAC (the
> > grandmaster) using PTPv2 domain 0?
>
> Not yet, at least not in a way that is discoverable by the client. But
> I'm currently implementing the missing bits. Most notably RFC7273
> support.
>
> > 3. Can I customize the SDP info, as required by Ravenna/AES67?
>
> Which customisation do you mean?
>
> --
> Sebastian Dröge, Centricular Ltd · http://www.centricular.com
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20151206/5c291407/attachment.html>