On Thu, May 23, 2019 at 8:10 PM Jonathan Viney
wrote:
> On Thu, May 23, 2019 at 7:14 PM Moritz Barsnick wrote:
>
>> On Thu, May 23, 2019 at 16:51:16 +1200, Jonathan Viney wrote:
>> > > The NTP time from the first RTCP packet is currently extracted in
>> > > libavformat/rtsp.c and stored in
On Thu, May 23, 2019 at 7:14 PM Moritz Barsnick wrote:
> On Thu, May 23, 2019 at 16:51:16 +1200, Jonathan Viney wrote:
> > > The NTP time from the first RTCP packet is currently extracted in
> > > libavformat/rtsp.c and stored in AVFormatContext.start_time_realtime.
> > > However, there is no
On Thu, May 23, 2019 at 16:51:16 +1200, Jonathan Viney wrote:
> > The NTP time from the first RTCP packet is currently extracted in
> > libavformat/rtsp.c and stored in AVFormatContext.start_time_realtime.
> > However, there is no way to access this value when using ffmpeg from the
> >
Apologies, here is the patch in text/plain.
On Thu, May 23, 2019 at 4:44 PM Jonathan Viney
wrote:
> Hi,
>
> The NTP time from the first RTCP packet is currently extracted in
> libavformat/rtsp.c and stored in AVFormatContext.start_time_realtime.
> However, there is no way to access this value
Hi,
The NTP time from the first RTCP packet is currently extracted in
libavformat/rtsp.c and stored in AVFormatContext.start_time_realtime.
However, there is no way to access this value when using ffmpeg from the
commandline.
This patch adds an option when using an RTSP input to write the value
