From: Quentin RENARD <asticode@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] avfilter: add vf_yazf filter Date: Mon, 02 Jun 2025 11:25:43 +0200 Message-ID: <31D036DC-5BEF-4E40-AFF3-7142ADD0BD14@gmail.com> (raw) In-Reply-To: <20250601221323.GZ29660@pb2> > If this filter is meant to be same as existing zoompan but more precise, > then you should modify the original filter with a mode option for FP use. Thing is I hesitated modifying the existing zoompan but there are a few things that don’t fit my use case and I didn’t want to update too many things: - frame’s PTS is rewritten - configurable output size is not dynamic (and is not evaluated in frame mode) - if output aspect ratio is different than input aspect ratio, output image will be stretched I can: - add an option to enable PTS passthrough - add “w” and “h” options on top of “s” options that would allow dynamic output size - make sure computed crop size respect output aspect ratio Would that be ok? > I would suggest to add a 2nd FFFilter entry to > libavfilter/vf_perspective.c > > with a zoompan user interface to access the already existing interpolation code > in vf_perspective.c > > we have bilinear and bicubic interpolation there and it should form a > better basis for the implementation Reusing vf_perspective.c interpolation implementations seems like a really great idea, I didn’t know they existed. However I don’t understand the way you suggest I should do it. Are you suggesting I should add “const FFFilter ff_vf_yazp = {}” in “vf_perspective.c” and move the zoompan logic there? If not, maybe what you’re suggesting has already been implemented in another filter and I can use it as an example to understand and reproduce it better? Cheers Quentin _______________________________________________ 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-06-02 9:25 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-05-31 14:49 Quentin RENARD 2025-06-01 8:21 ` Gyan Doshi 2025-06-01 22:13 ` Michael Niedermayer 2025-06-02 9:25 ` Quentin RENARD [this message] 2025-06-04 1:11 ` Michael Niedermayer
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=31D036DC-5BEF-4E40-AFF3-7142ADD0BD14@gmail.com \ --to=asticode@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