Quantcast

Use ONVIF 1.0 NTP timestamp for synchronization

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Use ONVIF 1.0 NTP timestamp for synchronization

Jan Koppe
Hello,

first off - I'm new here, so short introduction to what I'm trying to
achieve:

I work for a university doing lecture capture. Our system does automatic
lecture recording using ffmpeg, magewell capture cards for beamer-video
(via HDMI) and audio, and Axis P1428-E security network cameras to film
the teachers. Because the Video of the teacher and the audio signal are
basically recorded on two separate machines (the camera's running linux,
providing a rtp stream) we are having severe issues with synchronizing
those two, because the start-latency for the camera stream is changing
ever so slightly for each capture.

I've dug a bit into the rtp protocol (very basic understanding only for
now) and saw that our cameras support the ONVIF 1.0 standard, which says
that a wallclock NTP timestamp is sent within the RTP header. As far as
I can see this would be ideal: the university is running a dedicated NTP
server to which all devices synchronize, so if we could leverage this
timestamp to sync up audio and video our issues would be solved (there
will probably still be a small offset, but that should be much more
consistent and can be fixed easily).

At this point I am completely stuck: I tried capturing in separate
processes, a single process with multiple inputs, different -vsync
parameters but have not got it to work at all. It seems that ffmpeg is
not capable of detecting these timestamps.

Before I dig into ffmpegs code and try to understand what's going on -
is there anybody that can tell me if this idea is even worth chasing? Am
I missing something? Better suggestions?

Any help or ideas are much appreciated!

Regards,
Jan

--
Jan Koppe
eLectures / LearnWeb
Westfälische Wilhelms-Universität
Georgskommende 25 - Room 310
48143 Münster/Westf. - Germany
Tel. + 49 (0) 251 - 83 29295
E-mail: [hidden email]



_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".

smime.p7s (6K) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Use ONVIF 1.0 NTP timestamp for synchronization

Carl Eugen Hoyos-2
2017-02-12 10:03 GMT+01:00 Jan Koppe <[hidden email]>:

> I've dug a bit into the rtp protocol (very basic understanding only for
> now) and saw that our cameras support the ONVIF 1.0 standard,
> which says that a wallclock NTP timestamp is sent within the RTP
> header. As far as I can see this would be ideal: the university is
> running a dedicated NTP server to which all devices synchronize, so
> if we could leverage this timestamp to sync up audio and video our
> issues would be solved (there will probably still be a small offset, but
> that should be much more consistent and can be fixed easily).

I suspect ONVIF is not supported by FFmpeg (the wikipedia page
contains hints that this is a pure marketing thing though, all the
better if it really works).

> At this point I am completely stuck: I tried capturing in separate
> processes, a single process with multiple inputs, different -vsync
> parameters but have not got it to work at all.

(Command line and complete, uncut console output missing.)

> It seems that ffmpeg is
> not capable of detecting these timestamps.

Patch welcome!

Carl Eugen
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Loading...