Sent from my mobile device On Sun, 7 Feb 2021, 19:21 Nicolas George, <geo...@nsup.org> wrote:
> Kieran Kunhya (12021-02-07): > > NTP is allowed to jump when it wants for example. It's not trivial for > the > > user to guarantee this. > > In practice, it does not. > Read the docs where it explains where it can jump. > > Exactly, so by default you must give the user a clock which is guaranteed > > not to jump as you don't know. If they need to synchronise between PCs > > using your naive process they can choose gettimeofday. > > So why are you still arguing this? > > > Hopefully they understand the consequences of that unlike you. It's > > still a flawed process because of timestamp jitter etc. > > I obviously understand the consequences better than you, since you did > not even realize why the wall time clock was needed. > Your scenario is contrived. Its impossible to sync exactly between different machines for all the reasons I explained and you didn't understand. I think this should be the end of the discussion. > Yes, since you are not interested in reading the NTP docs or understanding the purpose of a monotonic clock. Kieran > Regards, > > -- > Nicolas George > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > To unsubscribe, visit link above, or email > ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe". _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
