From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTP id 6A6FD42E4B for ; Sat, 9 Jul 2022 18:28:13 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 33B7068B918; Sat, 9 Jul 2022 21:28:11 +0300 (EEST) Received: from mout-p-101.mailbox.org (mout-p-101.mailbox.org [80.241.56.151]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 0D3CC68B6F9 for ; Sat, 9 Jul 2022 21:28:05 +0300 (EEST) Received: from smtp102.mailbox.org (smtp102.mailbox.org [10.196.197.102]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-p-101.mailbox.org (Postfix) with ESMTPS id 4LgJYG6DLsz9sT8 for ; Sat, 9 Jul 2022 20:28:02 +0200 (CEST) Message-ID: <4695e134-a83f-fdb3-3c04-ed3b724a82c9@gyani.pro> Date: Sat, 9 Jul 2022 23:57:49 +0530 MIME-Version: 1.0 Content-Language: en-US To: ffmpeg-devel@ffmpeg.org References: <20220704162912.5577-1-ffmpeg@gyani.pro> <165718689777.31466.279724099132649515@lain.khirnov.net> From: Gyan Doshi In-Reply-To: Subject: Re: [FFmpeg-devel] [PATCH v3] ffmpeg: add option -isync X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: On 2022-07-08 09:26 am, Gyan Doshi wrote: > > > On 2022-07-07 03:11 pm, Anton Khirnov wrote: >> Quoting Gyan Doshi (2022-07-04 18:29:12) >>> This is a per-file input option that adjusts an input's timestamps >>> with reference to another input, so that emitted packet timestamps >>> account for the difference between the start times of the two inputs. >>> >>> Typical use case is to sync two or more live inputs such as from >>> capture >>> devices. Both the target and reference input source timestamps >>> should be >>> based on the same clock source. >>> >>> If not all inputs have timestamps, the wallclock times at the time of >>> reception of inputs shall be used. FFmpeg must have been compiled with >>> thread support for this last case. >> I'm wondering if simply using the other input's InputFile.ts_offset >> wouldn't achieve the same effect with much less complexity. > > That's what I initially did. But since the code can also use two other > sources for start times (start_time_realtime, first_pkt_wallclock), > those intervals may not exactly match the difference between > fmctx->start_times so I use a generic calculation. Plan to push on Monday, if no further changes. 5.1 is to be cut soon. Regards, Gyan _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".