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 ESMTPS id 689734B4F4 for ; Thu, 30 Jan 2025 05:08:06 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 8528768BDA9; Thu, 30 Jan 2025 07:08:03 +0200 (EET) Received: from mail-lj1-f178.google.com (mail-lj1-f178.google.com [209.85.208.178]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 49B3B68BD76 for ; Thu, 30 Jan 2025 07:07:57 +0200 (EET) Received: by mail-lj1-f178.google.com with SMTP id 38308e7fff4ca-302250144adso400401fa.2 for ; Wed, 29 Jan 2025 21:07:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=proxyid.net; s=google; t=1738213676; x=1738818476; darn=ffmpeg.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=3lSwKSHnbuVv3pNsXA7bdPqUTZB/V5Euq9DukY+zWJE=; b=G71Ht6Rz9d1sr82XJL1BwIMsC8WrjcudRXd7e3D+TyYLOiPbOjtfoAJF5Qnltk/5rH m53DjHFbh8+JdmBk5i6Mk1DEqGOHJ3m4FIdxrgGF+D+Nx8ESeZVuCwRMHCAxeHAb2cI8 k8HghnVx+lpID3qtt7SE+UBG+AR3kFcqmTTdvO5w4Xt6V0U9iUgR2LTLv26V3USwxbii A9vt/GwDqg7TuNPwe/D6YyKvflO4SP0aSGYcPLfrjnyf2ElQ4UTcCifvQNTnn3s7uHqg WVVDd+pMgWoJvsR9+FlosthZHCZFhOJcv47HGlucit9piuy445f28v/tQAhII6jm4Fhn s0jA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1738213676; x=1738818476; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=3lSwKSHnbuVv3pNsXA7bdPqUTZB/V5Euq9DukY+zWJE=; b=aKyTYpDx07PQiUU5cGMHdTqhHg0oFgyVvwjmtJyZlLahSV2WUYHul5JOzG+TEvEqZe vf9XoHtmvRjeHravVtg4z6AK8UKq1NaDL9Wb7Wx3XIY8WJ416J/J2ZGcdrXxDdKB/rIc fQ6R17otGJCwl8FykK5N9kPQTSejsBYBC4SBYBmX1CIXoWl6sirw0ICCjDF7DyR31+q2 8/bB4b0ANBSAUkSoNiqB8T1Wczanv8zuLsEPZ3LhCk3ZaGZW+VTcj2sPDbTOBMw4C0OF SrUpf2B6ylYVmMy5DbI15d8ulzvoqPFbKOEeirKOvnCp8EkvlSy8xTN6vAw/ROY+fIrX ZnSQ== X-Gm-Message-State: AOJu0YzJ0egxtkO2lKbogVm47Ixx3SOgVtkbRKogr0A1iKDmgK7jlWBh LCXjBe2NTR5TdVCBmk2hTY7opuA4GDcBdbGiMgkoosj/UQ8k4fHZd03a6ZaMSPAOHjx7bzg43z6 syCaKlyTskGR8WkJtcIkShhaPkg+AL908hfGeUA== X-Gm-Gg: ASbGncu6LiTBQUEoAiPqUmfS+WbYao2gZRXErks5akd2drX/HtNFhXvfoLFTwVKQr3b K/iAmhF+ml1imY9BZlB9PMNQN/9kCiB1Pt0HOggKT9VpBrJ1RVxN7ZpEQMCW+ivgYP97KECbS X-Google-Smtp-Source: AGHT+IEedXdZnbhXx6FKzrLIBZGdAdCSYhdXJXoZj+L2U19vBdQeCjbdOSDQEwGwBI9Rz1I631QVHXX9K0EJt144+D8= X-Received: by 2002:a05:651c:19aa:b0:302:40ee:4c34 with SMTP id 38308e7fff4ca-307a1149ed1mr1943901fa.4.1738213676142; Wed, 29 Jan 2025 21:07:56 -0800 (PST) MIME-Version: 1.0 References: <20241128011514.836463-1-marth64@proxyid.net> <2f43d1e7-303c-4ff8-bd95-37a60f7d537b@passwd.hu> <61f11f5d-22d0-4223-9b21-56e5282d1b9d@gmail.com> In-Reply-To: From: Marth64 Date: Wed, 29 Jan 2025 23:07:19 -0600 X-Gm-Features: AWEUYZn4fZ12Yfq77fD1FmsSAq_5Z48Y3GL2To0KND68XepCFE3OzRZ6PB2cBJI Message-ID: To: Soft Works Subject: Re: [FFmpeg-devel] [PATCH v2 00/11] fix broken CC detection and ffprobe fields (cover letter) 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 Cc: Kieran Kunhya , 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: > Which kind of recurrence pattern are you talking about? I am talking about really sparse pattern. e.g. nothing for a long time, then ads inserted or program changes, and embedded bit stream starts. It's not that often but it happens with SCTE-20, or sloppy DVD edits for example. > Even if it was just 98% reliable, those 2% could not serve as justification for why probing of the 98% takes twice or thrice the time. I do agree. Having the "fast but catches most" solution as an option would be useful. I had tried to put up 3 proposals and -analyze_frames was the only one that seemed to stick since it did not break API or make things awkward with dispositions. For now, -analyze_frames helps to at least make the feature workable and has a utilitarian purpose for flexible CC probing needs. _______________________________________________ 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".