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 2ED2D4545F for ; Mon, 30 Jan 2023 11:01:41 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 884BD68BC9B; Mon, 30 Jan 2023 13:01:38 +0200 (EET) Received: from nef.ens.fr (nef2.ens.fr [129.199.96.40]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id C791668B95C for ; Mon, 30 Jan 2023 13:01:31 +0200 (EET) X-ENS-nef-client: 129.199.129.80 ( name = phare.normalesup.org ) Received: from phare.normalesup.org (phare.normalesup.org [129.199.129.80]) by nef.ens.fr (8.14.4/1.01.28121999) with ESMTP id 30UB1UtB016412 for ; Mon, 30 Jan 2023 12:01:31 +0100 Received: by phare.normalesup.org (Postfix, from userid 1001) id E12A8EB5BB; Mon, 30 Jan 2023 12:01:30 +0100 (CET) Date: Mon, 30 Jan 2023 12:01:30 +0100 From: Nicolas George To: FFmpeg development discussions and patches Message-ID: References: <20230127131639.4928-1-anton@khirnov.net> <20230127131639.4928-3-anton@khirnov.net> <167483795412.4503.13289836478999948630@lain.khirnov.net> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <167483795412.4503.13289836478999948630@lain.khirnov.net> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (nef.ens.fr [129.199.96.32]); Mon, 30 Jan 2023 12:01:31 +0100 (CET) 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: Anton Khirnov (12023-01-27): > 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. You are explaining nothing that was not already present in the commit message, and my interpretation is still: you are engaged in a wrong solution and are trying to make it work, i.e. XY problem . Just force the timestamps to the input of framesync filters and you will get what you want on the output. > > And serializing timestamps in decimal in a giant string with newlines in 1 2 3 4 > > it: definitely no. > Why not? > 'No' with no reasoning and no suggested alternative is not much of an > argument. There were four arguments. -- 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-request@ffmpeg.org with subject "unsubscribe".