From: Marth64 <marth64@proxyid.net>
To: Soft Works <softworkz@hotmail.com>
Cc: Kieran Kunhya <kieran618@googlemail.com>,
FFmpeg development discussions and patches
<ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2 00/11] fix broken CC detection and ffprobe fields (cover letter)
Date: Wed, 29 Jan 2025 23:07:19 -0600
Message-ID: <CAAhd_PXC6R1jRkoY99pb4ZQTqYNX5Y6w7AqzkUOkEMaTth3bcg@mail.gmail.com> (raw)
In-Reply-To: <DM8P223MB036570BE03B9B46727A4AD81BAE92@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>
> 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".
next prev parent reply other threads:[~2025-01-30 5:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241128011514.836463-1-marth64@proxyid.net>
[not found] ` <2f43d1e7-303c-4ff8-bd95-37a60f7d537b@passwd.hu>
[not found] ` <61f11f5d-22d0-4223-9b21-56e5282d1b9d@gmail.com>
[not found] ` <bd3bfe4c-b916-d563-625f-e7f2f623fd5e@passwd.hu>
[not found] ` <CA+28BfDkBa8RwGco0uVfmQC=s=umD7uycOq-1bsr0eJpce2byA@mail.gmail.com>
[not found] ` <daef6726-1881-890e-0e28-4e0f3ffe1f9a@passwd.hu>
[not found] ` <CA+28BfC3Ct=aV-fNPktM+39v5Fp9bpQOc-r-FobWuzUSe89CgQ@mail.gmail.com>
[not found] ` <CA+28BfD+2Z75h-EOjriaACrdxAf790L6e0FubBP1qzfUuipVxA@mail.gmail.com>
[not found] ` <CA+28BfAJ7Juo1csX1Nojb2=S=tfKoQByFqHwyJM5oyRytvQHxA@mail.gmail.com>
2025-01-27 9:04 ` Soft Works
2025-01-27 9:40 ` Kieran Kunhya via ffmpeg-devel
2025-01-27 10:00 ` Soft Works
2025-01-27 10:07 ` Soft Works
2025-01-27 19:02 ` Soft Works
2025-01-27 19:25 ` Kieran Kunhya via ffmpeg-devel
2025-01-27 19:36 ` Soft Works
2025-01-27 20:15 ` Devin Heitmueller
2025-01-27 20:39 ` Soft Works
2025-01-30 4:43 ` Marth64
2025-01-30 4:58 ` Soft Works
2025-01-30 5:07 ` Marth64 [this message]
2025-01-30 5:20 ` Soft Works
2025-01-30 5:24 ` Marth64
2025-01-30 5:36 ` Soft Works
2025-01-30 5:41 ` Marth64
2025-01-30 5:46 ` Marth64
2025-01-30 5:54 ` Soft Works
2025-01-30 6:07 ` Marth64
2025-01-30 6:40 ` Soft Works
2025-01-30 6:55 ` Marth64
2025-01-30 7:41 ` Soft Works
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAhd_PXC6R1jRkoY99pb4ZQTqYNX5Y6w7AqzkUOkEMaTth3bcg@mail.gmail.com \
--to=marth64@proxyid.net \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=kieran618@googlemail.com \
--cc=softworkz@hotmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git