From: Gyan Doshi <ffmpeg@gyani.pro>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] fftools/ffmpeg_enc: Prevent duplicate A53 Closed Captions at frame rate up-conversion
Date: Tue, 13 Jun 2023 20:11:42 +0530
Message-ID: <f2a50419-51fb-9d3a-ccb1-250f60d69d82@gyani.pro> (raw)
In-Reply-To: <CAHGibzHvDEM0kmMMGvaKUYq0up1h5sxdzTSvNLpafQsqMbT1zA@mail.gmail.com>
On 2023-06-13 07:46 pm, Devin Heitmueller wrote:
> On Sat, Jun 10, 2023 at 11:55 PM Anton Khirnov <anton@khirnov.net> wrote:
>> I don't think there's a fundamental reason -r handling could not be
>> moved to lavfi, but it's a nontrivial task. E.g. the dup/drop counts are
>> integrated with the CLI and would have to be exported from lavfi somehow
>> if you wanted to keep that functionality.
> I think the big question here in my mind is: does anyone actually
> care about the dup/drop counts? I recognize it's a change in behavior
> for the application to not show that in the status, but how useful is
> it really to know that the app duplicated 50% of your frames because
> you put "-r 60000/1001" on the command line?
The dup/drop code is active in the absence of output `-r` if the output
format is not VFR flagged.
Then the dup/drop count is useful to diagnose an abnormally large frame
rate detected in the input stream,
such as a WebM with a 1k tbr or a cover image with a 90k tbr.
More mundanely, one can check the 'CFR'-ness of a stream by looking at
those counts, especially if lavfi is not present.
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".
prev parent reply other threads:[~2023-06-13 14:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 13:19 Artem Smorodin
2023-06-09 15:13 ` Devin Heitmueller
2023-06-09 16:33 ` [FFmpeg-devel] [External Sender] " Artem Smorodin
2023-06-13 14:11 ` Devin Heitmueller
2023-06-11 3:55 ` [FFmpeg-devel] " Anton Khirnov
2023-06-13 14:16 ` Devin Heitmueller
2023-06-13 14:41 ` Gyan Doshi [this message]
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=f2a50419-51fb-9d3a-ccb1-250f60d69d82@gyani.pro \
--to=ffmpeg@gyani.pro \
--cc=ffmpeg-devel@ffmpeg.org \
/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