From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 2/2] fftools/ffmpeg_filter: Fix audio_drift_threshold check
Date: Sat, 2 Jul 2022 14:56:50 +0200
Message-ID: <20220702125650.GC396728@pb2> (raw)
In-Reply-To: <165675110681.31466.8599184593020973018@lain.khirnov.net>
[-- Attachment #1.1: Type: text/plain, Size: 1057 bytes --]
On Sat, Jul 02, 2022 at 10:38:26AM +0200, Anton Khirnov wrote:
> Quoting Michael Niedermayer (2022-07-01 21:53:00)
> > On Thu, Jun 30, 2022 at 10:55:46AM +0200, Anton Khirnov wrote:
> > > Variant 2 is less bad, but the whole check seems hacky to me, since it
> > > seems to make assumptions about swr defaults
> > >
> > > Won't setting this unconditionally have the same effect?
> >
> > it has the same effect but its not so nice to the user to recommand extra
> > arguments which make no difference
>
> Sorry, I don't follow. What is recommending any arguments to the user
> here?
i meant this thing here:
./ffmpeg -i matrixbench_mpeg2.mpg -async 1 -f null - 2>&1 | grep async
-async is forwarded to lavfi similarly to -af aresample=async=1:min_hard_comp=0.100000:first_pts=0.
vs.
-async is forwarded to lavfi similarly to -af aresample=async=1:first_pts=0.
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Observe your enemies, for they first find out your faults. -- Antisthenes
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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:[~2022-07-02 12:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 12:13 [FFmpeg-devel] [PATCH 1/2] " Michael Niedermayer
2022-06-28 12:14 ` [FFmpeg-devel] [PATCH 2/2] " Michael Niedermayer
2022-06-30 8:55 ` Anton Khirnov
2022-07-01 19:53 ` Michael Niedermayer
2022-07-02 8:38 ` Anton Khirnov
2022-07-02 12:56 ` Michael Niedermayer [this message]
2022-07-05 16:58 ` Anton Khirnov
2022-07-05 22:36 ` Michael Niedermayer
2022-07-06 6:49 ` Anton Khirnov
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=20220702125650.GC396728@pb2 \
--to=michael@niedermayer.cc \
--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