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 D565B453B0 for ; Fri, 27 Jan 2023 16:46:05 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 481A368BE27; Fri, 27 Jan 2023 18:46:01 +0200 (EET) Received: from mail0.khirnov.net (red.khirnov.net [176.97.15.12]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 2655C68B640 for ; Fri, 27 Jan 2023 18:45:55 +0200 (EET) Received: from localhost (localhost [IPv6:::1]) by mail0.khirnov.net (Postfix) with ESMTP id C03292404EC for ; Fri, 27 Jan 2023 17:45:54 +0100 (CET) Received: from mail0.khirnov.net ([IPv6:::1]) by localhost (mail0.khirnov.net [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id feFUYPtuhv6o for ; Fri, 27 Jan 2023 17:45:54 +0100 (CET) Received: from lain.khirnov.net (lain.khirnov.net [IPv6:2001:67c:1138:4306::3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "lain.khirnov.net", Issuer "smtp.khirnov.net SMTP CA" (verified OK)) by mail0.khirnov.net (Postfix) with ESMTPS id 38420240178 for ; Fri, 27 Jan 2023 17:45:54 +0100 (CET) Received: by lain.khirnov.net (Postfix, from userid 1000) id 265AE1601B2; Fri, 27 Jan 2023 17:45:54 +0100 (CET) From: Anton Khirnov To: FFmpeg development discussions and patches In-Reply-To: References: <20230127131639.4928-1-anton@khirnov.net> <20230127131639.4928-3-anton@khirnov.net> Mail-Followup-To: FFmpeg development discussions and patches Date: Fri, 27 Jan 2023 17:45:54 +0100 Message-ID: <167483795412.4503.13289836478999948630@lain.khirnov.net> User-Agent: alot/0.8.1 MIME-Version: 1.0 Subject: Re: [FFmpeg-devel] [PATCH 3/4] lavfi/framesync: add syncing via external timestamp map 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-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: Quoting Nicolas George (2023-01-27 15:53:42) > framesync generates output based on its input. Therefore to force > timestamps on output frames you need to force timestamps on input > frames. This is not forcing timestamps on output frames. This is solving the general problem where the correct matching of input frames is determined by some external logic. The specific case that is of interest to me is where this logic is the ffmpeg CLI framerate conversion, which allows framesync to accurately match videos processed through it. But I can imagine other cases where this would be useful. > And serializing timestamps in decimal in a giant string with newlines in > it: definitely no. Why not? 'No' with no reasoning and no suggested alternative is not much of an argument. -- Anton Khirnov _______________________________________________ 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".