From: Paul B Mahol <onemda@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avfilter/vf_cropdetect: add ability to change limit/reset at runtime
Date: Tue, 17 Jan 2023 19:11:46 +0100
Message-ID: <CAPYw7P6TmmF2-xWHQBpnHdCJWEYmfdvP0K4LTQs3KaXOvQSN5g@mail.gmail.com> (raw)
In-Reply-To: <a53a3ced-5fc0-23a9-d3a4-a89571830972@gmail.com>
On 1/17/23, Jeffrey Chapuis <ashyni1987@gmail.com> wrote:
> I'm getting there, don't give up on me.
>
> Now 'limit_upscaled' become the variable used in filter_frame() and
> 'limit' is never change, unless by user
> We only have to update 'limit_upscaled' if 'limit' really changes.
probably ok
_______________________________________________
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:[~2023-01-17 18:11 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 13:15 Jeffrey CHAPUIS
2023-01-10 15:45 ` Paul B Mahol
2023-01-11 11:42 ` Jeffrey Chapuis
2023-01-11 17:46 ` Jeffrey Chapuis
2023-01-12 15:53 ` Jeffrey Chapuis
2023-01-17 11:46 ` Jeffrey Chapuis
2023-01-17 11:52 ` Paul B Mahol
2023-01-17 12:27 ` Jeffrey Chapuis
2023-01-17 12:34 ` Paul B Mahol
2023-01-17 13:31 ` Jeffrey Chapuis
2023-01-17 13:45 ` Paul B Mahol
2023-01-17 14:24 ` Jeffrey Chapuis
2023-01-17 14:29 ` Paul B Mahol
2023-01-17 15:19 ` Jeffrey Chapuis
2023-01-17 16:23 ` Paul B Mahol
2023-01-17 18:00 ` Jeffrey Chapuis
2023-01-17 18:11 ` Paul B Mahol [this message]
2023-01-17 22:07 ` Jeffrey Chapuis
2023-01-19 12:11 ` Jeffrey Chapuis
2023-01-19 13:50 ` Jeffrey Chapuis
-- strict thread matches above, loose matches on Subject: below --
2022-12-28 11:02 Jeffrey CHAPUIS
2022-12-28 11:21 ` Marton Balint
2022-12-28 11:51 ` James Almer
2022-12-28 15:37 ` Jeffrey CHAPUIS
2022-12-27 12:33 Jeffrey CHAPUIS
2022-12-27 11:46 Jeffrey CHAPUIS
2022-12-27 12:34 ` James Almer
2022-12-27 12:57 ` Jeffrey CHAPUIS
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=CAPYw7P6TmmF2-xWHQBpnHdCJWEYmfdvP0K4LTQs3KaXOvQSN5g@mail.gmail.com \
--to=onemda@gmail.com \
--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